Hi,

If you got to the stage of gcbcaconh you've already done all the major probe calibrations. The s/n is measured is at the beginning and it aborts if the s/n on the first experiment is too low. There are a couple of other cases where s/n is measured and nt re-calculated (for the gNhsqc d1 array to set nt for the gNhsqc1D gNhsqc_1D data set (BP7a macro) and BP10 for the ghnco ghn_co data set.

You should recall ~/vnmrsys/AutoTripRes/ghn~/vnmrsys/AutoTripRes/ghn_co_ca_1D.fid. This has the nt value that is used also for the gcbcacoca1D.fid. This has the nt value that is used also for the gcbcaco_nh nh phi7cal calibration. It should be a small number, not something that would take hours.

You can also recall the ghnco1D data set. This has the nt set by the macro BP10 to achieve a s/n > 20. If something prevented normal behavior this experiment might not work and the s/n would be too low for normal nt. You can also check the behavior of the ghnca1D, ghncaco1D and ghncoca1D ghn_ca_1D, ghn_ca_co_1D and ghn_co_ca_1D fids - all of these should be using the nt determined by the BP10 macro and used for the ghnco1D ghn_co_1D data set. Note that the gzlvl2 and compC calibrations had already been done and should have taken a normal time.

Check the printouts (if you did them) and look at the nt value in the parameter printout. Otherwise, you could recall the data in the order it was acquired (use a shell and cd to vnmrsys/AutoTripRes. Then do "ls -altr". "ls -altr". This will show the fids in order, with the last acquired fid at the bottom. Recall the data and check the s/n and the nt number.

-George Gray, Varian Inc.

Hi,

If you got to the stage of gcbcaconh gcbca_co_nh you've already done all the major probe calibrations. The s/n is measured is at the beginning and it aborts if the s/n on the first experiment is too low. There are a couple of other cases where s/n is measured and nt re-calculated (for the gNhsqc d1 array to set nt for the gNhsqc_1D data set (BP7a macro) and BP10 for the ghn_co ghn_co data set.

You should recall ~/vnmrsys/AutoTripRes/ghn_co_ca_1D.fid. This has the nt value that is used also for the gcbcaconh phi7cal gcbca_co_nh phi7cal calibration. It should be a small number, not something that would take hours.

You can also recall the ghnco1D ghn_co_1D data set. This has the nt set by the macro BP10 to achieve a s/n > 20. If something prevented normal behavior this experiment might not work and the s/n would be too low for normal nt. You can also check the behavior of the ghn_ca_1D, ghn_ca_co_1D and ghn_co_ca_1D fids - all of these should be using the nt determined by the BP10 macro and used for the ghn_co_1D data set. Note that the gzlvl2 and compC calibrations had already been done and should have taken a normal time.

Check the printouts (if you did them) and look at the nt value in the parameter printout. Otherwise, you could recall the data in the order it was acquired (use a shell and cd to vnmrsys/AutoTripRes. Then do "ls -altr". This will show the fids in order, with the last acquired fid at the bottom. Recall the data and check the s/n and the nt number.

-George Gray, Varian Inc.