Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error when parsing values on win7 x64 #14

Open
jinstrong opened this issue Dec 11, 2018 · 3 comments
Open

error when parsing values on win7 x64 #14

jinstrong opened this issue Dec 11, 2018 · 3 comments

Comments

@jinstrong
Copy link
Contributor

jinstrong commented Dec 11, 2018

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:

double manual_data[4];
manual_data[0] = 8000004;
manual_data[1] = 8000005;
manual_data[2] = 8000006;
manual_data[3] = 8000007;
csicVariableTest("manual_data","efuse_fail",manual_data,0,0xffffffff,"");

the std file is uploaded here: stdf file

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.

@jinstrong
Copy link
Contributor Author

original test result is not correct, to do further validation.

@cmars
Copy link
Owner

cmars commented Dec 11, 2018

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?

@jinstrong
Copy link
Contributor Author

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

@jinstrong jinstrong reopened this Dec 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants