States 2D on MSL?
G. Pearson (gpearson@blue.weeg.uiowa.edu)
Wed, 24 Jan 1996 19:19:00 -0600
I'd like to do some hypercomplex 2D on an MSL, and I'd be interested in any
suggestions about how to do this "gracefully".
On an AC-300, etc., with an Aspect 3000 running DISRxx, I just do something
like this:
...
20 D1
do-a-cosine-thing
GO=20
WR #1
IF #1
30 D1
do-a-sine-thing
GO=30
WR #2
IF #2
...
And a similar program would work in UXNMR. File #1 contains the cosine data,
and file #2 contains the sine fids. But in DISMSL, the pulse program and
automation program are distinct, different entities.
At first, I considered trying something like this in an ".AUM" program:
...
10 RP cosine-thing-file-name [.PC program]
GO
WR #1
IF #1
RP sine-thing-file-name
GO
WR #2
IF #2
I4 ; increment the evolution time
IN=10
...
and write & compile separate .PC programs for the sine and cosine pulse
sequences. But I get an error messages for such an ".AUM" program at "compile
time" (just after Esc X) -- error messages about the "RP" lines with either
xxxx.PC or xxxx.PPG. So it looks like I'm stuck with using just _one_ pulse
program.
I _did_ look at the listings for CONOESY.AUM and CONOESY.PC, and found
something that looks somewhat promising. It _does_ seem to involve a lot of
time-consuming disk activity, copying the data from a buffer file to the data
files during acquisition.
; CONOESY.AUM
; CONOESY, MICROPROGRAM TO GENERATE
; COSY AND NOESY FILE WITH CONOESYC.PC,.PPG
1 D4=3U ; Reset D4 to 3U
2 ZE ; Zero data
3 GO ; Acquire data
4 RE #3 ; Read COSY data from buffer file
5 WR #1 ; Store COSY data into SER file
6 IF #1 ; Increment file extension for COSY
7 IF #3 ; Increment extension for buffer file
8 RE #3 ; Read NOESY data
9 WR #2 ; Store NOESY data to NOESY SER file
10 IF #2 ; Increment NOESY SER file extension
11 RF #3.001 ; Reset buffer file extension to 1
12 I4 ; Increment duration 4 for next row
13 IN=2 ; Next row acquisition
14 EXIT ; Stop after NE rows
...
; File #3 is buffer file, MUST be called FIDn.SER, n is
; the number of JOB where acquisition is started.
; This file may be deleted after the experiment.
...
; CONOESY.PC
; COMBINED COSY AND NOESY SHIFT-CORRELATED 2D
; COSY DATA ACQUIRED DURING THE MIXING TIME
; USE WITH CONOESY.AUM MICROPROGRAM.
; SEE HAASNOOT ET AL., J.M.R., 56, 1984, 343
; GUREVICH ET AL., J.M.R., 56, 1984, 471
; 90-D4-90-AQ1-D9-90-AQ2-D0
DE=DW*3/4
PROT F1 F2 XT
SCANS, 10U
LOOP C1 TIMES
D1 [F1 @PL1] ; 90 DEG PREPARATION PULSE
D4 ; EVOLUTION
D1 [F1 @PL2] ; 90 DEG MIXING PULSE
DE [STA] ; USE NT
AQ ; ACQUIRE COSY DATA
D9 ; RANDOMIZED MIXING TIME
D1 [F1 @PL3] ; 90 DEG DETECTION PULSE
DE [STA]
D0 ; ACQUIRE NOESY DATA
++PL1
++PL2
++PL3
END LOOP
10U
GOTO SCANS
BEGIN LISTS
...
I would presume that I could simply write a pulse program which would acquire
a cosine transient, then a sine transient, then add the 2nd cosine transient
to the first one, then the 2nd sine transient to the first one, etc., until I
had done C1 scans on each FID.
QUESTIONS:
1. I don't understand the need for the 2 lines which say
SCANS, 10U
... and
GOTO SCANS
Can anyone explain this to me? Why wont the program work without these
lines? Why does the program work _with_ these lines?
2. Is there another way to do what I want to do?
Thanks in advance for any information.
-- Gerry
---------------------------------------------------------------
Gerald A. Pearson INTERNET: gerald-pearson@uiowa.edu
Chem. Dept., Univ. of Iowa VOICE: 319-335-1336
Iowa City, IA 52242-1219, USA FAX: 319-335-1270
---------------------------------------------------------------