UniHIPE is a tool that produces fits file in the format required by Unimap.
Using UniHIPE you can also launch directly Unimap and generate the final maps.
The tool requires HIPE (v.12 or greater) installed in your computer. In order to install HIPE follow the link: http://www.cosmos.esa.int/web/herschel/hipe-download
To generate final maps you have to install Unimap:to install Unimap follow the link http://infocom.uniroma1.it/unimap/
To install UniHIPE:
Now UniHIPE is added to the HIPE task list (look for uniHipe under SPIRE or PACS task list).
Double click on uniHipe in the task list opens the plugin GUI. A brief description of the parameters available to the users is provided here. The description follow the GUI division: the GUI is divided in three sections: Main, UniHIPE and Unimap.
In the main tab you have to define main inputs for the UniHIPE/Unimap process
obsidList: the list of the obsid that you want process using UniHIPE and Unimap:
tag: the name to identify the UniHIPE run (if not set the default is a combination of obsids name, e.g. obsid1_obsid2)
inOutDir (MANDATORY): in this directory will be stored the fits file in the format required by Unimap generated UniHIPE and the final maps produced by Unimap.
instrument (MANDATORY): select between SPIRE and PACS
batchExec (default value: False): select it to exec the task in batch mode. If is set and store is set to Local Directory you have to provide a list of directory where the level1 fits files are stored using location parameter (see below)
batchExec = False
execUniHipe (default value: True): if selected UniHIPE is used to produce the level1 data in the format expected by Unimap. If set, you have to provide also values for the specific UniHipe parameters (see description of these parameters below in the section UniHipe Tab. You can deselect it f you have already generated the level1 data and you want execute only Unimap.
execUnimap (default value: False): select it to execute the Unimap process and generate the maps. If set, you have to provide also values for the specific Unimap parameters (see description of these parameters below in the section Unimap Tab.
In the UniHipe tab you have to define specific inputs for the UniHIPE process, i.e. the process that convert standard SPIRE/PACS level1 into Unimap input format.
type: select the type of process: i.e. from where starts the SPIRE process or which PACS band process. Possible values are:
pacs_blue: converts level1 PACS blue band
store: where the products to convert are stored. Possible values are:
Local Directory: the products are stored in a local directory outside the HIPE local store. If the parameter is set to Local Directory you have to provide a list of directory (one for each obsid in obsList). If the task is executed in interactive way (i.e. batchExec is set to false) a popup window will be open and you will select the directories using the GUI interface. Otherwise you have to provide a list of directories using the "location" parameter (see below).
location: if store is set to Local Store you can use this parameter to provide the name of the local store. Only if the store parameter (see above) is set to Local Directory, you have to provide a list of directory (separated by a comma) where the level1 data are stored as for the following example:
updateCal (only for SPIRE data): if set to True, the calibration tree attached to the observations is updated using the last calibration tree available locally (i.e. the last tree stored on your machine) and it will be used when the data are reprocessed from level0 or level0_5.
updateCal = True
In the Unimap tab you have to define specific inputs for the Unimap process, i.e. the process that convert level1 generated by UniHIPE process in the final maps.
mcrDir: location of the MATLAB runtime.
unimapDir: where Unimap is installed
spireArray and pacsArray: the SPIRE/PACS band to process with Unimap. For SPIRE, if you select ALL, all the three bands are processed.
filterSize: pgls high pass filter size in arcsec
noiseFilterType: Noise Filter Type. Possible values:
5 fit avefilt
startImage: Starting image for the gls (default value: 1). Possible values:
wglsDThreshold: Threshold to detect an artifact (lower values = more artifacts)
wglsGThreshold: Threshold to grow an artifact (lower values= wider artifacts)
loadWglsImage: Select it to load final WGLS image generated by Unimap in the HIPE session.
(Note that many others parameters for Unimap are modifiable by the user changing the unimap_par.txt file available in the directory where the Unimap is installed on your machine)
You can execute UniHIPE in interactive mode, setting all parameters via GUI ad described above or you can call it via command line writing a simple jython script.
An example of jython script is provided with the plugin and is available under HIPE menu > Tools > UniHipe Plugin.
To execute the jython script via command line you have to type:
To allocate, e.g, 6gb of memory to the process:
hipe -Xmx6g myUniHipeScript.py
UniHipe creates the FITS files for Unimap (unimap_obsid_<instrument>_<array>_<tag>.fits) in the subdirectory "tag" within the inOutDir directory. It also generates an auxiliary file "unimap_meta.dat" that will be managed by unimap to create the fits header
Unimap, if called, generates the final maps with the name unimap_<array>.fits: this is an image that stores all the maps generated by different Unimap steps as different layers. For a description on how Unimap works, please refers to Unimap website.
Write a e-mail to Fabiana FaustinI firstname.lastname@example.org
Comments and suggestions are welcome!
UniHipe is developed by SSDC (ASI Space Science Data Center) www.ssdc.asi.it
The SSDC is a facility managed by the Italian Space Agency, ASI
If you research benefits from the use of SSDC, we would appreciate the following acwnoledgment in your paper:
Part of this work based on archival data, software or online services provided by the ASI SPACE SCIENCE DATA CENTER (SSDC)