Running in batch mode

Occasionally it would be useful to retrieve planet fluxes without having to run FLUXES interactively. The current version has been modified so that in certain circumstances the flux values can be written to ADAM parameters and retrieved (this is somewhat easier than parsing the output text file).

When FLUXES is run with a single planet name and filter the calculated flux values for that combination are written to the following ADAM parameters:

HPBW:

Half-power beam width used to calculate F_BEAM (arcsec)

F_CENTRE:

the centre frequency of the selected filter (GHz)

F_WIDTH:

the filter width (GHz)

F_TOTAL:

the total flux (Jy)

F_BEAM:

the total flux in the beam (Jy)

T_BRIGHT:

the brightness temperature of the planet (K)

T_ERROR:

the error in the brightness temperature (K)

SEMI_DIAM:

Semi-diameter of the selected planet (arcsec). If `ALL' planets are selected then the parameter will retain the value of the last planet processed (Neptune)

SOLID_ANG:

Solid angle of the selected planet (steradians). If `ALL' planets are selected then the parameter will retain the value of the last planet processed (Neptune)

If FLUXES is run from the shell (as opposed to running it as a monolith (see later in the section for information on running fluxes as a monolith)) the parameter values can be retrieved by using either the KAPPA parget command or, if running from perl, the par_get routine supplied as part of the NDFPERL package.

Here is an example, running FLUXES from the command-line with no output except via the parameter system

% fluxes pos=no flu=yes screen=no ofl=no now filter=850 apass=no \
       planet=uranus msg_filter=quiet
% parget f_total fluxes
72.4569

Note how MSG_FILTER was used to turn off default messages, and that the FILTER and PLANET were selected explcitly. Also, useful output was obtained even though fluxes was instructed to write to neither the screen or a file (and MSG_FILTER=QUIET hides output even if SCREEN=yes).

It is possible to run FLUXES as a monolith but this requires that the fluxes monolith is run directly (not via the fluxes.csh shell script), that the envrionment variables FLUXES_DIR and FLUXPWD are set to the location of the fluxes binary and the current working directory respectively. If it is running as a monolith (specifically as an I-task) the parameter values can then be retrieved from the monolith (e.g. by using STARTCL ).