mex2isis Documentation

mex2isis - Convert Vicar-formatted MEX images to ISIS format
OVERVIEW

This procedure converts Vicar-formatted MEX HRSC/SRC files
to ISIS-formatted cube files.

The procedure can be used to process a single input file
(specified by the FROM parameter) or a list of files (specified
by the FROMLIST parameter).

PROCESSING WITHOUT USE OF TAE

This procedure provides an interactive interface to the PERL
scripts that perform the work involved in converting the PDS
files to ISIS cubes. The PERL scripts can also be run
standalone from the command line which makes them ideal for use
in web.html applications. There are two PERL scripts available
for converting Vicar-formatted MEX files to ISIS cubes:

mex2isis.pl, mex2isis_batch.pl

The mex2isis.pl script will process a single file for each
execution of the script. The mex2isis_batch.pl script allows you
to process a list of files for each execution of the script.

The syntax for processing a single file is as follows:

mex2isis.pl FROM=from [BASEMULT=basemult] [TRANSTAB=transtab]
[TARGDEF=targdef] [KERNLST=kernlst] [INSTPARS=inst] [LONSYS=lon]
[LATSYS=lat] [MAXLINES=maxl]

The syntax for processing a list of files is as follows:

mex2isis_batch.pl FROM=fromlist [BASEMULT=basemult] [TRANSTAB=transtab]
[TARGDEF=targdef] [KERNLST=kernlst] [INSTPARS=inst] [LONSYS=lon]
[LATSYS=lat] [MAXLINES=maxl]

All the parameters in square brackets [] above are optional. The
parameters in square brackets can be used to specify how the output
cube is created. Each parameter has a KEYWORD=value syntax associated
with it. In order to specify a parameter on the command line, you
must specify the keyword in upper case (FROM, BASEMULT, TRANSTAB,
TARGDEF, KERNLST, INSTPARS, LONSYS, LATSYS, MAXLINES) followed by an
'=' sign and the value. Do not put any spaces in the parameter
specification. The parameters can occur in any order. If an optional
parameter is not specified, then a default value will be supplied by
the Perl script.

PROCESSING AND ERROR LOGGING

If an error occurs during processing, then mex2isis.err will be
created which will contain some error-related information. The session
log file (print.prt unless the ISIS_LOG_FILE environment variable has
been set) will contain a complete history of the processing as well as
additional error information.

Programmer:  Janet Barrett, U.S.G.S., Flagstaff, 30 Mar 2004

Input Vicar filename
 (file extension required)

--

List of input Vicar filenames

--

Maximum number of lines
to put in an output HRSC
file

20000

How will core base and
multiplier be set?
(RAD,REF,STD)

STD

Name of translation
table file

--

File containing target
definitions

--

File containing kernel list

--

File containing instrument
parameters

--

Longitude system
(180,360)

360

Latitude system
(OCENTRIC,OGRAPHIC)

OCENTRIC

ADDITIONAL NOTES:

Parm	Description
FROM	This is a Vicar-formatted MEX HRSC/SRC file. The file extension must be included with the filename. If FROM is specified, then the FROMLIST parameter must be specified as the Null TAE parameter value. The output filename will automatically be created by using the 'root' input name with ".lev1.cub" appended.
FROMLIST	This specifies a file that contains a list of Vicar-formatted MEX HRSC/SRC files to be processed. The input list must be a single column file that contains one input Vicar file name per line. The file extension of the filenames in the list must be included. If FROMLIST is specified, then the FROM parameter must be specified as the Null TAE parameter value. The output filenames will automatically be created by using the 'root' input name with ".lev1.cub" appended.
MAXLINES	This is the approximate number of lines that will be put in an output HRSC file. The upper limit allowed for the MAXLINES parameter is 99000. The maximum number of lines allowed in an ISIS image is 100000. Some allowance must be made to account for missing lines that must be filled in during the latter part of the processing. This is why MAXLINES is limited to 99000 instead of 100000. The MAXLINES parameter is ignored if the input file is an SRC file.
BASEMULT	Determines how the CORE_BASE and CORE_MULTIPLIER will be set when the MEX image gets converted to ISIS. If you set BASEMULT=RAD, then the core base will be set to the RADIANCE_OFFSET value and the core multiplier will be set to the RADIANCE_SCALING_FACTOR value. If the ABSOLUTE_FLUX_CALIB_FLAG is set to N, then the radiance scaling is no good and your request of BASEMULT=RAD will be ignored. Instead, the core base and multiplier will be set to 0 and 1. If you set BASEMULT=REF, then the core base will be set to 0 and the core multiplier will be set to the REFLECTANCE_SCALING_FACTOR value. If you set BASEMULT=STD, then the core base will be set to 0 and the core multiplier will be set to 1.
TRANSTAB	This is the translation table to be used by pds2isis for translating PDS labels keywords to ISIS label keywords. The default is to use the latest version of the mex2isis_translation.def file in $ISISMEXDATA.
TARGDEF	This is the target definition file to be used by levinit for acquiring information specific to Mars. The default is to use $ISISDATA/targets/mars.def.# where # specifies the latest version of the file available.
KERNLST	This is the kernel list file to be used by levinit for acquiring the names and locations of SPICE kernels for the MEX images.
INSTPARS	This is the instrument parameters file to be used by levinit for obtaining instrument specific information about the MEX SRC/HRSC instruments.
LONSYS	This is the longitude system that will be used when the output image is processed by other ISIS programs. The valid values are 180 and 360. The default is 360 which implies that longitudes will be in the range 0 to 360 for the image. A longitude system of 180 implies that longitudes will be in the range -180 to 180 for the image.
LATSYS	This is the latitude system that will be used when the output image is processed by other ISIS programs. The valid values are OGRAPHIC and OCENTRIC. The default is OCENTRIC.