Just guessing here - since data looks largely like noise - you might be reading starting incorrect byte or your reading of number numbers may be shifted with respect to the data point boundaries or you might have incorrect byte order (little-endian vs. big-endian).

Maybe you can take a step back and look at the FID after reading it from the source and compare it to what you see in spinworks or other software.

Just guessing here - since data looks largely like noise - you might be reading starting incorrect byte or your reading of numbers may be shifted with respect to the data point boundaries or you might have incorrect byte order (little-endian vs. big-endian).

Maybe you can take a step back and look at the FID after reading it from the source and compare it to what you see in spinworks or other software.

Just guessing here - since data looks largely like noise - you might be reading starting incorrect byte or your reading of numbers may be shifted with respect to the data point boundaries or you might have incorrect byte order (little-endian vs. big-endian).

Maybe you can take a step back and look at the FID after reading it from the source and compare it to what you see in spinworks or other software.

edit by offset (in the comments) I mean "byte distance" from the beginning of the file up to the point from where you read.read. basically that you are getting wrong numbers means that either you are reading them from wrong locations within file, or you have reversed byte order or you might be mis-interpreting format of storage of the numerical data (float/double/long, etc.) - I have not worked with programming like that in a long time though.

Of course you might have more than one issue at once.

Just guessing here - since data looks largely like noise - you might be reading starting incorrect byte or your reading of numbers may be shifted with respect to the data point boundaries or you might have incorrect byte order (little-endian vs. big-endian).

Maybe you can take a step back and look at the FID after reading it from the source and compare it to what you see in spinworks or other software.

edit by offset (in the comments) I mean "byte distance" from the beginning of the file up to the point from where you read. basically that you are getting wrong numbers means that either you are reading them from wrong locations within file, or you have reversed byte order or you might be mis-interpreting format of storage of the numerical data (float/double/long, etc.) - I have not worked with programming like that in a long time though.

Of course you might have more than one issue at once.

Just guessing here - since data looks largely like noise - you might be reading starting incorrect byte or your reading of numbers may be shifted with respect to the data point boundaries or you might have incorrect byte order (little-endian vs. big-endian).

Maybe you can take a step back and look at the FID after reading it from the source and compare it to what you see in spinworks or other software.

edit by offset (in the comments) I mean "byte distance" from the beginning of the file up to the point from where you read. basically that you are getting wrong numbers means that either you are reading them from wrong locations within file, or you have reversed byte order or you might be mis-interpreting format of storage of the numerical data (float/double/long, etc.) - I have not worked with programming like that in a long time though. Of course you might have more than one issue at once.

Take a look at previous posts tagged "data-format""data-format", maybe they will give you some hints.

Just guessing here - since data looks largely like noise - you might be reading starting incorrect byte or your reading of numbers may be shifted with respect to the data point boundaries or you might have incorrect byte order (little-endian vs. big-endian).

Maybe you can take a step back and look at the FID after reading it from the source and compare it to what you see in spinworks or other software.

edit by offset (in the comments) I mean "byte distance" from the beginning of the file up to the point from where you read. basically that you are getting wrong numbers means that either you are reading them from wrong locations within file, or you have reversed byte order or you might be mis-interpreting format of storage of the numerical data (float/double/long, etc.) - I have not worked with programming like that in a long time though. Of course you might have more than one issue at once.

Take a look at previous posts tagged "data-format", "data-format", maybe they will give you some hints.

Just guessing here - since data looks largely like noise - you might be reading starting incorrect byte or your reading of numbers may be shifted with respect to the data point boundaries or you might have incorrect byte order (little-endian vs. big-endian).

Maybe you can take a step back and look at the FID after reading it from the source and compare it to what you see in spinworks or other software.

edit maybe you can try creating a synthetic fid where all points have the same non-zero value. Then read the data and see what numbers you get. That may give you some hints. You can also compare the real data offset as you read with the expected offset - based on what you know from the data format.

by offset (in the comments) I mean "byte distance" from the beginning of the file up to the point from where you read. basically that you are getting wrong numbers means that either you are reading them from wrong locations within file, or you have reversed byte order or you might be mis-interpreting format of storage of the numerical data (float/double/long, etc.) - I have not worked with programming like that in a long time though. Of course you might have more than one issue at once.

Take a look at previous posts tagged "data-format", maybe they will give you some hints.