4 ms·
I understand you don't want to change because it does invalidate a big portion of your article. But by dancing around the problem, instead of addressing it, you
by HardyLeung 15y ago
I understand you don't want to change because it does invalidate a big portion of your article. But by dancing around the problem, instead of addressing it, you did weaken the trustworthiness of your article, and make it sound more of a witch hunt (read: chasing idea without much evidence).
You have two points that I think are reasonable to raise: (1) is there a mistake (intentional or not) in the assumed margin of error in the measuring equipment? (2) is the DRAM caching behavior taken into consideration? Neither of these two points have anything to do with FPGA per se. Now by including the enchilada word "FPGA platform" into the fray (whereas it was clearly not the intention at the beginning), I feel like you are making things up as you go, which is unfortunate since part of your argument is valid.
- mrb 15y agoI cannot title it "DRAM artifacts" because it would be only 1 of the 3 different causes I speculate on (DRAM, oscillator, FPGA clock). I chose the word "FPGA" to match the terminology of the paper which uses the word as a synonym for the Data Acquisition System.
- CamperBob 15y agoI chose the word "FPGA" to match the terminology of the paper which uses the word as a synonym for the Data Acquisition System. If so, that's a problem with the paper in itself. (I haven't read it.)