Level 2 Help for PLUMAGE

Input files contain the labels from which the PLACES information is extracted.
Although the program is intended to work for EDR's, most RDR's have the proper
labels and could be used instead.

The input files can be listed on the command line, or in a list file, as with
the MARS mosaic programs.

The output XML file, suitable for upload into PLACES.

Override for the user name in the generated XML.

Override the "method" documentation string in the generated XML.  If
set to null (method=--) then the method will be omitted.  Normally the
image's PRODUCT_ID is appended to this string, unless -NO_PRODUCT_ID is
specified.

Override the "institution" documentation string in the generated XML.  If
set to null (institution=--) then the institution will be omitted.

Override for the product ID field.  The product ID is appended to the mission
string, unless -NO_PRODUCT_ID is specified, and is intended to provide
traceability to the source of the data.  This parameter should not normally
be used; the default is to extract PRODUCT_ID from the label, which is more
appropriate.  Specifically, this parameter should not be used when multiple
files are being processed, because all files would then share the same
product ID.

Turns on or off the <trace> element.  This is a documentation-only element that
is ignored by PLACES.  It exists to help trace down where potentially bad
information in the XML file came from, for anomaly tracking.

Turns on or off the <origination> tag.  This contains metadata including
user, method, and institution.  Because this metadata is currently associated
with the solution ID (always "telemetry" here), it really has no purpose.
If PLACES is changed to keep metadata with each solution, this can be
re-enabled.

The practical effect of this is that, if -NO_ORIG is in effect, the only
other parameters that matter are INP, OUT, and MISSION.  Everything else
is ignored.

Normally, the product ID (from the label, or PRODUCT_ID override) is appended
to the "method" string in the generated XML, in order to provide traceability
to the source of the data.  This keyword (via -NO_PRODUCT_ID) can be used to
disable this appending.  Note that the text of "method" should be adjusted in
this case, since it is written assuming the product ID will follow.

Normally, SITE_COORDINATE_SYSTEM groups are examined, and unique sites are
output along with the normal rover frames.  Specifying -NO_SITE turns this
off, ignoring site coordinate systems.  Note that it is not an error for
the site group to be missing from the label.

Normally, the joint angles in various articulation device labels are examined
and output along with the pose solutions.  This can be disabled via
-NO_MECHANISMS.

Normally, the exposure time and nstrument ID of images are written to an
<observation> element.  This can be disabled via -NO_OBSERVATION.

If the -DO_MSL_INIT flag is set, then the program will first look at the
INITIAL_STATE_PARMS group for the ROVER_MOTION_COUNTER and Rover position
and orientation.  If not found, it will revert to the standard labels.  This
allows PLUMAGE to find the "initial" state before visodom is run for those
kind of images.  The flag only applies to MSL images, but it is "safe"
for all MSL images.  It is ignored for other missions.

If provided, specifies a minimum SCLK threshold.  Any images with a SCLK
below this value will be ignored.

If provided, specifies a maximum SCLK threshold.  Any images with a SCLK
above this value will be ignored.

The ADD_SITE parameter adds the given number to all Site indices.  The intent
is to be able to interact with the development PLACES server using "fresh"
Site territory (i.e. a range of sites not cluttered with previous data).
It should obviously never be used in operations.