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

posted Nov 23 '09 at 08:45

hasancelik's gravatar image

hasancelik
48

ASCII->nmrPipe format conversion

I have a 2D complex time domain set stored in ASCII format. I want to be able to process it using nmrPipe. Unfortunately I am running into trouble once I try to use txt2pipe.tcl macro from the nmrPipe package. By convention it assumes that the data is in frequency domain and is real. The conversion into the time domain can be achieved by setting the headers correctly, however the 2D acqusition mode not as easily (Comlex/States/Rance-Kay etc. ). Here is the header I use before FT'ing:

sethdr test.fid -ndim 2 -aq2D States -xFT Time -xMODE Complex -xT 1024 -xN 512 -yFT Time -yMODE Complex -yT 256 -xN 128

Also the way the data is stored is as the following (with 4 spacing in between parameters):

1 1 1 Re[1,1] ! N-type

2 1 1 Re[1,1]

3 1 1 Re[1,1]

...

512 1 1 Re[1,1]

513 1 1 Im[1,1]

...

1024 1 1 Im[1,1]

1 2 1 Re[1,1]* ! P-type

2 2 1 Re[1,1]*

3 2 1 Re[1,1]*

...

512 2 1 Re[1,1]*

513 2 1 Im[1,1]*

...

1024 2 1 Im[1,1]*

. . .

1 256 1 Re[1,1]*

2 256 1 Re[1,1]*

3 256 1 Re[1,1]*

...

512 256 1 Re[1,1]*

513 256 1 Im[1,1]*

...

1024 256 1 Im[1,1]*

I would appreciate it if anyone can point me out whether there is something wrong with the header or the way the data is stored, or even whether it is possible to do with nmrDraw or not.

Thanks, Hasan Celik

click to hide/show revision 2
removed > mark from title because of a bug in RSS feed generator

posted Nov 23 '09 at 09:26

Evgeny%20Fadeev's gravatar image

Evgeny Fadeev
5771

ASCII->nmrPipe ASCII to nmrPipe format conversion

I have a 2D complex time domain set stored in ASCII format. I want to be able to process it using nmrPipe. Unfortunately I am running into trouble once I try to use txt2pipe.tcl macro from the nmrPipe package. By convention it assumes that the data is in frequency domain and is real. The conversion into the time domain can be achieved by setting the headers correctly, however the 2D acqusition mode not as easily (Comlex/States/Rance-Kay etc. ). Here is the header I use before FT'ing:

sethdr test.fid -ndim 2 -aq2D States -xFT Time -xMODE Complex -xT 1024 -xN 512 -yFT Time -yMODE Complex -yT 256 -xN 128

Also the way the data is stored is as the following (with 4 spacing in between parameters):

1 1 1 Re[1,1] ! N-type

2 1 1 Re[1,1]

3 1 1 Re[1,1]

...

512 1 1 Re[1,1]

513 1 1 Im[1,1]

...

1024 1 1 Im[1,1]

1 2 1 Re[1,1]* ! P-type

2 2 1 Re[1,1]*

3 2 1 Re[1,1]*

...

512 2 1 Re[1,1]*

513 2 1 Im[1,1]*

...

1024 2 1 Im[1,1]*

. . .

1 256 1 Re[1,1]*

2 256 1 Re[1,1]*

3 256 1 Re[1,1]*

...

512 256 1 Re[1,1]*

513 256 1 Im[1,1]*

...

1024 256 1 Im[1,1]*

I would appreciate it if anyone can point me out whether there is something wrong with the header or the way the data is stored, or even whether it is possible to do with nmrDraw or not.

Thanks, Hasan Celik

click to hide/show revision 3
made title more detailed

posted Nov 23 '09 at 09:28

Evgeny%20Fadeev's gravatar image

Evgeny Fadeev
5771

ASCII to nmrPipe format conversionconversion of 2D complex time tomain data

I have a 2D complex time domain set stored in ASCII format. I want to be able to process it using nmrPipe. Unfortunately I am running into trouble once I try to use txt2pipe.tcl macro from the nmrPipe package. By convention it assumes that the data is in frequency domain and is real. The conversion into the time domain can be achieved by setting the headers correctly, however the 2D acqusition mode not as easily (Comlex/States/Rance-Kay etc. ). Here is the header I use before FT'ing:

sethdr test.fid -ndim 2 -aq2D States -xFT Time -xMODE Complex -xT 1024 -xN 512 -yFT Time -yMODE Complex -yT 256 -xN 128

Also the way the data is stored is as the following (with 4 spacing in between parameters):

1 1 1 Re[1,1] ! N-type

2 1 1 Re[1,1]

3 1 1 Re[1,1]

...

512 1 1 Re[1,1]

513 1 1 Im[1,1]

...

1024 1 1 Im[1,1]

1 2 1 Re[1,1]* ! P-type

2 2 1 Re[1,1]*

3 2 1 Re[1,1]*

...

512 2 1 Re[1,1]*

513 2 1 Im[1,1]*

...

1024 2 1 Im[1,1]*

. . .

1 256 1 Re[1,1]*

2 256 1 Re[1,1]*

3 256 1 Re[1,1]*

...

512 256 1 Re[1,1]*

513 256 1 Im[1,1]*

...

1024 256 1 Im[1,1]*

I would appreciate it if anyone can point me out whether there is something wrong with the header or the way the data is stored, or even whether it is possible to do with nmrDraw or not.

Thanks, Hasan Celik

click to hide/show revision 4
No.3 Revision

posted Nov 23 '09 at 09:28

Evgeny%20Fadeev's gravatar image

Evgeny Fadeev
5771

ASCII to nmrPipe format conversion of 2D complex time tomain domain data

I have a 2D complex time domain set stored in ASCII format. I want to be able to process it using nmrPipe. Unfortunately I am running into trouble once I try to use txt2pipe.tcl macro from the nmrPipe package. By convention it assumes that the data is in frequency domain and is real. The conversion into the time domain can be achieved by setting the headers correctly, however the 2D acqusition mode not as easily (Comlex/States/Rance-Kay etc. ). Here is the header I use before FT'ing:

sethdr test.fid -ndim 2 -aq2D States -xFT Time -xMODE Complex -xT 1024 -xN 512 -yFT Time -yMODE Complex -yT 256 -xN 128

Also the way the data is stored is as the following (with 4 spacing in between parameters):

1 1 1 Re[1,1] ! N-type

2 1 1 Re[1,1]

3 1 1 Re[1,1]

...

512 1 1 Re[1,1]

513 1 1 Im[1,1]

...

1024 1 1 Im[1,1]

1 2 1 Re[1,1]* ! P-type

2 2 1 Re[1,1]*

3 2 1 Re[1,1]*

...

512 2 1 Re[1,1]*

513 2 1 Im[1,1]*

...

1024 2 1 Im[1,1]*

. . .

1 256 1 Re[1,1]*

2 256 1 Re[1,1]*

3 256 1 Re[1,1]*

...

512 256 1 Re[1,1]*

513 256 1 Im[1,1]*

...

1024 256 1 Im[1,1]*

I would appreciate it if anyone can point me out whether there is something wrong with the header or the way the data is stored, or even whether it is possible to do with nmrDraw or not.

Thanks, Hasan Celik

click to hide/show revision 5
No.4 Revision

posted Dec 04 '09 at 19:28

Evgeny%20Fadeev's gravatar image

Evgeny Fadeev
5771

ASCII to nmrPipe format conversion of 2D complex time domain data

I have a 2D complex time domain set stored in ASCII format. I want to be able to process it using nmrPipe. Unfortunately I am running into trouble once I try to use txt2pipe.tcl macro from the nmrPipe package. By convention it assumes that the data is in frequency domain and is real. The conversion into the time domain can be achieved by setting the headers correctly, however the 2D acqusition mode not as easily (Comlex/States/Rance-Kay etc. ). Here is the header I use before FT'ing:

sethdr test.fid -ndim 2 -aq2D States -xFT Time -xMODE Complex -xT 1024 -xN 512 -yFT Time -yMODE Complex -yT 256 -xN 128

Also the way the data is stored is as the following (with 4 spacing in between parameters):

1 1 1 Re[1,1] ! N-type

2 1 1 Re[1,1]

3 1 1 Re[1,1]

...

512 1 1 Re[1,1]

513 1 1 Im[1,1]

...

1024 1 1 Im[1,1]

1 2 1 Re[1,1]* ! P-type

2 2 1 Re[1,1]*

3 2 1 Re[1,1]*

...

512 2 1 Re[1,1]*

513 2 1 Im[1,1]*

...

1024 2 1 Im[1,1]*

. . .

1 256 1 Re[1,1]*

2 256 1 Re[1,1]*

3 256 1 Re[1,1]*

...

512 256 1 Re[1,1]*

513 256 1 Im[1,1]*

...

1024 256 1 Im[1,1]*

I would appreciate it if anyone can point me out whether there is something wrong with the header or the way the data is stored, or even whether it is possible to do with nmrDraw or not.

Thanks, Hasan Celik

click to hide/show revision 6
corrected formatting

posted Dec 10 '09 at 07:01

Evgeny%20Fadeev's gravatar image

Evgeny Fadeev
5771

ASCII to nmrPipe format conversion of 2D complex time domain data

I have a 2D complex time domain set stored in ASCII format. I want to be able to process it using nmrPipe. Unfortunately I am running into trouble once I try to use txt2pipe.tcl macro from the nmrPipe package. By convention it assumes that the data is in frequency domain and is real. The conversion into the time domain can be achieved by setting the headers correctly, however the 2D acqusition mode not as easily (Comlex/States/Rance-Kay etc. ). Here is the header I use before FT'ing:

sethdr test.fid -ndim 2 -aq2D States -xFT Time -xMODE Complex \
        -xT 1024 -xN 512 -yFT Time -yMODE Complex -yT 256 -xN 128

128

Also the way the data is stored is as the following (with 4 spacing in between parameters):

1 1 1 Re[1,1] ! N-type

2 1 1 Re[1,1]

3 1 1 Re[1,1]

...

512 1 1 Re[1,1]

513 1 1 Im[1,1]

...

1024 1 1 Im[1,1]

1 2 1 Re[1,1]* ! P-type

2 2 1 Re[1,1]*

3 2 1 Re[1,1]*

...

512 2 1 Re[1,1]*

513 2 1 Im[1,1]*

...

1024 2 1 Im[1,1]*

. . .

1 256 1 Re[1,1]*

2 256 1 Re[1,1]*

3 256 1 Re[1,1]*

...

512 256 1 Re[1,1]*

513 256 1 Im[1,1]*

...

1024 256 1 Im[1,1]*

I would appreciate it if anyone can point me out whether there is something wrong with the header or the way the data is stored, or even whether it is possible to do with nmrDraw or not.

Thanks, Hasan Celik

powered by CNPROG