Revision history [back]
click to hide/show revision 1
initial version

posted Jan 18 '10 at 05:50

j's gravatar image

j
131

I've written a binary parser for the varian fid files. Below is the output. The global header in varian FID files define a meta data parameter "S_COMPLEX". Additionally, each FID block defines the np_cmplx,ni_cmplex,and ni2_cmplx. I'm reading all of these values in as false !!! This implies that my fid is not complex... And I know that, in fact, my fid file is complex. So my confusion is as follows : Why does my fid meta data appear to be telling me that my fid points are real, as opposed to complex ? Here is the output of my program. As you can see, many of the meta data parameters look reasonable, implying that the parser basically works okay. For example, it is getting reasonable values for the number of points, the data flag, the fid flag, the number of traces, etc.... but all the boolean flags for "complex" vs "real" seem to be off. //////////////////////////////////////// data true fid true There are 1 block headers in this file type. np complex false ni complex false ni2 complex false nf complex false more false Added 12 meta data parameters out of 12 1 : FILE_NUM_TYPE = Integer 2 : BLOCK_HEADER_SKIP_SIZE = 28 3 : FILE_NUM_RC = Real 4 : FILE_GLOBAL_FOOTER = 0 5 : FILE_DATA_ORDER = INTERLEAVED 6 : FILE_AMOUNT_OF_DATA_FILES = 1 8 : DEBUG1 = {bytesPerTrace=8192.0, bytesPerElement=4.0, elementsPerTrace=2048.0, bytesPerTrace/bytesPerElement=2048.0} 9 : FILE_BLOCK_COUNT = 256 10 : FILE_GLOBAL_HEADER = 32 11 : BLOCK_FOOTER_SKIP_SIZE = 0 12 : FILE_ENDIAN = BIG_ENDIAN
click to hide/show revision 2
No.1 Revision

posted Jan 18 '10 at 05:52

j's gravatar image

j
131

I've written a binary parser for the varian fid files.  Below is the output.  The global header in varian FID files define a meta data parameter "SCOMPLEX". "S_COMPLEX".  Additionally, each FID block defines the npcmplx,nicmplex,and ni2cmplx. np_cmplx,ni_cmplex,and ni2_cmplx.  I'm reading all of these values in as false !!! This implies that my fid is not complex... And I know that, in fact, my fid file is complex.  

So my confusion is as follows : Why does my fid meta data appear to be telling me that my fid points are real, as opposed to complex ?

Here is the output of my program. As you can see, many of the meta data parameters look reasonable, implying that the parser basically works okay. For example, it is getting reasonable values for the number of points, the data flag, the fid flag, the number of traces, etc.... but all the boolean flags for "complex" vs "real" seem to be off.

<code> //////////////////////////////////////// data true fid true

true There are 1 block headers in this file type. np complex false ni complex false ni2 complex false nf complex false more false

false Added 12 meta data parameters out of 12

12 1 : FILENUMTYPE FILE_NUM_TYPE = Integer 2 : BLOCKHEADERSKIPSIZE BLOCK_HEADER_SKIP_SIZE = 28 3 : FILENUMRC FILE_NUM_RC = Real 4 : FILEGLOBALFOOTER FILE_GLOBAL_FOOTER = 0 5 : FILEDATAORDER FILE_DATA_ORDER = INTERLEAVED 6 : FILEAMOUNTOFDATAFILES FILE_AMOUNT_OF_DATA_FILES = 1 8 : DEBUG1 = {bytesPerTrace=8192.0, bytesPerElement=4.0, elementsPerTrace=2048.0, bytesPerTrace/bytesPerElement=2048.0} 9 : FILEBLOCKCOUNT FILE_BLOCK_COUNT = 256 10 : FILEGLOBALHEADER FILE_GLOBAL_HEADER = 32 11 : BLOCKFOOTERSKIPSIZE BLOCK_FOOTER_SKIP_SIZE = 0 12 : FILEENDIAN = BIGENDIANFILE_ENDIAN = BIG_ENDIAN

click to hide/show revision 3
No.2 Revision

posted Jan 18 '10 at 05:53

j's gravatar image

j
131

I've written a binary parser for the varian fid files.  Below is the output.  output.

The global header in varian FID files define a meta data parameter "S_COMPLEX". "SCOMPLEX".
Additionally, each FID block defines the np_cmplx,ni_cmplex,and ni2_cmplx. npcmplx,nicmplex,and ni2cmplx.
I'm reading all of these values in as false !!! This implies that my fid is not complex... And I know that, in fact, my fid file is complex.

So my confusion is as follows : Why does my fid meta data appear to be be

telling me that my fid points are real, as opposed to complex ?

Here is the output of my program.  As you can see, many of the meta data parameters parameters

look reasonable, implying that the parser basically works okay. For example, it is getting reasonable values for the number of points, the data flag, the fid flag, the number of traces, etc.... but all the boolean flags for "complex" vs "real" seem to be off.

<code>
////////////////////////////////////////
data true
fid true

There are 1 block headers in this file type. 
    np  complex false
    ni  complex false
    ni2 complex false
    nf complex false
    more false

Added 12 meta data parameters out of 12

1 : FILE_NUM_TYPE = Integer
2 : BLOCK_HEADER_SKIP_SIZE = 28
3 : FILE_NUM_RC = Real
4 : FILE_GLOBAL_FOOTER = 0
5 : FILE_DATA_ORDER = INTERLEAVED
6 : FILE_AMOUNT_OF_DATA_FILES = 1
8 : DEBUG1 = {bytesPerTrace=8192.0, bytesPerElement=4.0, elementsPerTrace=2048.0, bytesPerTrace/bytesPerElement=2048.0}
9 : FILE_BLOCK_COUNT = 256
10 : FILE_GLOBAL_HEADER = 32
11 : BLOCK_FOOTER_SKIP_SIZE = 0
12 : FILE_ENDIAN = BIG_ENDIAN

click to hide/show revision 4
No.3 Revision

posted Jan 18 '10 at 05:53

j's gravatar image

j
131

    I've written a binary parser for the varian fid files.  Below is the output.

output. The global header in varian FID files define a meta data parameter "SCOMPLEX".
"S_COMPLEX". Additionally, each FID block defines the npcmplx,nicmplex,and ni2cmplx.
np_cmplx,ni_cmplex,and ni2_cmplx. I'm reading all of these values in as false !!! This implies that my fid is not complex... And I know that, in fact, my fid file is complex.



    So my confusion is as follows : Why does my fid meta data appear to be

be telling me that my fid points are real, as opposed to complex ?



    Here is the output of my program.  As you can see, many of the meta data parameters

parameters look reasonable, implying that the parser basically works okay. For example, it is getting reasonable values for the number of points, the data flag, the fid flag, the number of traces, etc.... but all the boolean flags for "complex" vs "real" seem to be off.



<code>
////////////////////////////////////////
data true
fid true

There are 1 block headers in this file type. 
    np  complex false
    ni  complex false
    ni2 complex false
    nf complex false
    more false

Added 12 meta data parameters out of 12

1 : FILE_NUM_TYPE = Integer
2 : BLOCK_HEADER_SKIP_SIZE = 28
3 : FILE_NUM_RC = Real
4 : FILE_GLOBAL_FOOTER = 0
5 : FILE_DATA_ORDER = INTERLEAVED
6 : FILE_AMOUNT_OF_DATA_FILES = 1
8 : DEBUG1 = {bytesPerTrace=8192.0, bytesPerElement=4.0, elementsPerTrace=2048.0, bytesPerTrace/bytesPerElement=2048.0}
9 : FILE_BLOCK_COUNT = 256
10 : FILE_GLOBAL_HEADER = 32
11 : BLOCK_FOOTER_SKIP_SIZE = 0
12 : FILE_ENDIAN = BIG_ENDIAN

click to hide/show revision 5
reformatted text with markdown

posted Jan 18 '10 at 10:54

Evgeny%20Fadeev's gravatar image

Evgeny Fadeev
5771

    

I've written a binary parser for the varian fid files. Below is the output.
The global header in varian FID files define a meta data parameter "S_COMPLEX". S_COMPLEX.
Additionally, each FID block defines the np_cmplx,ni_cmplex,and ni2_cmplx. np_cmplx, ni_cmplex,and ni2_cmplx.
I'm reading all of these values in as false !!! This implies that my fid is not complex... And I know that, in fact, my fid file is complex.

So my confusion is as follows : Why does my fid meta data appear to be telling me that my fid points are real, as opposed to complex ?

Here is the output of my program. As you can see, many of the meta data parameters look reasonable, implying that the parser basically works okay. For example, it is getting reasonable values for the number of points, the data flag, the fid flag, the number of traces, etc.... but all the boolean flags for "complex" vs "real" seem to be off. <code>

////////////////////////////////////////
data true
fid true

There are 1 block headers in this file type. 
    np  complex false
    ni  complex false
    ni2 complex false
    nf complex false
    more false

Added 12 meta data parameters out of 12

1 : FILE_NUM_TYPE = Integer
2 : BLOCK_HEADER_SKIP_SIZE = 28
3 : FILE_NUM_RC = Real
4 : FILE_GLOBAL_FOOTER = 0
5 : FILE_DATA_ORDER = INTERLEAVED
6 : FILE_AMOUNT_OF_DATA_FILES = 1
8 : DEBUG1 = {bytesPerTrace=8192.0, bytesPerElement=4.0, elementsPerTrace=2048.0, bytesPerTrace/bytesPerElement=2048.0}
9 : FILE_BLOCK_COUNT = 256
10 : FILE_GLOBAL_HEADER = 32
11 : BLOCK_FOOTER_SKIP_SIZE = 0
12 : FILE_ENDIAN = BIG_ENDIAN

powered by CNPROG