Level 2 Help for MARSIGOOD

Input files contain a goodness band which indicates whether the product
meets thresholds.  Up to 5 inputs are supported, although this is arbitrary
and easily increased if needed.  List file inputs are not supported.

If an input file is "--", it is ignored.  This allows the same slots to
be re-used in different scenarios.  For example, on InSight the SEIS goodness
file has two roughness inputs, but HP3 has only one.  Supplying -- for the
second input for HP3 allows the 3rd input to be tilt in most cases, meaning
the SINGLE_BAD values don't have to change per instrument.

Output goodness file.  The values in this file are controlled by the
GOOD_VALUE, SINGLE_BAD, MULTI_BAD, and MASK_BAD parameters.

Optional mask file.  If the mask file is present, anything outside the mask
is marked bad.

Specifies the band in each input that contains the goodness map.  If there
are fewer entries than files, the last entry in BAND is used for all remaining
files.

Specifies the threshold value for "good" status for each input.  Values
greater than or equal to the threshold are considered good.

Specifies the band in the mask file to be used.

Specifies the threshold for the mask band.  Values greater than or equal to
the threshold are considered good (unmasked).

Specifies the value to use in the output file to indicate the value is good.

Specifies the value to use in the output file if a single value is bad.
If there are fewer entries than files, the last entry in SINGLE_BAD is used
for all remaining files.

Note that multiple inputs can use the same SINGLE_BAD value, but if more than
one of these are bad, it reverts to a multi-bad situation.

Specifies the value to use in the output file to indicate more than one
input was bad.

Specifies the value to use in the output file to indicate the mask was bad.

A colon-separated list of directories in which to look for configuration
and calibration files.  Environment variables are allowed in the list
(and may themselves contain colon-separated lists).  The directories are
searched in order for each config/cal file when it is loaded.  This allows
multiple projects to be supported simultaneously, and allows the user to
override any given config/cal file.  Note that the directory structure below
the directories specified in this path must match what the project expects.
For example, Mars 98 expects flat fields to be in a subdirectory named
"flat_fields" while Mars Pathfinder expects them to be directly in the
directory specified by the path (i.e. no intermediate subdirectories).

Specifies a mission-specific pointing method to use.  Normally this
parameter is not used, in which case the "default" pointing methods
are used.  Some missions may have special, or alternate, pointing
methods available, which are indicated by this string (for example,
backlash models, using arm joint angles instead of x/y/z/az/el, etc).
A substring search is used, so multiple methods (where that makes sense)
can be specified by separating the keywords with commas.

Note that nav files created using one pointing method will most likely
not be compatible with a mosaic created using a different pointing method.

The methods available vary per mission, but some methods available at
the time of this writing are:

BACKLASH : Mars 98 SSI only.  Selects a backlash pointing model,
which adjusts the telemetered azimuth and elevation values based on
knowledge of the camera's mechanical backlash and the direction the
motor was travelling when the image was taken.

The DATA_SET_NAME typically identifies the instrument that acquired the
data, the target of that instrument, and the processing level of the data.
This value is copied to the output label, property IDENTIFICATION,
keyword DATA_SET_NAME.

The DATA_SET_ID value for a given data set or product is constructed
according to flight project naming conventions.  In most cases the
DATA_SET_ID is an abbreviation of the DATA_SET_NAME.
This value is copied to the output label, property IDENTIFICATION,
keyword DATA_SET_ID.

When a data set is released incrementally, such as every three months during
a mission, the RELEASE_ID is updated each time part of the data set is released.
For each mission(or host id if multiple spacecrafts), the first release of a data
set should have a value of "0001".
This value is copied to the output label, property IDENTIFICATION,
keyword RELEASE_ID.

Specifies a permanent, unique identifier assigned to a data product by
its producer. Most commonly, it is the filename minus the extension.
This value is copied to the output label, property IDENTIFICATION,
keyword PRODUCT_ID.

Specifies the unique identifier of an entity associated with the
production of a data set. This value is copied to the output label,
property IDENTIFICATION, keyword PRODUCER_ID.

Specifies the identity of a university, research center, NASA center or other
institution associated with the production of a data set.
This value is copied to the output label, property IDENTIFICATION, keyword
PRODUCER_INSTITUTION_NAME.

Specifies a target.  The target may be a planet, satellite, ring, region, feature,
asteroid or comet.  This value is copied to the output label, property
IDENTIFICATION, keyword TARGET_NAME.

Specifies the type of a named target. This value is copied to the output
label, property IDENTIFICATION, keyword TARGET_NAME.