Private parameters for program NGIDS
This document contains an overview of the parameter interface of the program NGIDS. The program also uses a number of public interfaces; references to these are also listed.
The remainder of the document describes the individual parameters in alphabetical order. This description centers on the Help texts, which have been designed to guide the user to the proper choice at each junction, even if his knowledge of the overall workings of the program is only superficial.
See also:
Prompt: Propagate flag changes to all channels (Yes/No)?
Expected input: Yes/No: 1 value
If you answer Yes to this prompt, each flag will be set for all channels. That is: If you set a flag in channel <i> it will be copied (in the flag list) to the corresponding points in all other frequency channels.
Prompt: Propagate flag changes to all polarisations (Yes/No)?
Expected input: Yes/No: 1 value
If you answer Yes to this prompt, each flag will be set for all polarisations. That is: if you set a flag on an XX visibility it will be copied (in the flag list) to the corresponding XY, YX and YY visibilities.
Prompt: Display area (l,m, dl,dm)
Expected input: Integer: 1 to 4 values
Specify the map area to be displayed. The coordinates are in grid units. (0,0) is the map centre increase is toward the upper right (decreasing RA, incrasing DEC). The area is defined by four values:
l,m area centre dl,dm area size
Prompt: Blank flagged data-points (Yes/No)?
Expected input: Yes/No: 1 value
If you answer YES to this prompt, data points that are flagged will be set to blank in the GIDS window.
A single red overlay plane is used to display flagged data points. This plane will contain the flags for the last plane loaded. The BLANK_FLAGS option allows you to discern flagged data in other pictures.
Prompt: Clip limit for flagging
Expected input: Real: 1 value
All visibilities that exceed the limit in the quantity displayed (cf. parameter DATA_TYPE) will be flagged. Select a suitable level by consulting the display. The colour bar to the left is annotated with values and you the pixel value pointed at by the cursor is shown in the upper left corner.see parameter DATA_TYPE
Prompt: Select visibility component to display
Expected input: Character *16: 1 value
Specify how to display complex visibility values
Prompt: display-size compression factor
Expected input: Integer: 1 value
For a value N, the points in a N*N box are averaged into a single display point. . Example: A 1024*1024 map loaded with N=2 will result in a 512*512 image.
Prompt: Data-value range for diaplay
Expected input: Real: 1 to 2 values
Data values outside the limuts will be truncated to the coresponding limit.
By choosing suitable limits you can concentrate the display on a particular range of intensities in the map. The defaults shown are the extremes in the image to be displayed.
Prompt: Display-plane range to delete
Expected input: Integer: 1 to 2 values
The display planes are numbered sequentially in the order in which they were loaded. You may specify here the first and last value for a range of planes that will be removed from the GIDS display memory.
Prompt: Load next picture
Expected input: Character *5: 1 value
This prompt appears after the loading of a picture. NGIDS will wait for your reply while you may manipulate the GIDS display. Your reply options are:
YES Load next picture, then return with this prompt NO Quit loading, return to OPTION prompt ALL Load all remaining pictures without intervening consultations
Prompt: action
Expected input: Character *24: 1 value
Specify the action to perform.
Loading/unloading visibility data or images for half-tone/colour display. The visibility 'planes' or images that you select are stored in display memory for rapid access. The number of pictures that you can store is limited by the availablity of this memory.
MAP Load images(s) from map (.WMP) files. DATA Load (corrected) data from visibility (.SCN) files
Select mode for flagging of visibility data on the display. The flags you set will not yet be written back to the .SCN file, so you can freely experiment.
DOFLAG Switch to Flagging mode for .SCN-file visibilities CLIPFLAG Switch to Flagging mode using cliplevels FLAG Flagging in .WMP maps using the PGPLOT cursor in GIDS
Saving the flags you set on your display:
UNLOAD Save flags list in a .FLF (binary file), from which you can then transfer to the .SCN file through NFLAG LOAD. WRITE Save flags list in an ASCII file, which you may manually edit before transferringt it to the .SCN file through NFLAG READ. CLEAR Clear flags list.see NFLAG OPS_FLIST parameter
Terminate current action sequence:
GCLEAR Remove a sequence of loaded pictures. NOFLAG Switch back to normal display mode. QUIT Leave NGIDS (the GIDS window will remain on the screen).
Prompt: (output filename)
Expected input: Character *80: 1 value
Specify the full name for the output disk-file.
Expected input: Character *16: 1 value
In displaying visibilities, you can choose between three two-dimensional cross sections:
IFRS Hour angle (horizontal) versus interferometer (vertical), one picture per frequency channel. Interferometers in the order ....
BASE As IFRS, but interferometers in order of increasing baseline, - and of increasing East telecope number within sets of redundant baselines.
CHAN Hour angle (horizontal) versus frequency channel (vertical), one picture per interferometer.
NOTE: You select the channels to be displayed through the SCN_SETS parameter, in the form <grp>.<obs>.<fld>.<CHN>. You have the liberty to select SCN_SETS with channels for more than one <grp>.<obs>.<fld>. You may think of some good use of this option (e.g. displaying the same channel for all fields in a mosaic).
Prompt: Flags to use
Expected input: Character *16: 1 to 16 values
Each of the flagging modes (parameter OPTION, options FLAG, DOFLAG, CLIPFLAG) uses a specific flag type by default. You may define here one ore more flags to use instead. The use foreseen for this option is to experiment using one of 'user' flags without getting the experimental settings tangled up with settings already in existence.see parameter OPTION
NONE revert to default types per flagging mode ALL or * use all flag types (not a very sensible idea)
MAN use the flag type for the MANUAL class of operations CLIP use the flag type for the CLIP class of operations NOISE use the flag type for the NOISE class of operations SHAD use the flag type for the SHADOW class of operations ADD use the flag type for the ADDITIVE class of operations
U1 use a separate flag for some user-defined operations U2 use a separate flag for some user-defined operations U3 use a separate flag for some user-defined operations
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.