##########################################
Details about footprint pre-processing job
DT - 20-01-2017
##########################################

HIFI: scripts run: 
	* hifi_header.py with list hifi_list.dat
	* hifi_pointing.py with list hifi_list.dat

SPIRE-S: scripts run: 
	* pire_spectro_header.py with list spire.spectro
	* spire_spectro1_pointing.py with list spire.spectro
	* NOTE: script spire_spectro_raster_pointing.py could not be run as
	list file spire_spectro_raster.list was not provided

SPIRE-P: scripts run
	* spire_photo_header.py with list spire.photo
	* spire_photo_pointing.py with list spire.photo

PACS-S: scripts run
	* pacs_spectro_header.py with list pacs.lines
	* pacs_spectro_pointing.py with list pacs.lines

PACS-P: scripts run
	* pacs_photo_header.py with list pacs.photo
	* pacs_photo_pointing.py with list pacs.photo

SPIRE/PACS PARALLEL: scripts run
	* parallel_header.py with list parallel.pacs


####################
Remarks:

 * PARALLEL mode:
	- I am assuming that the header info only needs to be generated based on the PACS instrument (as the parallel_header.py script does) and that the SPIRE info would be the same. As a matter of fact, if I use parallel_header.py and fetch the obsid with instrument=SPIRE, the script does not work
	- there was no script specific to parallel mode for the pointing information. I have assumed that this is covered in the respective obsid lists for SPIRE-P and PACS-P and therefore is part of the pointing files for those sub-instruments.

 * SPIRE-S raster maps:
	- there was no obsid list specific to SPIRE-S raster maps, however I was given a dedicated script (spire_spectro_raster_pointing.py) that assumes availability of spire_spectro_raster.list. I have assumed that those obsids are already contained in the spire.spectro list