You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have used the official parse tool, which gives correct result as below:
Dtr.rec_len = 65 MSB = 0x00, LSB = 0x41
Dtr.rec_typ = 50
Dtr.rec_sub = 30
Dtr.text_dat = test value is 8000006.000000 for testname manual_data at site 2
But with this tool, the result is parsed as 8000005.5, which is pretty strange. Please help take a look and fix this issue if time allows.
The text was updated successfully, but these errors were encountered:
Looks to me that the code that generates the DTR record text in your test program, is rounding the result value of the preceding PTR record. Maybe a format string issue?
Hi Cmars,
Based on my trying on different tools, I found they gave different results.
1: for pystdf and stdfparser, which are both written in python, the results are both 8000005.5 (actual data is 8000006);
2: for stdf-radar, which is written in R, the result is both 8000005.5 (actual data is 8000006);
3: with stdf-extrator, the result is 8000006, which is matching the original result.
If you want detailed examples, plesae try this problem_example
Hi,
I have used both this pystdf and stdfparser, and found both have wrong parsed results.
The original stdf file is generated on D10, with lines as below:
the std file is uploaded here: stdf file
I have used the official parse tool, which gives correct result as below:
But with this tool, the result is parsed as 8000005.5, which is pretty strange. Please help take a look and fix this issue if time allows.
The text was updated successfully, but these errors were encountered: