Hello Holger,
I cannot answer your question below off the top of my head, but I can tell you what I do to increase the gradient parameter space w/out invading the standard Bruker parameter space. I define new pulse names in the header of the pulse program or, better yet, in the *.incl file that I use. The disadvantages are that you must adjust pulse widths in the pulse program, not from the TS command line or ased, and you must enter gradient powers and names manually. However, this has not been much of an inconvenience for our users. To make things easy, I tabulate the gradient pulse names & powers I use as comments in the footer of the pulse program.
I combine all the .incl files I typically use into one file and add the following lines:
define pulse PG1
define pulse PG2
define pulse PG3
define pulse PG4
define pulse PG5
define pulse PG6
define pulse PG7
define pulse PG8
define pulse PG9
define pulse PG10
etc.
(But, again, these can be placed directly at the beginning of the pulse program if desired.)
pulse program usage:
#include "/opt/topspin/exp/stan/nmr/lists/pp/user/bits.jlb" ;(My incl file including above PGi definitions)
;Gradient Pulses
"PG1=1.8m"
"PG2=250u"
"PG3=800u"
"PG4=101.3u" ;decoding
"PG5=500u" ;half-encoding
"PG20=500u"
>.
>.
>.
;beginning of pulse sequence
(p29:sp21 ph11:r):H
3u
2u pl1:H
(p1 ph0):H
3u
PG1:gp1
DELTA
d16
(center (p2 ph0):H (p22 ph0):N)
3u
DELTA
PG1:gp1
d16
(p1 ph1):H
5u
PG20:gp20
d16
>.
>.
>.
etc.
>.
>.
>.
;Footer
;gpz1 = +2% sine.50
;gpz2 = +50% sine.50
;gpz3 = +70% sine.100
;gpz4 = +60% sine.20 Decoding gradient
;gpz5 = -60% sine.20 half-Encoding gradient
;gpz6 = +60% sine.20 half-Encoding gradient
;gpz20 = +50% sine.50
I have only used TS2.1, but I presume the above will work with TS1.3.
regards,
-Dusty Baber
On Oct 21, 2011, at 5:51 PM, Frank H Foersterling wrote:
> AMMRLlers,
> In Bruker Topspin 1.3 I am trying to add p31 as a 5ms gradient pulse
> into the prosol parameters (for the noesy with ZQ suppression). I
> added a line in the relations/default file in the conf/instr/spec/prosol
> directory (in the global section something like P[31]=P_grad3 also a
> line in the params file of the appropriate probehead. But edprosol now
> gives me an error message about an undefined pulse. Is there another
> file I need to edit or is adding gradient pulses not possible ?
> Both gradient pulses already defined in prosol (p16 and p19) are already
> used by experiments I am doing, so changing p31 to p19 in the
> pulseprogram is not an option. Upgrading to a newer version of topspin
> is also not an option.
> Any advise would be apprechiated.
>
> Holger
>
James (Dusty) Baber
NIDDK/NIH
5 Memorial Dr, Rm B1-01
Bethesda, MD 20892-0520
Received on Mon Oct 24 2011 - 04:42:11 MST