HiCal
Generate radiometrically corrected HiRISE Channel products in directory: $HiRISE_ROOT/Data/HiCal
HiCal -File <pathname> -Catalog <catalog> -Id <Unique_Id> -Configuration <conf_file>
The full pathname of the ISIS cube file containing a raw HiRISE channel image
Specify the name of the configuration file such as HiCal.conf. If this is not specified then the default is $HiRISE_ROOT/Configuration/HiCal/HiCal.conf
Specify the catalog to use (default HiCat). The HiCal pipeline extrats information from the EDR_Products, Planned_Observations, and Planned_CCD_Parameters tables.
Unique Id given to temporary files located in the /tmp directory.
HiCal is the pipeline subsystem for generating radiometrically corrected HiRISE images. The input is a raw HiRISE channel image. The output will be a radiometrically corrected channel image.
This procedure continues to go through considerable evolution as the instrument calibration procedures are improved.
HiCal expects the HiRISE_ROOT environment variable specifying the root directory of the HiRISE directory tree. HiCal terminates if this environment variable does not exist.
HiCal must have a configuration file. It can be optionaly specified with the -Configruation parameter. HiCal adds the output file name to the next pipeline in the sequence. If not specified in the command line, HiCal looks for the file $HiRISE_ROOT/Configuration/HiCal/HiCal.conf. If the configuration file can not be found then HiCal will terminate.
Refer to HiCal.conf file for details on the description of the configuration parameters used by HiCal.
Please note:
Because the HiCal pipeline uses ISIS, its peferences file should be set for pipeline processing.
Group=UserInterface HistoryPath = $PWD HistoryRecording = Off EndGroup
Group = SessionLog TerminalOutput = On FileOutput = Off EndGroup
Group=ErrorFacility FileLine = on Format = PVL EndGroup
The following codes are returned by HiCal:
0; # Success value 1; # Command line error parameter 2; # Input list file does not exist 3; # Input Cube file(s) do not exit 4; # Could not create a directory 5; # ISIS processing error 6; # configuration file does not exists 7; # configuration parameter not found 8; # Data_Location failed 9; # Environment variable not set 10; # Can't make entry to next pipeline 11; # Can not delete a file 12; # File does not exist
Eric Eliason UA/LPL Richard Leis UA/LPL
Copyright(C) 2004 Arizona Board of Regents on behalf of the Lunar and
Planetary Laboratory at the University of Arizona.
The launch of the Lunar Reconnaissance Orbiter (LRO) mission from
Kennedy Space Center keeps getting delayed. The original launch date
was scheduled for this month. There have been at-risk design problems
with the Atlas 5 launch vehicle detected from previous launches and
the idea is to fix the them before using it again. There are a series
of spacecraft, including LRO, that is waiting to go once the problems
get fixed. The good news is that the LRO spacecraft is ready for
launch and once the ATLAS 5 problems get resolved, then they're good
go.
So it looks like the LRO launch will now be sometime in June, but there is not yet an exact date.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
1.47 2011/10/21 23:08:04