|
Linuxpops
3.01.04
Spectral Anaysis Package for Single Dish Data
|
Nearly every command in Linuxpos contains modifier flags. The flags modify the behaviour of the commands and allows flexibility.
To see what flags are present for a command just ask help: Example baseline fitting using the bshape command.
All commands have their own internal help reply.
The following flags are common to all/most/some commands.
/h Print out Help
/q Quiet flag; Most commands respect this
/v Sometimes commands will produce more verbose output with this set
Color flags used for labels and things. Most commands that print on the plots respect these
/Cbk
/Crd
/Cgr
/Cyl
/Cbl
/Cmg
/Ccy
/Cwt
Formatting flags for printouts:
/log
/hex
/exp
Normally, the order of flags after a command is not important. The source code for the command checks for the presence of a particular flag in the order of importance.
But, some of the more complicated commands such as otf and gmap have many options and soon we start to run out of flags. In those cases we used overloaded flags, in that, a particular flag may appears more that once in the command.
So, in order to allow this on these commands, the very first flag will become the 'key' action flag. Once this action flags has been handled, it is noted and removed from the flag-array and it's reference count is decremented; thus there can be additional flags of the same type.
For instance, gmap can use the /p flag multiple times. If it's the first flag, then gmap will plot the map, but if there are more /p flags in the same command, then that tells the plotting routine to make a PS file out of the plot. Another /p flags tells it to make a PS and a PNG file.
So far, only gmap and otf commands require the action flag to be first. Additional commands may come on-line in the future. It's easy to tell which commands as they will highlight a YELLOW CAUTION warning in the help for those commands.