Command Log

This NUTS feature creates a record of commands used in processing each data file. 

commandlog OR cmdlog - a non-2-letter command which controls the command logging operation of NUTS.  Logged commands are stored in the NUTS header (only if NUTS Header Type 3 is used) when the file is saved. If a file is opened that already has a command log, the log will be read and additional commands will be appended.

An example of the command log section of a NUTS header is shown below.  The date and time are the first entry.  When the file is opened, the file name with complete path is listed.  The data were processed with 2 Hz of linebroadening, FT, phasing (QP auto-phase followed by touch-up phasing using PH) and quick polynomial baseline correction, then the processed spectrum was saved.

##$CMD_LOG
Wednesday August 29, 2001 17:32:16
ga C:\nuts\data\qeeb.fid
lb 2.000000
em 2.000000
ft
qp 3.281250 -7.031250 0.000000
ph -0.035889 2.468750 0.000000
qb
sa C:\nuts\data\qeeb.nmr
##$END_CMD_LOG

When phase correction commands are logged, the three values listed are the zero-, first- and second-order corrections.  Note that the values reported are the total, cumulative phase correction, not the incremental adjustment applied by that one command.  So if multiple phasing operations are performed, as shown above for QP followed by PH commands, the last reported values represent the final phase correction applied to the spectrum.

The command log can be enabled or disabled by an entry in the NUTS.INI file:

NUTS_LOG_COMMANDS = TRUE

If this entry is commented out, set to anything other than TRUE, or is absent, then NUTS, by default, will not log the commands.

The command logging can be turned on with the command

cmdlog on

and command logging can be turned off with the command

cmdlog off

The "cmdlog" command without any argument will bring up a dialog box from which the user selects a file, then notepad.exe will be started and the command log for the selected file will be displayed.

When a command Link is executed, the commands in the Link are entered into the command log just once to prevent repetitious entries.  Note that when running macros containing a Loop, it may be advisable to turn off command logging to prevent the command log from getting too big, which will result in slow (potentially, VERY SLOW) reading of the file subsequently.

Last updated: 4/20/05