|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
| |
< < | Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here: | > > | Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here: | | |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < | | > > | HIPE (Herschel Interactive Processing Environment): The latest User Release version that you should use for reducing SPIRE data can be downloaded from this link . | | | |
< < |
- We also provide access to the latest stable developer build (latest stable CIB).
| > > | | | | |
< < |
- Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here:
| > > | Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here: | | | |
The SPIRE Launch Pads | |
< < |
- The SPIRE Launch Pads are single sheet quick entries (like a cheat sheet) into SPIRE data reduction and providing quick references to the relevant sections in the SPIRE Data Reduction Guide. There are launch pads for Data Access, SPIRE Photometer and Spectrometer data reduction.
| > > | The SPIRE Launch Pads are single sheet quick entries (like a cheat sheet) into SPIRE data reduction and providing quick references to the relevant sections in the SPIRE Data Reduction Guide. There are launch pads for Data Access, SPIRE Photometer and Spectrometer data reduction. | |
|
META TOPICPARENT |
name="WebHome" |
- The currently available user contributed scripts and plugins are listed here
.
| |
< < | | > > |
- Users are welcome to submit scripts and software that they believe could be of general interest to the community to the Herschel helpdesk.
| |
Further information |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
- The currently available user contributed scripts and plugins are listed here
.
- Users are welcome to submit scripts and software that they believe could be of general interest to the community to the Herschel http://herschel.esac.esa.int/esupport/Helpdesk.
| |
Further information |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
SPIRE Spectrometer | |
< < | | > > | | |
- Calibration of the Herschel SPIRE Fourier Transform Spectrometer
, Swinyard et al., 2014, MNRAS, 440, 3658
- Observing extended sources with the Herschel SPIRE Fourier Transform Spectrometer
, Wu et al., 2013, A&A, 556, 116
- Beam profile for the Herschel-SPIRE Fourier transform spectrometer
, Makiwa et al., 2013, Applied Optics, 52, 3864
| |
- We also provide access to the latest stable developer build (latest stable CIB).
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
Please contact the Herschel helpdesk if you plan to use a developer build as there may be some additional information needed in order for you to properly make use of it.
| |
< < |
- Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here:
| > > |
- Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here:
| | | |
< < |
- SPIA: The SPIRE Photometer Interactive Analysis (SPIA) package is available in HIPE (previously it was a plugin). SPIA provides a structured GUI based access to the more intricate parts of the scan map photometer pipeline for SPIRE without the immediate need to resort to scripts. More information can be found in the SDRG or on the SPIA web page
* Note: A bug that renders two deglitchers in the task spiaLevel1 unusable was found only recently. We have prepared a quick fix that will work on a standard HIPE 12.1 installation. Please see the SPIA web page for more information.
| > > | <-- * SPIA: The SPIRE Photometer Interactive Analysis (SPIA) package is available in HIPE (previously it was a plugin). SPIA provides a structured GUI based access to the more intricate parts of the scan map photometer pipeline for SPIRE without the immediate need to resort to scripts. More information can be found in the SDRG or on the SPIA web page
* Note: A bug that renders two deglitchers in the task spiaLevel1 unusable was found only recently. We have prepared a quick fix that will work on a standard HIPE 12.1 installation. Please see the SPIA web page for more information. --> | |
The SPIRE Launch Pads | |
Spectrometer Overview | |
< < | The best source of information for reducing SPIRE Spectrometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific types of sources: | > > | The best source of information for reducing SPIRE Spectrometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific types of sources: | |
- Faint (<10 Jy) and medium (<100 Jy) strength sources
- Bright sources (>500 Jy)
| |
SPIRE Calibration Tree (& release note) |
Release Date |
Applicable HIPE Version |
Comment |
| |
< < |
SPIRE_CAL_13_1 |
Apr 2015 |
HIPE v13.0 |
Calibration tree currently used in operations |
| > > |
SPIRE_CAL_14_2 |
Dec 2015 |
HIPE v14.0 |
Calibration tree currently used in operations |
SPIRE_CAL_13_1 |
Apr 2015 |
HIPE v13.0 |
Calibration tree currently used in operations |
| |
| |
Details of individual calibration products can be found here. | |
< < |
- Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_13_1") etc. The default (applicable to the HIPE version in use) can be obtained with cal = spireCal(calTree="spire_cal") . It can then be saved to a local pool right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
| > > |
- Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_14_2") etc. The default (applicable to the HIPE version in use) can be obtained with cal = spireCal(calTree="spire_cal") . It can then be saved to a local pool right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
| |
- Alternatively, the latest calibration tree for SPIRE can be obtained as a jar file from Latest calibration trees
. Then, you have to possibilities to read and save:
| |
< < |
-
- The jar file can be load directly into HIPE with the command:
cal = spireCal(jarFile="PATH_TO_FILE/spire_cal_13_1.jar") . To save it to a local pool, proceed as described above, right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- The jar file can also be saved directly to a local pool without opening HIPE, running the following command in the terminal command line:
cal_import PATH_TO_FILE/spire_cal_13_1.jar . Then, to load the calibration tree in HIPE, simply type: cal = spireCal(pool="spire_cal_13_1")
| > > |
-
- The jar file can be load directly into HIPE with the command:
cal = spireCal(jarFile="PATH_TO_FILE/spire_cal_14_2.jar") . To save it to a local pool, proceed as described above, right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- The jar file can also be saved directly to a local pool without opening HIPE, running the following command in the terminal command line:
cal_import PATH_TO_FILE/spire_cal_14_2.jar . Then, to load the calibration tree in HIPE, simply type: cal = spireCal(pool="spire_cal_14_2")
| |
See the SPIRE Data Reduction Guide for more details. | | <-- * Additionally repeatability of measured photometry to flux densities >100mJy ~ 2% -->
| |
< < |
-
- These are available in the SPIRE calibration context, at the standard map pixel size of (6,10,14) arcsec/pixel for (250,350,500) µm bands, and can be accessed in HIPE after a calibration context has been loaded (see above).
- A more detailed analysis of the SPIRE beam profile data was undertaken in 2012, leading to revised values for beam profile solid angles and derivation of a semi empirical wavelength dependent beam profile model. The results at a scale of 1 arcsec/pixel as well as the data needed for the model are available for download. A detailed description of the analysis is given as well.
-
A final analysis of the SPIRE beam profiles was completed in Oct 2014, taking into account so called "shadow" observations that were taken after Neptune had moved away. This dramatically reduced the uncertainties in the beam profile solid angles to better than 1%. It also eliminated the need for a "static" part in the semi-empirical beam profile model. The results at a scale of 1 arcsec/pixel as well as the data needed for the model are available for download. A detailed description of the analysis is available too.
<-- * The observed beams at much finer scale of 1 arcsec/pixel, as well as the theoretical ones, are available from here . Please read the release note for more details. --> | > > |
-
-
A final analysis of the SPIRE beam profiles was completed in Oct 2014, taking into account so called "shadow" observations that were taken after Neptune had moved away. This dramatically reduced the uncertainties in the beam profile solid angles to better than 1%. It also eliminated the need for a "static" part in the semi-empirical beam profile model. The results at a scale of 1 arcsec/pixel as well as the data needed for the model are available for download. A detailed description of the analysis is available too.
- These new beam maps and radial profiles are available also in the latest SPIRE calibration tree (
BeamProf , RadialCorrBeam ).
<-- * These are available in the SPIRE calibration context, at 1 arcsec/pixel as well as with the standard map pixel size of (6,10,14) arcsec/pixel for (250,350,500) µm bands, and can be accessed in HIPE after a calibration context has been loaded (see above).
-
- A more detailed analysis of the SPIRE beam profile data was undertaken in 2012, leading to revised values for beam profile solid angles and derivation of a semi empirical wavelength dependent beam profile model. The results at a scale of 1 arcsec/pixel as well as the data needed for the model are available for download. A detailed description of the analysis is given as well. -->
| |
- SPIRE Photometer filter transmission curves:
| |
< < |
-
- These are also available in the SPIRE calibration context (photRsrf) and can be accessed in HIPE after a calibration context has been loaded (See above).
| > > |
-
- These are available in the SPIRE calibration context (
photRsrf ).
| |
- Neptune and Uranus models used for the SPIRE photometer flux calibration:
| |
< < |
-
- The ESA2 models used up to HIPE v10 and
spire_cal_10_1 , are available here .
| |
-
-
The ESA4 models used from HIPE v11 and spire_cal_11_0 , are available here .
| |
> > |
-
- The ESA2 models used up to HIPE v10 and
spire_cal_10_1 , are available here .
| |
Spectrometer calibration and uncertainties | |
-
- Calibration uncertainties, which should be included in addition to the statistical errors of any measurement from HIPE v11 onwards, are as follows:
- Point sources observed on the centre detectors (SSWD4 and SLWC3): the measured repeatability is 6%, with the following contributions: (i) absolute systematic uncertainty in the models from comparison of Uranus and Neptune - determined to be ±3%; (i) the statistical repeatability determined from observations of Uranus and Neptune, with pointing corrected - estimated at ±1% (excluding the edges of the bands); (iii) the uncertainties in the instrument and telescope model, which lead to an additive continuum offset error of 0.4 Jy for SLW and 0.3 Jy for SSW and (iv) the effect of the Herschel APE.
- Sparse observations of significantly extended sources:
| |
< < |
-
-
-
- the absolute uncertainty in intensity for a reasonably bright, fully extended object, observed in the central detectors is, in theory, ±1%, with the following contributions: (i) the systematic uncertainty in telescope model of 0.06%; (ii) the statistical repeatability estimated at ±1% and (iii) an additive continuum offset of 3.4x10-20 W/m2/Hz/sr for SLW and 1.1x10-19 W/m2/Hz/sr for SSW.
- In practice, truly extended sources tend to be faint and the uncertainty is therefore dominated by the additive offsets. When the source extent is larger than the main beam size, but not fully extended, or if there is structure inside the beam, then the uncertainties are dominated by the source-beam coupling ( see Wu et al. 2013
) and are significantly greater than 1%.
| > > |
-
-
-
- the conservative absolute uncertainty in intensity for a reasonably bright, fully extended object, observed in the central detectors is of the order of 10%, with the following contributions: (i) the systematic uncertainty in telescope model of 0.06%; (ii) the statistical repeatability estimated at ±1% (iii) an additive continuum offset of 3.4x10-20 W/m2/Hz/sr for SLW and 1.1x10-19 W/m2/Hz/sr for SSW and (iv) far-field feehorn efficiency correction of the order of 10% (conservative).
- When the source extent is larger than the main beam size, but not fully extended, or if there is structure inside the beam, then the uncertainties are dominated by the source-beam coupling ( see Wu et al. 2013
) and are greater than ±10%.
| |
-
-
- Mapping mode: the variations between detectors becomes important and the overall repeatability has been measured as ±7% (see Benielli et al., 2014
for a full discussion of mapping mode observations). The off-axis detectors are less well calibrated, especially outside the unvignetted part of the field.
- Uranus model used for the SPIRE FTS point-source flux calibration:
|
|
META TOPICPARENT |
name="WebHome" |
| |
> > | Spectrometer data reduction | | | |
< < | Spectrometer data reduction | > > | Spectrometer Overview | | | |
< < | Spectrometer Overview | | The best source of information for reducing SPIRE Spectrometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific types of sources: | |
< < |
- Faint (<10 Jy) and medium (<100 Jy) strength sources
- Bright sources (>500 Jy)
| > > |
- Faint (<10 Jy) and medium (<100 Jy) strength sources
- Bright sources (>500 Jy)
| |
- Semi-extended sources
- Spectral mapping observations
- Observations with few repetitions
For faint sources, the subtraction of instrument, telescope and background emission is particularly important. Optimum subtraction can be performed in several ways (read the SPIRE Data Reduction Guide for details): | |
< < |
- Subtract the Dark Sky spectrum closest to your observation (use the "Background Subtraction" script in HIPE)
- Subtract the spectrum of surrounding detectors (use the "Background Subtraction" script in HIPE)
| > > |
- Subtract the Dark Sky spectrum closest to your observation (use the "Background Subtraction" script in HIPE)
- Subtract the spectrum of surrounding detectors (use the "Background Subtraction" script in HIPE)
| |
Dark Sky observations are observed on every SPIRE Spectrometer OD, and are all public in the Archive. | |
< < | A listing of the available Dark Sky observations can be found here. | > > | A listing of the available Dark Sky observations can be found here. | | | |
< < | Spectrometer Data Processing Issues | > > | Spectrometer Data Processing Issues | |
The SPIRE Spectrometer DP known issues listed here. | |
--> | |
> > | Photometer data reduction | | | |
> > | Photometer Overview | | | |
< < | Photometer data reduction
Photometer Overview | | The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available as a standalone hyperlink document as well as through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered. | |
< < |
Photometer Data Processing Issues | > > | Photometer Data Processing Issues | |
The SPIRE Photometer DP known issues listed here. | |
--> | |
< < | Known Issues in ODs 1304 & 1305 | > > | Known Issues in ODs 1304 & 1305 | |
For (yet) unknown reasons, the three detectors PSW-B5, PSW-E9 and PSW-F8 - that use to behave well during the entire mission - were noisy during the two operational days 1304 and 1305. The result are stripes visible in the final PSW map which the current (HIPE 11) pipeline is not able to correct. The solution is to mask and exclude these detectors from the analysis. This could be done in 2 ways: | |
< < |
- You can use the
SpireMaskEditor GUI as described in Sec. 8.4 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to Master all samples in all scans (listed as BBID) for the detectors mentioned above.
- Alternatively, you can use these lines of code
| > > |
- You can use the
SpireMaskEditor GUI as described in Sec. 8.4 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to Master all samples in all scans (listed as BBID) for the detectors mentioned above.
- Alternatively, you can use these lines of code
| |
- After either of those cases, you must then re-run level 1 to 2 steps on the newly modified level1 product. If your observation has been already re-reduced with HIPE 11, original and new level1s are already destriped, so you can directly run the naive map-maker on the new level1. Otherwise, you must run the destriper step: check the pipeline script for details.
| |
< < |
Planck-HFI & Herschel-SPIRE cross calibration: absolute offset re-processing | > > | Planck-HFI & Herschel-SPIRE cross calibration: absolute offset re-processing | |
As of HCSS 11, a new task named zeroPointCorrection is available to the users: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. | | A detailed descirption of the algorithm used for the cross-calibration with Planck and implemented in the zeroPointCorrection is described in the HIPE 11 SPIRE Data Reduction Guide, sec. 4.10.
--> | |
< < | Source Extraction and Photometry | > > | Source Extraction and Photometry | |
- The current recommended method for photometry
sourceExtractorTimeline task (formerly known as the Timeline Fitter) which works on the detector timelines. The Map based algorithm sourceExtractorSussex (SUSSEXtractor) providers good results and is useful on larger maps where the sourceExtractorTimeline will be significantly slower. sourceExtractorDaophot (DAOphot) also provides a reasonable estimate of the source flux but may require an aperture correction.
- Photometry on single direction fast scan parallel mode maps:
| |
< < |
-
- The photometry on single scan direction fast parallel mode results in higher photometric errors of up to 5 percent for aperture photometry compared to nominal speed and cross linked maps. The best results are obtained using the Timeline Fitter. Wherever possible orthogonal and nominal direction parallel scans should be merged.
| > > |
-
- The photometry on single scan direction fast parallel mode results in higher photometric errors of up to 5 percent for aperture photometry compared to nominal speed and cross linked maps. The best results are obtained using the Timeline Fitter. Wherever possible orthogonal and nominal direction parallel scans should be merged.
| |
-
- Currently no astrometry correction is made during the merging process for parallel maps. For fast parallel mode an astrometry offset may be present which can in cases where there is a large offset, result in reduced photometers accuracy of the order of up to 25% compared to large cross-linked scan maps.
| |
< < | | |
- In HIPE13 (and HIPE 11), the default PRF used by SUSSEXtractor has a size of 5x5 pixels. In HIPE 12, a PRF of size 13x13 was used to allow a more complete coverage of the PRF edges, but this lead to some secondary effects that negatively affected the measured flux densities. If you use HIPE v12 we advise you to change the input PRF size using this script, in order to obtain the same photometry as in HIPE v13.
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
| |
Known Issues in ODs 1304 & 1305 | |
Details on how to run the task are available in the SPIRE Data Reduction Guide, Section 6.8 | |
> > | Be aware that for small size SPIRE maps, smaller than ~30 arcmin, the zero-offset can be rather uncertain, due to the large Planck beam (8 arcmin). In such cases the interpretation of the zero offset as the absolute zero level must to be treated with caution. | | <-- Herschel-SPIRE detectors are only sensitive to relative variations, and so as a consequence, the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. The Planck-HFI detectors are similar to the SPIRE ones, but the Planck observing strategy allowed it to (almost) observe a great circle on the sky every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by ~10%.
--> | |
- Photometry on single direction fast scan parallel mode maps: The photometry on single scan direction fast parallel mode results in higher photometric errors of up to 5 percent for aperture photometry compared to nominal speed and cross linked maps. The best results are obtained using the Timeline Fitter. Wherever possible orthogonal and nominal direction parallel scans should be merged.
| |
< < |
- Between HIPE11 and HIPE12 default size of the PRF used by SUSSEXtractor was changes from a 5x5 PRF to a 13x13 PRF to allow a more complete coverage of the PRF edges. Note that this change has an effect on the resulting flux densities measured by SUSSEXtractor with the HIPE 12 results being systematically higher by about 10 % compared to Timeline Fitter. Caution is advised using SUSSEXtractor with HIPE12. The original HIPE11 results can be replicated by this script
| > > |
- In HIPE13 (and HIPE 11), the default PRF used by SUSSEXtractor has a size of 5x5 pixels. In HIPE 12, a PRF of size 13x13 was used to allow a more complete coverage of the PRF edges, but this lead to some secondary effects that negatively affected the measured flux densities. If you use HIPE v12 we advise you to change the input PRF size using this script, in order to obtain the same photometry as in HIPE v13.
<-- * In HIPE13 (and HIPE 11), the default size of the PRF used by SUSSEXtractor has a size of 5x5 pixels. In HIPE 12, a PRF of size 13x13 was used to allow a more complete coverage of the PRF edges, but this lead to some secondary effects that negatively affected the flux densities measured by SUSSEXtractor. The original HIPE11/13 results can be replicated by this script
--> | |
SPIRE report from the January 2013 HSC Map Making Workshop |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Documents explaining SPIRE | |
< < | A quick guide to the SPIRE instrument is provided in the SPIRE fact sheet | > > | A quick guide to the SPIRE instrument is provided in the SPIRE fact sheet.
Note that the SPIRE Spectrometer information in the fact sheet is outdate. Please use this up-to-date fact sheet for the Spectrometer. | |
SPIRE Handbook and SPIRE Data Reduction Guide
| |
< < | | > > | | |
Documents with relevance to the SPIRE calibration: | | SPIRE Spectrometer | |
< < | | > > | | |
- Calibration of the Herschel SPIRE Fourier Transform Spectrometer
, Swinyard et al., 2014, MNRAS, 440, 3658
- Observing extended sources with the Herschel SPIRE Fourier Transform Spectrometer
, Wu et al., 2013, A&A, 556, 116
- Beam profile for the Herschel-SPIRE Fourier transform spectrometer
, Makiwa et al., 2013, Applied Optics, 52, 3864
| |
Historical papers | |
< < | Some values on the performance and calibration in these papers are outdated. Please consult the latest SPIRE Data Reduction Guide or the SPIRE Handbook for most up to date information. | > > | Some values on the performance and calibration in these papers are outdated. Please consult the latest SPIRE Data Reduction Guide or the SPIRE Handbook for most up to date information. | |
- The Herschel-SPIRE instrument and its in-flight performance, Griffin et al., 2010, A&A, 518, L3
- In-flight calibration of the Herschel-SPIRE instrument: Swinyard et al., 2010, A&A, 518, L4,
| | Photometer data reduction
Overview | |
< < | The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available as a standalone hyperlink document as well as through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered. | > > | The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available as a standalone hyperlink document as well as through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered. | |
Data Processing Issues | |
SPIRE Calibration Tree (& release note) |
Release Date |
Applicable HIPE Version |
Comment |
| |
< < |
SPIRE_CAL_12_3 |
May 2014 |
HIPE v12.1 |
Calibration tree currently used in operations |
| > > |
| |
| |
Details of individual calibration products can be found here. | |
< < |
- Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_12_3") etc. The default (applicable to the HIPE version in use) can be obtained with cal = spireCal(calTree="spire_cal") . It can then be saved to a local pool right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
| > > |
- Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_13_1") etc. The default (applicable to the HIPE version in use) can be obtained with cal = spireCal(calTree="spire_cal") . It can then be saved to a local pool right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
| |
- Alternatively, the latest calibration tree for SPIRE can be obtained as a jar file from Latest calibration trees
. Then, you have to possibilities to read and save:
| |
< < |
-
- The jar file can be load directly into HIPE with the command:
cal = spireCal(jarFile="PATH_TO_FILE/spire_cal_12_3.jar") . To save it to a local pool, proceed as described above, right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- The jar file can also be saved directly to a local pool without opening HIPE, running the following command in the terminal command line:
cal_import PATH_TO_FILE/spire_cal_12_3.jar . Then, to load the calibration tree in HIPE, simply type: cal = spireCal(pool="spire_cal_12_3")
| > > |
-
- The jar file can be load directly into HIPE with the command:
cal = spireCal(jarFile="PATH_TO_FILE/spire_cal_13_1.jar") . To save it to a local pool, proceed as described above, right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- The jar file can also be saved directly to a local pool without opening HIPE, running the following command in the terminal command line:
cal_import PATH_TO_FILE/spire_cal_13_1.jar . Then, to load the calibration tree in HIPE, simply type: cal = spireCal(pool="spire_cal_13_1")
| |
See the SPIRE Data Reduction Guide for more details. | |
Spectrometer calibration and uncertainties | |
< < | | > > | | |
-
- Calibration uncertainties, which should be included in addition to the statistical errors of any measurement from HIPE v11 onwards, are as follows:
- Point sources observed on the centre detectors (SSWD4 and SLWC3): the measured repeatability is 6%, with the following contributions: (i) absolute systematic uncertainty in the models from comparison of Uranus and Neptune - determined to be ±3%; (i) the statistical repeatability determined from observations of Uranus and Neptune, with pointing corrected - estimated at ±1% (excluding the edges of the bands); (iii) the uncertainties in the instrument and telescope model, which lead to an additive continuum offset error of 0.4 Jy for SLW and 0.3 Jy for SSW and (iv) the effect of the Herschel APE.
- Sparse observations of significantly extended sources:
- the absolute uncertainty in intensity for a reasonably bright, fully extended object, observed in the central detectors is, in theory, ±1%, with the following contributions: (i) the systematic uncertainty in telescope model of 0.06%; (ii) the statistical repeatability estimated at ±1% and (iii) an additive continuum offset of 3.4x10-20 W/m2/Hz/sr for SLW and 1.1x10-19 W/m2/Hz/sr for SSW.
- In practice, truly extended sources tend to be faint and the uncertainty is therefore dominated by the additive offsets. When the source extent is larger than the main beam size, but not fully extended, or if there is structure inside the beam, then the uncertainties are dominated by the source-beam coupling (see Wu et al. 2013
) and are significantly greater than 1%.
| |
< < |
-
-
- Mapping mode: the variations between detectors becomes important and the overall repeatability has been measured as ±7% (see Benielli et al. 2013, submitted, for a full discussion of mapping mode observations). The off-axis detectors are less well calibrated, especially outside the unvignetted part of the field.
| > > |
-
-
- Mapping mode: the variations between detectors becomes important and the overall repeatability has been measured as ±7% (see Benielli et al., 2014
for a full discussion of mapping mode observations). The off-axis detectors are less well calibrated, especially outside the unvignetted part of the field.
| |
- Uranus model used for the SPIRE FTS point-source flux calibration:
- The ESA4 model, used from HIPE v10 onwards, is available here
.
| | Contact the Helpdesk | |
< < | | > > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE FTS fact sheet v10" date="1428659261" name="FTS-flyer-landscape_v11_A4.pdf" path="FTS-flyer-landscape_v11_A4.pdf" size="1710010" user="Main.IvanV" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1376316561" name="zeroPointCorr_HIPE11.py.txt" path="zeroPointCorr_HIPE11.py.txt" size="2765" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.7" date="1345816678" name="SPIRE_SpectrometerLaunchPad_v1.7.pdf" path="SPIRE_SpectrometerLaunchPad_v1.7.pdf" size="195133" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1376316527" name="zeroPointCorr_HIPE10.py.txt" path="zeroPointCorr_HIPE10.py.txt" size="2814" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE FTS fact sheet v10" date="1428658242" name="FTS-flyer-landscape_v10_A4.pdf" path="FTS-flyer-landscape_v10_A4.pdf" size="1709830" user="Main.IvanV" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="Script to correct photometer data in ODs 1304/1305" date="1374833050" name="correct_od1304_1305.py.txt" path="correct_od1304_1305.py.txt" size="610" user="Main.EdwardPolehampton" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE A&A paper, Griifin et al 2010" date="1295862676" name="aa14519-10.pdf" path="aa14519-10.pdf" size="1353253" user="Main.AnthonyMarston" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
|
META TOPICPARENT |
name="WebHome" |
| |
> > | <--
- Set CURRENT_DOC_BUILD = hcss-doc-12.0 -->
| | SPIRE instrument and calibration web pages
| |
| |
-
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
Please contact the Herschel helpdesk if you plan to use a developer build as there may be some additional information needed in order for you to properly make use of it.
- Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here:
| |
< < | | > > | | |
- SPIA: The SPIRE Photometer Interactive Analysis (SPIA) package is available as a plug-in for HIPE. SPIA provides a structured GUI based access to the more intricate parts of the scan map photometer pipeline for SPIRE without the immediate need to resort to scripts. More information can be found in the SDRG or on the SPIA web page
The SPIRE Launch Pads | |
< < |
- The SPIRE Launch Pads are single sheet quick entries (like a cheat sheet) into SPIRE data reduction and providing quick references to the relevant sections in the SPIRE Data Reduction Guide. There are launch pads for Data Access, SPIRE Photometer and Spectrometer data reduction.
| > > |
- The SPIRE Launch Pads are single sheet quick entries (like a cheat sheet) into SPIRE data reduction and providing quick references to the relevant sections in the SPIRE Data Reduction Guide. There are launch pads for Data Access, SPIRE Photometer and Spectrometer data reduction.
| |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
SPIRE_CAL_1_2 |
HIPE v1 |
Phot flux conv based on Ceres |
(SPIRE_CAL_1_1) |
HIPE v1 |
Pre-launch dummy values |
| |
< < | More details of the changes in each version are given here . | > > | Details of individual calibration products can be found here. | |
- Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_12_2") etc. The default (applicable to the HIPE version in use) can be obtained with cal = spireCal(calTree="spire_cal") . It can then be saved to a local pool right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- Alternatively, the latest calibration tree for SPIRE can be obtained as a jar file from Latest calibration trees
. Then, you have to possibilities to read and save:
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Photometer calibration | |
< < |
- SPIRE Photometer Calibration:
Full details of the SPIRE calibration can be found in the SPIRE Observers Manual and in dedicated publications: the calibration scheme is described in Griffin et al. (2013) and the implementation using Neptune as the primary calibration standard, is described in Bendo et al. (2013) .
| > > |
- SPIRE Photometer Calibration:
Full details of the SPIRE calibration can be found in the SPIRE Handbook and in dedicated publications: the calibration scheme is described in Griffin et al. (2013) and the implementation using Neptune as the primary calibration standard, is described in Bendo et al. (2013) .
| |
-
- Calibration uncertainties, which should be included in addition to the statistical errors of any measurement, are as follows:
- ± 4% absolute from Neptune model (this uncertainty is systematic and correlated across the three bands)
- ± 1.5% (random) from Neptune photometry
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
SPIRE Calibration Tree |
Applicable HIPE Version |
Comment |
| |
< < |
SPIRE_CAL_11_0 |
HIPE v11 |
Calibration tree currently used in operations |
| > > |
SPIRE_CAL_12_2 |
HIPE v12 |
Calibration tree currently used in operations |
SPIRE_CAL_11_0 |
HIPE v11 |
Final v11 cal tree |
| |
SPIRE_CAL_10_1 |
HIPE v10 |
Final v10 cal tree |
SPIRE_CAL_9_1 |
HIPE v9 |
Final v9 cal tree |
SPIRE_CAL_8_1 |
HIPE v8 |
Final v8 cal tree |
| |
More details of the changes in each version are given here . | |
< < |
- Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_11_0") etc. The default (applicable to the HIPE version in use) can be obtained with cal = spireCal(calTree="spire_cal") . It can then be saved to a local pool right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
| > > |
- Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_12_2") etc. The default (applicable to the HIPE version in use) can be obtained with cal = spireCal(calTree="spire_cal") . It can then be saved to a local pool right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
| |
- Alternatively, the latest calibration tree for SPIRE can be obtained as a jar file from Latest calibration trees
. Then, you have to possibilities to read and save:
| |
< < |
-
- The jar file can be load directly into HIPE with the command:
cal = spireCal(jarFile="PATH_TO_FILE/spire_cal_11_0.jar") . To save it to a local pool, proceed as described above, right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- The jar file can also be saved directly to a local pool without opening HIPE, running the following command in the terminal command line:
cal_import PATH_TO_FILE/spire_cal_11_0.jar . Then, to load the calibration tree in HIPE, simply type: cal = spireCal(pool="spire_cal_11_0")
| > > |
-
- The jar file can be load directly into HIPE with the command:
cal = spireCal(jarFile="PATH_TO_FILE/spire_cal_12_2.jar") . To save it to a local pool, proceed as described above, right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- The jar file can also be saved directly to a local pool without opening HIPE, running the following command in the terminal command line:
cal_import PATH_TO_FILE/spire_cal_12_2.jar . Then, to load the calibration tree in HIPE, simply type: cal = spireCal(pool="spire_cal_12_2")
| | | |
< < | See the SPIRE Data Reduction Guide for more details. | > > | See the SPIRE Data Reduction Guide for more details. | |
SPIRE calibration and performance
Photometer calibration | |
< < |
- SPIRE Photometer Calibration:
Full details of the SPIRE calibration can be found in the SPIRE Observers Manual and in dedicated publications: the calibration scheme is described in Griffin et al. (2013) and the implementation using Neptune as the primary calibration standard, is described in Bendo et al. (2013).
| > > |
- SPIRE Photometer Calibration:
Full details of the SPIRE calibration can be found in the SPIRE Observers Manual and in dedicated publications: the calibration scheme is described in Griffin et al. (2013) and the implementation using Neptune as the primary calibration standard, is described in Bendo et al. (2013) .
| |
-
- Calibration uncertainties, which should be included in addition to the statistical errors of any measurement, are as follows:
- ± 4% absolute from Neptune model (this uncertainty is systematic and correlated across the three bands)
- ± 1.5% (random) from Neptune photometry
| |
- SPIRE Photometer Beams:
- These are available in the SPIRE calibration context, at the standard map pixel size of (6,10,14) arcsec/pixel for (250,350,500) µm bands, and can be accessed in HIPE after a calibration context has been loaded (see above).
| |
< < | <-- * The observed beams at much finer scale of 1 arcsec/pixel, as well as the theoretical ones, are available from here . Please read the release note for more details. --> | |
-
-
A new more detailed analysis of the SPIRE beam profile data was undertaken in 2012, leading to revised values for beam profile solid angles and derivation of a semi empirical wavelength dependent beam profile model. The results at a scale of 1 arcsec/pixel as well as the data needed for the model are available for download. A detailed description of the analysis is given as well.
| |
< < | | > > | <-- * The observed beams at much finer scale of 1 arcsec/pixel, as well as the theoretical ones, are available from here . Please read the release note for more details. --> | |
- SPIRE Photometer filter transmission curves:
- These are also available in the SPIRE calibration context (photRsrf) and can be accessed in HIPE after a calibration context has been loaded (See above).
| |
Spectrometer calibration | |
< < | | > > | | |
-
- Calibration uncertainties, which should be included in addition to the statistical errors of any measurement from HIPE v11 onwards, are as follows:
- Point sources observed on the centre detectors (SSWD4 and SLWC3): the measured repeatability is 6%, with the following contributions: (i) absolute systematic uncertainty in the models from comparison of Uranus and Neptune - determined to be ±3%; (i) the statistical repeatability determined from observations of Uranus and Neptune, with pointing corrected - estimated at ±1% (excluding the edges of the bands); (iii) the uncertainties in the instrument and telescope model, which lead to an additive continuum offset error of 0.4 Jy for SLW and 0.3 Jy for SSW and (iv) the effect of the Herschel APE.
- Sparse observations of significantly extended sources:
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | | This page provides up-to-date information about using the SPIRE instrument: from preparing observations to reducing your data. This page also provides you with the latest calibration accuracies and known SPIRE calibration issues. | |
< < | Observing with SPIRE | > > | Documents explaining SPIRE | |
<--The most up to date information on instrument calibration and performance is given in the SPIRE Observers' Manual. This is the reference document used by all the rest of the SPIRE user guides (eg data reduction guide, cookbooks etc). Sometimes it may happen that outdated values are quoted in some of the documents. In such a case use the values given in the SPIRE Observers' Manual. --> | |
< < | | > > |
| | | |
< < |
- Summary papers from the A&A Special Issue:
| > > |
- Summary papers from the A&A Special Issue, volume 518 (2010):
| |
-
-
Some values on the performance are now outdated. Please consult the SDRG or the SPIRE Handbook for most up to date information.
- The Herschel-SPIRE instrument and its in-flight performance, Griffin et al., 2010, A&A, 518, L3, in-flight scientific capabilities of the SPIRE instrument.
- In-flight calibration of the Herschel-SPIRE instrument: Swinyard et al., 2010, A&A, 518, L4
| |
-
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
Please contact the Herschel helpdesk if you plan to use a developer build as there may be some additional information needed in order for you to properly make use of it.
- Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here:
| |
< < | | > > | | |
- SPIA: The SPIRE Photometer Interactive Analysis (SPIA) package is available as a plug-in for HIPE. SPIA provides a structured GUI based access to the more intricate parts of the scan map photometer pipeline for SPIRE without the immediate need to resort to scripts. More information can be found in the SDRG or on the SPIA web page
The SPIRE Launch Pads | |
< < |
- The SPIRE Launch Pads are single sheet quick entries (like a cheat sheet) into SPIRE data reduction and providing quick references to the relevant sections in the SPIRE Data Reduction Guide. There are launch pads for Data Access, SPIRE Photometer and Spectrometer data reduction.
| > > |
- The SPIRE Launch Pads are single sheet quick entries (like a cheat sheet) into SPIRE data reduction and providing quick references to the relevant sections in the SPIRE Data Reduction Guide. There are launch pads for Data Access, SPIRE Photometer and Spectrometer data reduction.
| | | |
> > | | |
Spectrometer data reduction | | Known Issues in ODs 1304 & 1305
For (yet) unknown reasons, the three detectors PSW-B5, PSW-E9 and PSW-F8 - that use to behave well during the entire mission - were noisy during the two operational days 1304 and 1305. The result are stripes visible in the final PSW map which the current (HIPE 11) pipeline is not able to correct. The solution is to mask and exclude these detectors from the analysis. This could be done in 2 ways: | |
< < |
- You can use the
SpireMaskEditor GUI as described in sec. 7.4.2 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to Master all samples in all scans (listed as BBID) for the detectors mentioned above.
| > > |
- You can use the
SpireMaskEditor GUI as described in Sec. 8.4 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to Master all samples in all scans (listed as BBID) for the detectors mentioned above.
| |
- Alternatively, you can use these lines of code
- After either of those cases, you must then re-run level 1 to 2 steps on the newly modified level1 product. If your observation has been already re-reduced with HIPE 11, original and new level1s are already destriped, so you can directly run the naive map-maker on the new level1. Otherwise, you must run the destriper step: check the pipeline script for details.
| |
Planck-HFI & Herschel-SPIRE cross calibration: absolute offset re-processing | |
< < | Herschel-SPIRE detectors are only sensitive to relative variations, and so as a consequence, the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. The Planck-HFI detectors are similar to the SPIRE ones, but the Planck observing strategy allowed it to (almost) observe a great circle on the sky every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by ~10%. | > > | As of HCSS 11, a new task named zeroPointCorrection is available to the users: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. | | | |
< < | As of HCSS 11, a new task named zeroPointCorrection is available to the users: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. To run the task, you will need to download the 2 Planck maps HFI-545 and HFI-857 maps from the HSC/SPIRE FTP area as they are not included in the HIPE distribution. These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective map beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation) | > > | Details on how to run the task are available in the SPIRE Data Reduction Guide, Section 6.8 | | | |
< < | The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 4.10 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the zeroPointCorrection task with one of the following methods: | > > | <-- Herschel-SPIRE detectors are only sensitive to relative variations, and so as a consequence, the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. The Planck-HFI detectors are similar to the SPIRE ones, but the Planck observing strategy allowed it to (almost) observe a great circle on the sky every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by ~10%.
-->
<-- To run the task, you will need to download the 2 Planck maps HFI-545 and HFI-857 maps from the HSC/SPIRE FTP area as they are not included in the HIPE distribution. These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective map beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation)
-->
| |
Source Extraction and Photometry |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
-
- Flux calibration of the Herschel-SPIRE photometer
, Bendo et al., 2013, MNRAS, 433, 3062
-
Observing extended sources with the Herschel SPIRE Fourier Transform Spectrometer , Wu et al., 2013, A&A, 556, 116
-
Beam profile for the Herschel-SPIRE Fourier transform spectrometer , Makiwa et al., 2013, Applied Optics, 52, 3864
| |
< < | | > > | | |
AOT release notes |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | | <--The most up to date information on instrument calibration and performance is given in the SPIRE Observers' Manual. This is the reference document used by all the rest of the SPIRE user guides (eg data reduction guide, cookbooks etc). Sometimes it may happen that outdated values are quoted in some of the documents. In such a case use the values given in the SPIRE Observers' Manual. -->
| |
< < | An update to the SPIRE OM is imminent (Dec 2013), the information in the current version is outdated, especially on performance, flux calibration uncertainties, colour corrections and extended source correction factors. Please use the information in the SPIRE Data Reduction Guide available form the HIPE-user documentation for latest released version (html). | > > | An update to the SPIRE OM is imminent (April 2014), the information in the current version is outdated, especially on performance, flux calibration uncertainties, colour corrections and extended source correction factors. Please use the information in the SPIRE Data Reduction Guide (SDRG) available form the HIPE-user documentation for the upcoming HIPE v12 (html). | |
- A quick guide to the SPIRE instrument: SPIRE fact sheet
- Summary papers from the A&A Special Issue:
| |
< < |
-
-
Some values on the performance are now outdated. Please consult the SPIRE Observers' Manual for most up to date information.
| > > |
-
-
Some values on the performance are now outdated. Please consult the SDRG or the SPIRE Handbook for most up to date information.
| |
-
- The Herschel-SPIRE instrument and its in-flight performance, Griffin et al., 2010, A&A, 518, L3, in-flight scientific capabilities of the SPIRE instrument.
- In-flight calibration of the Herschel-SPIRE instrument: Swinyard et al., 2010, A&A, 518, L4
- Detailed documents describing the pipeline algorithms:
| |
-
- Flux calibration of the Herschel-SPIRE photometer
, Bendo et al., 2013, MNRAS, 433, 3062
-
Observing extended sources with the Herschel SPIRE Fourier Transform Spectrometer , Wu et al., 2013, A&A, 556, 116
-
Beam profile for the Herschel-SPIRE Fourier transform spectrometer , Makiwa et al., 2013, Applied Optics, 52, 3864
| |
> > | | |
AOT release notes |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
- SPIRE Photometer Beams:
- These are available in the SPIRE calibration context, at the standard map pixel size of (6,10,14) arcsec/pixel for (250,350,500) µm bands, and can be accessed in HIPE after a calibration context has been loaded (see above).
| |
< < |
-
-
The observed beams at much finer scale of 1 arcsec/pixel, as well as the theoretical ones, are available from here . Please read the release note for more details.
| > > | <-- * The observed beams at much finer scale of 1 arcsec/pixel, as well as the theoretical ones, are available from here . Please read the release note for more details. --> | |
-
-
A new more detailed analysis of the SPIRE beam profile data was undertaken in 2012, leading to revised values for beam profile solid angles and derivation of a semi empirical wavelength dependent beam profile model. The results at a scale of 1 arcsec/pixel as well as the data needed for the model are available for download. A detailed description of the analysis is given as well.
- SPIRE Photometer filter transmission curves:
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
As of HCSS 11, a new task named zeroPointCorrection is available to the users: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. To run the task, you will need to download the 2 Planck maps HFI-545 and HFI-857 maps from the HSC/SPIRE FTP area as they are not included in the HIPE distribution. These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective map beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation) | |
< < | The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the zeroPointCorrection task with one of the following methods: | > > | The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 4.10 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the zeroPointCorrection task with one of the following methods: | |
- Run the zeroPointCorr_HIPE11.py script. It assumes that the observation has been reduced with HIPE 11 or later versions. It also sets the location of the two Planck maps by the
zeroPointCorrection task: please modify the PATH_TO_FILE accordingly to your set-up.
- Alternatively, run the correction using the SPIA interface (SPIRE Photometer Interactive Analysis
). In order to be able to run the zeroPointCorrection task, the user.props file present (by default) in you $HOME/.hcss directory must be modified and the following lines added (please modify the PATH_TO_FILE accordingly to your set-up):
-
spire.spg.hfi.545map = PATH_TO_FILE/DX9_map_545_smooth_8arcmin.fits
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
- The current recommended method for photometry
sourceExtractorTimeline task (formerly known as the Timeline Fitter) which works on the detector timelines. The Map based algorithm sourceExtractorSussex (SUSSEXtractor) providers good results and is useful on larger maps where the sourceExtractorTimeline will be significantly slower. sourceExtractorDaophot (DAOphot) also provides a reasonable estimate of the source flux but may require an aperture correction.
| |
> > |
- Photometry on single direction fast scan parallel mode maps: The photometry on single scan direction fast parallel mode results in higher photometric errors of up to 5 percent for aperture photometry compared to nominal speed and cross linked maps. The best results are obtained using the Timeline Fitter. Wherever possible orthogonal and nominal direction parallel scans should be merged.
| |
SPIRE report from the January 2013 HSC Map Making Workshop |
|
META TOPICPARENT |
name="WebHome" |
| |
< < | | | SPIRE instrument and calibration web pages
| |
-
-
- Mapping mode: the variations between detectors becomes important and the overall repeatability has been measured as ±7% (see Benielli et al. 2013, submitted, for a full discussion of mapping mode observations). The off-axis detectors are less well calibrated, especially outside the unvignetted part of the field.
- Uranus model used for the SPIRE FTS point-source flux calibration:
| |
< < |
-
- The ESA4 model, used from HIPE v10, is available here
.
| > > |
-
- The ESA4 model, used from HIPE v10 onwards, is available here
.
| |
Interest groups and scripts |
|
META TOPICPARENT |
name="WebHome" |
| |
< < | * Set YELLOW =
* Set ENDCOLOR = | |
SPIRE instrument and calibration web pages |
|
META TOPICPARENT |
name="WebHome" |
| |
> > | * Set YELLOW =
* Set ENDCOLOR = | | SPIRE instrument and calibration web pages
| |
Observing with SPIRE | |
< < | The most up to date information on instrument calibration and performance is given in the SPIRE Observers' Manual. This is the reference document used by all the rest of the SPIRE user guides (eg data reduction guide, cookbooks etc). Sometimes it may happen that outdated values are quoted in some of the documents. In such a case use the values given in the SPIRE Observers' Manual. | > > | <--The most up to date information on instrument calibration and performance is given in the SPIRE Observers' Manual. This is the reference document used by all the rest of the SPIRE user guides (eg data reduction guide, cookbooks etc). Sometimes it may happen that outdated values are quoted in some of the documents. In such a case use the values given in the SPIRE Observers' Manual. -->
An update to the SPIRE OM is imminent (Dec 2013), the information in the current version is outdated, especially on performance, flux calibration uncertainties, colour corrections and extended source correction factors. Please use the information in the SPIRE Data Reduction Guide available form the HIPE-user documentation for latest released version (html). | | | |
< < | | |
- A quick guide to the SPIRE instrument: SPIRE fact sheet
- Summary papers from the A&A Special Issue:
-
Some values on the performance are now outdated. Please consult the SPIRE Observers' Manual for most up to date information.
- The Herschel-SPIRE instrument and its in-flight performance, Griffin et al., 2010, A&A, 518, L3, in-flight scientific capabilities of the SPIRE instrument.
- In-flight calibration of the Herschel-SPIRE instrument: Swinyard et al., 2010, A&A, 518, L4
| |
< < |
- Detailed documents describing the pipeline algorithms (to be updated soon):
| > > |
- Detailed documents describing the pipeline algorithms:
| | |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
SPIRE report from the January 2013 HSC Map Making Workshop | |
< < | * The official release of the report of SPIRE map-making test campaign (2013) can be downloaded as a PDF . | > > |
- The official release of the report of SPIRE map-making test campaign (2013) can be downloaded as a PDF
.
- A dedicated webpage to this matter is available at the NHSC website
| | |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
| |
< < | Photometer data reduction | | | |
< < | Overview
The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered. | > > | Spectrometer data reduction
The best source of information for reducing SPIRE Spectrometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific types of sources:
- Faint (<10 Jy) and medium (<100 Jy) strength sources
- Bright sources (>500 Jy)
- Semi-extended sources
- Spectral mapping observations
- Observations with few repetitions
For faint sources, the subtraction of instrument, telescope and background emission is particularly important. Optimum subtraction can be performed in several ways (read the SPIRE Data Reduction Guide for details):
- Subtract the Dark Sky spectrum closest to your observation (use the "Background Subtraction" script in HIPE)
- Subtract the spectrum of surrounding detectors (use the "Background Subtraction" script in HIPE)
| | | |
< < | New definition of Level-2 products
- For versions of the HCSS prior to HIPE 10.0, a single point source calibrated (Jy/beam) map was provided in the Level 2 product for each of the PSW, PMW, PLW bands. However, for observations processed with HIPE 10.0 or later, more than one map calibration is made available within the Level 2 product. Maps are provided for the following scenarios for post HIPE v10.0 processing:
| > > | Dark Sky observations are observed on every SPIRE Spectrometer OD, and are all public in the Archive. | | | |
> > | A listing of the available Dark Sky observations can be found here. | | | |
< < |
Description |
New Name (HIPE10+) |
Original (pre-HIPE10) Name |
Point Source (standard) Maps |
psrcPSW |
PSW |
Extended Emission Maps |
extdPSW |
- |
Solar System Object Maps |
ssoPSW |
- |
Point Source Destriper Diagnostic |
psrcPSWdiag |
pddPSW |
Extended Emission Destriper Diagnostic |
extdPSWdiag |
- |
|
|
|
| | | |
< < |
- psrcPxW are the previous PxW maps, calibrated for point source and in units of Jy/beam. Note that to do aperture photometry on such maps you'll first need to convert them to surface brightness (Jy/pixel, MJy/sr, etc.), although it is suggested to directly use the already extended emission calibrated extdPxW maps. Finally, bear in mind that SPIRE itself cannot measure the absolute sky flux, hence psrcPxW maps have an arbitrary offset having zero median.
| > > | | | | |
< < |
- In all cases, SPIRE data is calibrated in the assumption of source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.7 of the SPIRE Data Reduction Guide.
| | | |
< < |
- The SPIRE Photometer filter transmission curves, also known as Relative Spectral Response Functions (RSRF) are available here
. For more details, please read the .readme file in this ftp folder.
| | | |
> > | Photometer data reduction | | | |
< < | Data Processing Issues | > > | Overview
The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered.
Data Processing Issues | |
The main issues that you might find in your data are: undetected glitches, thermistor or detector jumps, and bad baseline removal. | |
- Quality flags in the quality context
- Currently, the quality flags at the quality context inside the observation context are just meant for HSC/ICC internal evaluation of the quality of the products and not for the users. In case the data had some serious quality problem, the PI of the program has been contacted about it. Otherwise, only information in the quality summary, when available, should concern the observers.
| |
< < | Known Issues in ODs 1304 & 1305 | > > |
Known Issues in ODs 1304 & 1305 | | For (yet) unknown reasons, the three detectors PSW-B5, PSW-E9 and PSW-F8 - that use to behave well during the entire mission - were noisy during the two operational days 1304 and 1305. The result are stripes visible in the final PSW map which the current (HIPE 11) pipeline is not able to correct. The solution is to mask and exclude these detectors from the analysis. This could be done in 2 ways:
- You can use the
SpireMaskEditor GUI as described in sec. 7.4.2 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to Master all samples in all scans (listed as BBID) for the detectors mentioned above.
- Alternatively, you can use these lines of code
| | * The official release of the report of SPIRE map-making test campaign (2013) can be downloaded as a PDF . | |
< < | Spectrometer data reduction
The best source of information for reducing SPIRE Spectrometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific types of sources:
- Faint (<10 Jy) and medium (<100 Jy) strength sources
- Bright sources (>500 Jy)
- Semi-extended sources
- Spectral mapping observations
- Observations with few repetitions
For faint sources, the subtraction of instrument, telescope and background emission is particularly important. Optimum subtraction can be performed in several ways (read the SPIRE Data Reduction Guide for details):
- Subtract the Dark Sky spectrum closest to your observation (use the "Background Subtraction" script in HIPE)
- Subtract the spectrum of surrounding detectors (use the "Background Subtraction" script in HIPE)
Dark Sky observations are observed on every SPIRE Spectrometer OD, and are all public in the Archive.
A listing of the available Dark Sky observations can be found here.
<--
Spectral Cube Analysis
Spectral cubes are produced by the Spectrometer pipeline for mapping observations. Some tips, suggestions and examples of spectral cube analysis for SPIRE data are provided here.
--> | |
Cookbooks |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
- The current recommended method for photometry
sourceExtractorTimeline task (formerly known as the Timeline Fitter) which works on the detector timelines. The Map based algorithm sourceExtractorSussex (SUSSEXtractor) providers good results and is useful on larger maps where the sourceExtractorTimeline will be significantly slower. sourceExtractorDaophot (DAOphot) also provides a reasonable estimate of the source flux but may require an aperture correction.
| |
> > | SPIRE report from the January 2013 HSC Map Making Workshop
* The official release of the report of SPIRE map-making test campaign (2013) can be downloaded as a PDF . | | Spectrometer data reduction
The best source of information for reducing SPIRE Spectrometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific types of sources: |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
-
- Documents with relevance to the SPIRE flux calibration:
| |
< < | | > > |
-
- Flux Calibration of Broadband Far Infrared and Submillimetre Photometric Instruments: Theory and Application to Herschel-SPIRE
, Griffin et al., 2013, MNRAS, 434, 992
- Flux calibration of the Herschel-SPIRE photometer
, Bendo et al., 2013, MNRAS, 433, 3062
-
Observing extended sources with the Herschel SPIRE Fourier Transform Spectrometer , Wu et al., 2013, A&A, 556, 116
-
Beam profile for the Herschel-SPIRE Fourier transform spectrometer , Makiwa et al., 2013, Applied Optics, 52, 3864
| |
AOT release notes |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < | | > > | | |
- We also provide access to the latest stable developer build (latest stable CIB).
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
Please contact the Herschel helpdesk if you plan to use a developer build as there may be some additional information needed in order for you to properly make use of it.
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
- Faint (<10 Jy) and medium (<100 Jy) strength sources
- Bright sources (>500 Jy)
| |
< < | | > > |
- Semi-extended sources
- Spectral mapping observations
| |
- Observations with few repetitions
| |
< < | | |
For faint sources, the subtraction of instrument, telescope and background emission is particularly important. Optimum subtraction can be performed in several ways (read the SPIRE Data Reduction Guide for details): | |
A listing of the available Dark Sky observations can be found here. | |
> > | | | Cookbooks
Cookbooks are provided inside the SPIRE Data Reduction Guide (see above). | |
-
- These are also available in the SPIRE calibration context (photRsrf) and can be accessed in HIPE after a calibration context has been loaded (See above).
- Neptune and Uranus models used for the SPIRE photometer flux calibration:
| |
< < |
-
- The ESA2 models of the SPIRE calibration, used up to HIPE v10 and
spire_cal_10_1 , are available here .
-
The ESA4 models of the SPIRE calibration, used from HIPE v11 and spire_cal_11_0 , are available here .
| > > |
-
- The ESA2 models used up to HIPE v10 and
spire_cal_10_1 , are available here .
-
The ESA4 models used from HIPE v11 and spire_cal_11_0 , are available here .
| |
Spectrometer calibration | |
< < | Important FTS information, including details of the calibration, point source and extended source calibration etc, is available in the SPIRE Observers' Manual, Sections 4.2 and 5.3. These two sections are a must-read for anybody processing SPIRE FTS data. | > > |
- SPIRE Spectrometer Calibration:
Full details of the SPIRE FTS calibration can be found in the SPIRE Observers Manual (to be updated soon) and in Swinyard et al. (2013, submitted).
- Calibration uncertainties, which should be included in addition to the statistical errors of any measurement from HIPE v11 onwards, are as follows:
- Point sources observed on the centre detectors (SSWD4 and SLWC3): the measured repeatability is 6%, with the following contributions: (i) absolute systematic uncertainty in the models from comparison of Uranus and Neptune - determined to be ±3%; (i) the statistical repeatability determined from observations of Uranus and Neptune, with pointing corrected - estimated at ±1% (excluding the edges of the bands); (iii) the uncertainties in the instrument and telescope model, which lead to an additive continuum offset error of 0.4 Jy for SLW and 0.3 Jy for SSW and (iv) the effect of the Herschel APE.
- Sparse observations of significantly extended sources:
- the absolute uncertainty in intensity for a reasonably bright, fully extended object, observed in the central detectors is, in theory, ±1%, with the following contributions: (i) the systematic uncertainty in telescope model of 0.06%; (ii) the statistical repeatability estimated at ±1% and (iii) an additive continuum offset of 3.4x10-20 W/m2/Hz/sr for SLW and 1.1x10-19 W/m2/Hz/sr for SSW.
- In practice, truly extended sources tend to be faint and the uncertainty is therefore dominated by the additive offsets. When the source extent is larger than the main beam size, but not fully extended, or if there is structure inside the beam, then the uncertainties are dominated by the source-beam coupling (see Wu et al. 2013
) and are significantly greater than 1%.
- Mapping mode: the variations between detectors becomes important and the overall repeatability has been measured as ±7% (see Benielli et al. 2013, submitted, for a full discussion of mapping mode observations). The off-axis detectors are less well calibrated, especially outside the unvignetted part of the field.
- Uranus model used for the SPIRE FTS point-source flux calibration:
- The ESA4 model, used from HIPE v10, is available here
.
| |
Interest groups and scripts |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Herschel-SPIRE detectors are only sensitive to relative variations, and so as a consequence, the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. The Planck-HFI detectors are similar to the SPIRE ones, but the Planck observing strategy allowed it to (almost) observe a great circle on the sky every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by ~10%. | |
< < | As of HCSS 10, a new task named zeroPointCorrection is available: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. At first, Planck data needed by the task were delivered to HSC under special agreement: as a consequence, Herschel users were not able to re-process the absolute offset calculation. However, Planck data became public in April 2013 and it is now possible to exectue the zeroPointCorrection task.
Files needed:
- Download the HFI-545
and HFI-857 maps from the HSC/SPIRE FTP area . These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective map beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation)
- If you are using HIPE 10.x, download the colour correction table file SpireHfiColourCorrTab_v1.1. This step is not needed if you are using HIPE 11 or later versions as the proper colour correction file is already included in the build.
| > > | As of HCSS 11, a new task named zeroPointCorrection is available to the users: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. To run the task, you will need to download the 2 Planck maps HFI-545 and HFI-857 maps from the HSC/SPIRE FTP area as they are not included in the HIPE distribution. These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective map beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation) | |
The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the zeroPointCorrection task with one of the following methods: | |
< < |
- If you are using HIPE 10, run the zeroPointCorr_HIPE10.py script. It assumes that the observation has been reduced with HIPE 10 or previous versions. It also sets three required properties needed by the
zeroPointCorrection task, i.e. the location of two HFI maps and the colour correction table: please modify the PATH_TO_FILE accordingly to your set-up.
- If you are using HIPE 11, run the zeroPointCorr_HIPE11.py script. It assumes that the observation has been reduced with HIPE 11 or later versions. It also sets the location of the two Planck maps by the
zeroPointCorrection task: please modify the PATH_TO_FILE accordingly to your set-up.
| > > |
- Run the zeroPointCorr_HIPE11.py script. It assumes that the observation has been reduced with HIPE 11 or later versions. It also sets the location of the two Planck maps by the
zeroPointCorrection task: please modify the PATH_TO_FILE accordingly to your set-up.
| |
- Alternatively, run the correction using the SPIA interface (SPIRE Photometer Interactive Analysis
). In order to be able to run the zeroPointCorrection task, the user.props file present (by default) in you $HOME/.hcss directory must be modified and the following lines added (please modify the PATH_TO_FILE accordingly to your set-up):
-
spire.spg.hfi.545map = PATH_TO_FILE/DX9_map_545_smooth_8arcmin.fits
-
spire.spg.hfi.857map = PATH_TO_FILE/DX9_map_857_smooth_8arcmin.fits
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | | As of HCSS 10, a new task named zeroPointCorrection is available: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. At first, Planck data needed by the task were delivered to HSC under special agreement: as a consequence, Herschel users were not able to re-process the absolute offset calculation. However, Planck data became public in April 2013 and it is now possible to exectue the zeroPointCorrection task.
Files needed: | |
< < |
- Download the HFI-545
and HFI-857 maps from the HSC/SPIRE FTP area . These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective map beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation)
| > > |
- Download the HFI-545
and HFI-857 maps from the HSC/SPIRE FTP area . These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective map beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation)
| |
- If you are using HIPE 10.x, download the colour correction table file SpireHfiColourCorrTab_v1.1. This step is not needed if you are using HIPE 11 or later versions as the proper colour correction file is already included in the build.
The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the zeroPointCorrection task with one of the following methods: |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Files needed:
- Download the HFI-545
and HFI-857 maps from the HSC/SPIRE FTP area . These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective map beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation)
| |
< < | | > > |
- If you are using HIPE 10.x, download the colour correction table file SpireHfiColourCorrTab_v1.1. This step is not needed if you are using HIPE 11 or later versions as the proper colour correction file is already included in the build.
| |
The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the zeroPointCorrection task with one of the following methods: | |
< < |
- Run the zeroPointCorr.py script. It assumes that a Level1Context and Level2Context are already defined and named
level1 and level2 , respectively. It also sets three required properties needed by the zeroPointCorrection task, i.e. the location of two HFI maps and the colour correction table: please modify the PATH_TO_FILE accordingly to your set-up.
| > > |
- If you are using HIPE 10, run the zeroPointCorr_HIPE10.py script. It assumes that the observation has been reduced with HIPE 10 or previous versions. It also sets three required properties needed by the
zeroPointCorrection task, i.e. the location of two HFI maps and the colour correction table: please modify the PATH_TO_FILE accordingly to your set-up.
- If you are using HIPE 11, run the zeroPointCorr_HIPE11.py script. It assumes that the observation has been reduced with HIPE 11 or later versions. It also sets the location of the two Planck maps by the
zeroPointCorrection task: please modify the PATH_TO_FILE accordingly to your set-up.
| |
- Alternatively, run the correction using the SPIA interface (SPIRE Photometer Interactive Analysis
). In order to be able to run the zeroPointCorrection task, the user.props file present (by default) in you $HOME/.hcss directory must be modified and the following lines added (please modify the PATH_TO_FILE accordingly to your set-up):
-
spire.spg.hfi.545map = PATH_TO_FILE/DX9_map_545_smooth_8arcmin.fits
-
spire.spg.hfi.857map = PATH_TO_FILE/DX9_map_857_smooth_8arcmin.fits
| |
< < |
-
-
spire.spg.hfi.colorc = PATH_TO_FILE/SpireHfiColourCorrTab_v1.1.fits
| | | |
< < | A detailed descirption of the algorithm used for the cross-calibration with Planck and implemented in the zeroPointCorrection is described in the attached document and it will be soon in the official HCSS documentation. | > > | A detailed descirption of the algorithm used for the cross-calibration with Planck and implemented in the zeroPointCorrection is described in the HIPE 11 SPIRE Data Reduction Guide, sec. 4.10. | |
Source Extraction and Photometry | | Contact the Helpdesk | |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1376316561" name="zeroPointCorr_HIPE11.py.txt" path="zeroPointCorr_HIPE11.py.txt" size="2765" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.7" date="1345816678" name="SPIRE_SpectrometerLaunchPad_v1.7.pdf" path="SPIRE_SpectrometerLaunchPad_v1.7.pdf" size="195133" user="Main.ChrisPearson" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1376316527" name="zeroPointCorr_HIPE10.py.txt" path="zeroPointCorr_HIPE10.py.txt" size="2814" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="Sensitivity of the SPIRE Detectors to Operating Parameters" date="1369124238" name="SPIRE_Detector_Parameter_Sensitivity_Issue_1_Nov_14_2007.pdf" path="SPIRE_Detector_Parameter_Sensitivity_Issue_1_Nov_14_2007.pdf" size="189448" user="Main.IvanV" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v10.3. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml.
-
Please note that there was a bug in the destriper task included in HIPE 9.0 that may affect your final map, especially if there are bright objects in the observed field. This has been corrected since HIPE 9.1. If your observation falls in the mentioned category, you are strongly advised to update your HIPE installation.
| > > | | |
- We also provide access to the latest stable developer build (latest stable CIB).
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
Please contact the Herschel helpdesk if you plan to use a developer build as there may be some additional information needed in order for you to properly make use of it.
- Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here:
| |
< < | | > > | | |
- SPIA: The SPIRE Photometer Interactive Analysis (SPIA) package is available as a plug-in for HIPE. SPIA provides a structured GUI based access to the more intricate parts of the scan map photometer pipeline for SPIRE without the immediate need to resort to scripts. More information can be found in the SDRG or on the SPIA web page
| | Overview
The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered. | |
< < | New definition of Leve2 products | > > | New definition of Level-2 products | |
- For versions of the HCSS prior to HIPE 10.0, a single point source calibrated (Jy/beam) map was provided in the Level 2 product for each of the PSW, PMW, PLW bands. However, for observations processed with HIPE 10.0 or later, more than one map calibration is made available within the Level 2 product. Maps are provided for the following scenarios for post HIPE v10.0 processing:
| |
Extended Emission Destriper Diagnostic |
extdPSWdiag |
- |
|
|
|
| |
< < |
- psrcPxW are the previous PxW maps, calibrated for point source and in units of Jy/beam. Note that to do aperture photometry on such maps you'll first need to convert them to surface brightness (Jy/pixel, MJy/sr, etc.), although it is suggested to directly use the already extended emission calibrated extdPxW maps. Finally, bear in mind that SPIRE itself cannot measure the absolute sky flux, hence psrcPxW maps have an arbitrary offset having zero median.
| > > |
- psrcPxW are the previous PxW maps, calibrated for point source and in units of Jy/beam. Note that to do aperture photometry on such maps you'll first need to convert them to surface brightness (Jy/pixel, MJy/sr, etc.), although it is suggested to directly use the already extended emission calibrated extdPxW maps. Finally, bear in mind that SPIRE itself cannot measure the absolute sky flux, hence psrcPxW maps have an arbitrary offset having zero median.
| |
- ssoPxW maps are corrected for SSO proper motion: maps are in Jy/beam and they are subject to the same photometry rules of the psrcPxW maps.
- extdPxW maps are calibrated for extended emission and provided in units of MJy/sr. These maps are provided with an estimation of the absolute offset via cross-calibration with Planck data.
| |
< < |
- In all cases, SPIRE data is calibrated in the assumption of source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.7 of the SPIRE Data Reduction Guide.
| > > |
- In all cases, SPIRE data is calibrated in the assumption of source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.7 of the SPIRE Data Reduction Guide.
| |
- The SPIRE Photometer filter transmission curves, also known as Relative Spectral Response Functions (RSRF) are available here
. For more details, please read the .readme file in this ftp folder.
| | The main issues that you might find in your data are: undetected glitches, thermistor or detector jumps, and bad baseline removal.
- Stripes in PSW, PMW and/or PLW (Level 2) maps
| |
< < |
-
- All SPIRE photometry pipelines now use the destriper by default, which improves the issue of stripes in Level 2 maps. There should be noticeable improvements in that respect with HIPE version 9. The destriper documentation can be found on the NHSC website
| > > |
-
- All SPIRE Photometer pipelines now use the destriper by default, which improves the issue of stripes in Level 2 maps. There should be noticeable improvements in that respect from HIPE version 9 onwards. The destriper documentation can be found on the NHSC website
| |
- De-glitcher masks faint sources
- For data taken in Parallel Mode in particular (sampling at 10Hz, at high speed 60"/s), the de-glitcher may flag very faint sources as glitches when it is run with standard parameters. Faint sources may have a "delta function" shape due to the low sampling rate, which looks similar to a small glitch. Try modifying the "correlation parameter" to 0.95: this will decrease the number of detected glitches - it may be better to have a limited detection rate in first level deglitching and defer to Level 2 deglitching.
| |
-
- This effect, related to data masking or poor coverage, is more evident in single fast-scan Parallel Mode maps. To avoid NaNs, increase the pixel size (i.e., decrease the map's resolution).
- This effect can also occur with destriped maps. In this case check if increasing the sigma parameter or switching off the Level 2 deglitcher helps.
| |
< < |
- WCS in 3-colour images
- Problems with the wrong WCS in the output RGB images in all observations reduced with HIPE 8 have been fixed in HIPE 9
| |
- Quality flags in the quality context
- Currently, the quality flags at the quality context inside the observation context are just meant for HSC/ICC internal evaluation of the quality of the products and not for the users. In case the data had some serious quality problem, the PI of the program has been contacted about it. Otherwise, only information in the quality summary, when available, should concern the observers.
Known Issues in ODs 1304 & 1305 | |
< < | For (yet) unknown reasons, the three detectors PSW-B5, PSW-E9 and PSW-F8 - that use to behave well during the entire mission - were noisy during the two operational days 1304 and 1305. The result are stripes visible in the final PSW map which the current (HIPE 10) pipeline is not able to correct. The solution is to mask and exclude these detectors from the analysis. This could be done in 2 ways:
- You can use the
SpireMaskEditor GUI as described in sec. 7.4.2 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to Master all samples in all scans (listed as BBID) for the detectors mentioned above.
- Alternatively, you can use the following line of codes:
##### EDIT MASK SCRIPT BEGINS #####
# List of detectors to be masked
bolos = ['PSWB5', 'PSWE9', 'PSWF8']
# Level1 of your observation, assuming the observation context varible is named 'obs'
level1 = obs.level1
# Create new level 1
new_l1 = Level1Context()
for scan in range(0, level1.getCount()):
#
# Load level 1 product, scan by scan
data = level1.refs[scan].product
#
# Change mask for selected detectors in all scans, setting it to MASTER
for bolo in bolos:
data['mask'][bolo].data[:] = 1
#
new_l1.addProduct(data)
##### EDIT MASK SCRIPT ENDS #####
| > > | For (yet) unknown reasons, the three detectors PSW-B5, PSW-E9 and PSW-F8 - that use to behave well during the entire mission - were noisy during the two operational days 1304 and 1305. The result are stripes visible in the final PSW map which the current (HIPE 11) pipeline is not able to correct. The solution is to mask and exclude these detectors from the analysis. This could be done in 2 ways:
- You can use the
SpireMaskEditor GUI as described in sec. 7.4.2 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to Master all samples in all scans (listed as BBID) for the detectors mentioned above.
- Alternatively, you can use these lines of code
| | | |
< < |
- After either of those cases, you must then re-run level 1 to 2 steps on the newly modified level1 product. If your observation has been already re-reduced with HIPE 10, original and new level1s are already destriped, so you can directly run the naive map-maker on the new level1. Otherwise, you must run the destriper step: check the pipeline script for details.
| > > |
- After either of those cases, you must then re-run level 1 to 2 steps on the newly modified level1 product. If your observation has been already re-reduced with HIPE 11, original and new level1s are already destriped, so you can directly run the naive map-maker on the new level1. Otherwise, you must run the destriper step: check the pipeline script for details.
| |
Planck-HFI & Herschel-SPIRE cross calibration: absolute offset re-processing | |
< < | Herschel-SPIRE detectors are only sensitive to relative variations, as a consequence the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. Planck-HFI detectors are similar to the SPIRE ones, however its observing strategy allows it to (almost) observe a sky's great circle every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by ~10%. | > > | Herschel-SPIRE detectors are only sensitive to relative variations, and so as a consequence, the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. The Planck-HFI detectors are similar to the SPIRE ones, but the Planck observing strategy allowed it to (almost) observe a great circle on the sky every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by ~10%. | | | |
< < | As of HCSS 10, a new task named zeroPointCorrection is available: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. At first, Planck data needed by the task were delivered to HSC under special agreement: as a consequence, Herschel users were not able to re-process the absolute offset calculation. However, Planck data became public in April 2013 and it is now possible to exectue the zeroPointCorrection . | > > | As of HCSS 10, a new task named zeroPointCorrection is available: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. At first, Planck data needed by the task were delivered to HSC under special agreement: as a consequence, Herschel users were not able to re-process the absolute offset calculation. However, Planck data became public in April 2013 and it is now possible to exectue the zeroPointCorrection task. | |
Files needed: | |
< < |
- Download the HFI-545
and HFI-857 maps from the HSC/SPIRE FTP area . These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective maps' beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation)
| > > |
- Download the HFI-545
and HFI-857 maps from the HSC/SPIRE FTP area . These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective map beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation)
| | | |
< < | The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the zeroPointCorrection task with one of the following methods: | > > | The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the zeroPointCorrection task with one of the following methods: | |
- Run the zeroPointCorr.py script. It assumes that a Level1Context and Level2Context are already defined and named
level1 and level2 , respectively. It also sets three required properties needed by the zeroPointCorrection task, i.e. the location of two HFI maps and the colour correction table: please modify the PATH_TO_FILE accordingly to your set-up.
- Alternatively, run the correction using the SPIA interface (SPIRE Photometer Interactive Analysis
). In order to be able to run the zeroPointCorrection task, the user.props file present (by default) in you $HOME/.hcss directory must be modified and the following lines added (please modify the PATH_TO_FILE accordingly to your set-up):
-
spire.spg.hfi.545map = PATH_TO_FILE/DX9_map_545_smooth_8arcmin.fits
| |
SPIRE Calibration Tree |
Applicable HIPE Version |
Comment |
| |
< < |
SPIRE_CAL_10_1 |
HIPE v10 |
Calibration tree currently used in operations |
| > > |
SPIRE_CAL_11_0 |
HIPE v11 |
Calibration tree currently used in operations |
SPIRE_CAL_10_1 |
HIPE v10 |
Final v10 cal tree |
| |
SPIRE_CAL_9_1 |
HIPE v9 |
Final v9 cal tree |
SPIRE_CAL_8_1 |
HIPE v8 |
Final v8 cal tree |
SPIRE_CAL_7_0 |
HIPE v7 |
Final v7 cal tree. |
| |
More details of the changes in each version are given here . | |
< < |
- Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_10_1") etc. The default (applicable to the HIPE version in use) can be obtained with cal = spireCal(calTree="spire_cal") . It can then be saved to a local pool right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
| > > |
- Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_11_0") etc. The default (applicable to the HIPE version in use) can be obtained with cal = spireCal(calTree="spire_cal") . It can then be saved to a local pool right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
| |
- Alternatively, the latest calibration tree for SPIRE can be obtained as a jar file from Latest calibration trees
. Then, you have to possibilities to read and save:
| |
< < |
-
- The jar file can be load directly into HIPE with the command:
cal = spireCal(jarFile="PATH_TO_FILE/spire_cal_10_1.jar") . To save it to a local pool, proceed as described above, right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- The jar file can also be saved directly to a local pool without opening HIPE, running the following command in the terminal command line:
cal_import PATH_TO_FILE/spire_cal_10_1.jar . Then, to load the calibration tree in HIPE, simply type: cal = spireCal(pool="spire_cal_10_1")
| > > |
-
- The jar file can be load directly into HIPE with the command:
cal = spireCal(jarFile="PATH_TO_FILE/spire_cal_11_0.jar") . To save it to a local pool, proceed as described above, right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- The jar file can also be saved directly to a local pool without opening HIPE, running the following command in the terminal command line:
cal_import PATH_TO_FILE/spire_cal_11_0.jar . Then, to load the calibration tree in HIPE, simply type: cal = spireCal(pool="spire_cal_11_0")
| | | |
< < | See the SPIRE Data Reduction Guide for more details. | > > | See the SPIRE Data Reduction Guide for more details. | |
SPIRE calibration and performance | |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="Script to correct photometer data in ODs 1304/1305" date="1374833050" name="correct_od1304_1305.py.txt" path="correct_od1304_1305.py.txt" size="610" user="Main.EdwardPolehampton" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE A&A paper, Griifin et al 2010" date="1295862676" name="aa14519-10.pdf" path="aa14519-10.pdf" size="1353253" user="Main.AnthonyMarston" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1370344174" name="SpireHfiColourCorrTab_v1.1.fits" path="SpireHfiColourCorrTab_v1.1.fits" size="20160" user="Main.LucaConversi" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < | | > > | | |
-
-
Please note that there was a bug in the destriper task included in HIPE 9.0 that may affect your final map, especially if there are bright objects in the observed field. This has been corrected since HIPE 9.1. If your observation falls in the mentioned category, you are strongly advised to update your HIPE installation.
- We also provide access to the latest stable developer build (latest stable CIB).
| |
< < |
-
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
| > > |
-
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
Please contact the Herschel helpdesk if you plan to use a developer build as there may be some additional information needed in order for you to properly make use of it.
| |
- Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here:
| | The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered.
New definition of Leve2 products | |
< < |
- For versions of the HCSS prior to HIPE 10.0, a single point source calibrated (Jy/beam) map was provided in the Level 2 product for each of the PSW, PMW, PLW bands. However, for observations processed with HIPE 10.0 or later, more than one map calibration is made available within the Level 2 product. Maps are provided for the following scenarios for post HIPE 10.0 processing:
| > > |
- For versions of the HCSS prior to HIPE 10.0, a single point source calibrated (Jy/beam) map was provided in the Level 2 product for each of the PSW, PMW, PLW bands. However, for observations processed with HIPE 10.0 or later, more than one map calibration is made available within the Level 2 product. Maps are provided for the following scenarios for post HIPE v10.0 processing:
| |
| |
Planck-HFI & Herschel-SPIRE cross calibration: absolute offset re-processing | |
< < | Herschel-SPIRE detectors are only sensitive to relative variations, as a consequence the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. Planck-HFI detectors are similar to the SPIRE ones, however its observing strategy allows it to (almost) observe a sky's great circle every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by $\sim 10$\%. | > > | Herschel-SPIRE detectors are only sensitive to relative variations, as a consequence the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. Planck-HFI detectors are similar to the SPIRE ones, however its observing strategy allows it to (almost) observe a sky's great circle every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by ~10%. | |
As of HCSS 10, a new task named zeroPointCorrection is available: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. At first, Planck data needed by the task were delivered to HSC under special agreement: as a consequence, Herschel users were not able to re-process the absolute offset calculation. However, Planck data became public in April 2013 and it is now possible to exectue the zeroPointCorrection . |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
-
-
spire.spg.hfi.857map = PATH_TO_FILE/DX9_map_857_smooth_8arcmin.fits
-
spire.spg.hfi.colorc = PATH_TO_FILE/SpireHfiColourCorrTab_v1.1.fits
| |
> > | A detailed descirption of the algorithm used for the cross-calibration with Planck and implemented in the zeroPointCorrection is described in the attached document and it will be soon in the official HCSS documentation. | |
Source Extraction and Photometry | |
META FILEATTACHMENT |
attr="" autoattached="1" comment="Sensitivity of the SPIRE Detectors to Operating Parameters" date="1369124238" name="SPIRE_Detector_Parameter_Sensitivity_Issue_1_Nov_14_2007.pdf" path="SPIRE_Detector_Parameter_Sensitivity_Issue_1_Nov_14_2007.pdf" size="189448" user="Main.IvanV" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.6" date="1345816649" name="SPIRE_DataLaunchPad_v1.6.pdf" path="SPIRE_DataLaunchPad_v1.6.pdf" size="205212" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1370854397" name="zeroPointCorr.py.txt" path="zeroPointCorr.py.txt" size="2959" user="Main.LucaConversi" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1371136153" name="Offset_Estimation_Description.pdf" path="Offset_Estimation_Description.pdf" size="2409147" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
-
- Documents with relevance to the SPIRE flux calibration:
| |
> > | | |
AOT release notes |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
- The SPIRE Photometer filter transmission curves, also known as Relative Spectral Response Functions (RSRF) are available here
. For more details, please read the .readme file in this ftp folder.
| |
< < | Planck-HFI & Herschel-SPIRE cross calibration: absolute offset re-processing
Herschel-SPIRE detectors are only sensitive to relative variations, as a consequence the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. Planck-HFI detectors are similar to the SPIRE ones, however its observing strategy allows it to (almost) observe a sky's great circle every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by $\sim 10$\%.
As of HCSS 10, a new task named zeroPointCorrection is available: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. At first, Planck data needed by the task were delivered to HSC under special agreement: as a consequence, Herschel users were not able to re-process the absolute offset calculation. However, Planck data became public in April 2013 and it is now possible to exectue the zeroPointCorrection .
Files needed:
- Download the HFI545
and HFI-857 maps from the HSC/SPIRE FTP area . These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective maps' beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation)
- Download the colour correction table file SpireHfiColourCorrTab_v1.1
The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the following code:
#################### SCRIPT BEGINS ####################
# The script assumes that:
# 1. a Level1Context is already defined and it is named "level1"
# 2. a Level2Context is already defined and it is named "level2"
# E.g.:
#
# obs = getObservation(1342195871,useHsa=1)
# level1 = obs.level1
# level2 = obs.level2
# Define properties needed by zeroPointCorrection task
Configuration.setProperty("spire.spg.hfi.colorc", "PATH_TO_FILE/SpireHfiColourCorrTab_v1.1.fits")
Configuration.setProperty("spire.spg.hfi.545map", "PATH_TO_FILE/DX9_map_545_smooth_8arcmin.fits")
Configuration.setProperty("spire.spg.hfi.857map", "PATH_TO_FILE/DX9_map_857_smooth_8arcmin.fits")
# Check if zero-point correction task is runnable
zeroPointIsRunnable = zeroPointCorrection.isRunnable()
if zeroPointIsRunnable:
print "Configuration is properly set. Zero-point correction task is runnable in this environment"
# Run zero-point correction task
if (zeroPointIsRunnable):
level2ZeroPoint = MapContext()
for key in level2.meta.keySet():
level2ZeroPoint.meta[key]=level2.meta[key].copy()
#
# Load relative gain correction file
chanRelGains = obs.calibration.phot.chanRelGain
#
# Create new Level1Context
scansZeroPoint = Level1Context()
scansZeroPoint.meta = level1.meta
#
# Apply relative gain correction, loading the original Level1Context from the "level1" variable
for i in range(level1.getCount()):
psp = level1.getProduct(i)
if psp.type=="PPT": psp.setType("PSP") #for old Level 1 contexts
psp = applyRelativeGains(psp, chanRelGains)
scansZeroPoint.addProduct(psp)
#
# Try to load the de-striper diagnostic products to speed-up re-processing
arrays = ["PSW","PMW","PLW"]
for array in arrays:
diagref = level2.refs['psrc'+array.upper()+'diag']
if diagref != None:
diag = diagref.product
else:
diag = None
#
# (Re-)run destriper on new Level1Context
newscans,mapZero,diagZero, p4,p5 = destriper(level1=scansZeroPoint, array=array, nThreads=2, \
withMedianCorrected=True, useSink=True, startParameters=diag)
#
# Save diagnostic product, this time with prefix extd, into the "level2" variable
level2ZeroPoint.refs.put(array,ProductRef(mapZero))
level2.refs.put('extd'+array.upper()+'diag', ProductRef(diagZero))
#
# Run the zeroPointCorrection tasks on extdPxW maps
zeroPointMaps, zeroPointParam=zeroPointCorrection(level2=level2ZeroPoint, hfiFwhm=8.0)
#
# Populate the "level2" variable with extdPxW maps, with the computed offset
for array in arrays:
level2.refs.put("extd"+array.upper(),ProductRef(zeroPointMaps.getProduct("extd"+array.upper())))
#################### SCRIPT ENDS ####################
| | Data Processing Issues
The main issues that you might find in your data are: undetected glitches, thermistor or detector jumps, and bad baseline removal. | |
- After either of those cases, you must then re-run level 1 to 2 steps on the newly modified level1 product. If your observation has been already re-reduced with HIPE 10, original and new level1s are already destriped, so you can directly run the naive map-maker on the new level1. Otherwise, you must run the destriper step: check the pipeline script for details.
| |
> > | Planck-HFI & Herschel-SPIRE cross calibration: absolute offset re-processing
Herschel-SPIRE detectors are only sensitive to relative variations, as a consequence the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. Planck-HFI detectors are similar to the SPIRE ones, however its observing strategy allows it to (almost) observe a sky's great circle every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by $\sim 10$\%.
As of HCSS 10, a new task named zeroPointCorrection is available: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. At first, Planck data needed by the task were delivered to HSC under special agreement: as a consequence, Herschel users were not able to re-process the absolute offset calculation. However, Planck data became public in April 2013 and it is now possible to exectue the zeroPointCorrection .
Files needed:
- Download the HFI-545
and HFI-857 maps from the HSC/SPIRE FTP area . These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective maps' beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation)
- Download the colour correction table file SpireHfiColourCorrTab_v1.1
The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the zeroPointCorrection task with one of the following methods:
- Run the zeroPointCorr.py script. It assumes that a Level1Context and Level2Context are already defined and named
level1 and level2 , respectively. It also sets three required properties needed by the zeroPointCorrection task, i.e. the location of two HFI maps and the colour correction table: please modify the PATH_TO_FILE accordingly to your set-up.
- Alternatively, run the correction using the SPIA interface (SPIRE Photometer Interactive Analysis
). In order to be able to run the zeroPointCorrection task, the user.props file present (by default) in you $HOME/.hcss directory must be modified and the following lines added (please modify the PATH_TO_FILE accordingly to your set-up):
-
spire.spg.hfi.545map = PATH_TO_FILE/DX9_map_545_smooth_8arcmin.fits
-
spire.spg.hfi.857map = PATH_TO_FILE/DX9_map_857_smooth_8arcmin.fits
-
spire.spg.hfi.colorc = PATH_TO_FILE/SpireHfiColourCorrTab_v1.1.fits
| | Source Extraction and Photometry
- The current recommended method for photometry
sourceExtractorTimeline task (formerly known as the Timeline Fitter) which works on the detector timelines. The Map based algorithm sourceExtractorSussex (SUSSEXtractor) providers good results and is useful on larger maps where the sourceExtractorTimeline will be significantly slower. sourceExtractorDaophot (DAOphot) also provides a reasonable estimate of the source flux but may require an aperture correction.
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
- extdPxW maps are calibrated for extended emission and provided in units of MJy/sr. These maps are provided with an estimation of the absolute offset via cross-calibration with Planck data.
| |
< < |
- In all cases, SPIRE data is calibrated in the assumption of source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.7 of the SPIRE Data Reduction Guide.
| > > |
- In all cases, SPIRE data is calibrated in the assumption of source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.7 of the SPIRE Data Reduction Guide.
| |
- The SPIRE Photometer filter transmission curves, also known as Relative Spectral Response Functions (RSRF) are available here
. For more details, please read the .readme file in this ftp folder.
| | | |
< < | The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the following code: | > > | The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the following code: | | | |
> > | #################### SCRIPT BEGINS #################### | | # The script assumes that:
# 1. a Level1Context is already defined and it is named "level1"
# 2. a Level2Context is already defined and it is named "level2" | |
> > | # E.g.:
#
# obs = getObservation(1342195871,useHsa=1)
# level1 = obs.level1
# level2 = obs.level2 | |
# Define properties needed by zeroPointCorrection task | |
< < | Configuration.setProperty("spire.spg.hfi.colorc", "PATH_TO_FILE/SpireHfiColourCorrTab_v2.2.fits") | > > | Configuration.setProperty("spire.spg.hfi.colorc", "PATH_TO_FILE/SpireHfiColourCorrTab_v1.1.fits") | | Configuration.setProperty("spire.spg.hfi.545map", "PATH_TO_FILE/DX9_map_545_smooth_8arcmin.fits")
Configuration.setProperty("spire.spg.hfi.857map", "PATH_TO_FILE/DX9_map_857_smooth_8arcmin.fits") | |
< < | # Check if properties are correctly set | > > | # Check if zero-point correction task is runnable
zeroPointIsRunnable = zeroPointCorrection.isRunnable()
if zeroPointIsRunnable:
print "Configuration is properly set. Zero-point correction task is runnable in this environment"
# Run zero-point correction task | | if (zeroPointIsRunnable):
level2ZeroPoint = MapContext()
for key in level2.meta.keySet(): | | scansZeroPoint.addProduct(psp)
#
# Try to load the de-striper diagnostic products to speed-up re-processing | |
> > | arrays = ["PSW","PMW","PLW"] | | for array in arrays:
diagref = level2.refs['psrc'+array.upper()+'diag']
if diagref = None: | | # Populate the "level2" variable with extdPxW maps, with the computed offset
for array in arrays:
level2.refs.put("extd"+array.upper(),ProductRef(zeroPointMaps.getProduct("extd"+array.upper()))) | |
> > |
#################### SCRIPT ENDS #################### | | | |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="Sensitivity of the SPIRE Detectors to Operating Parameters" date="1369124238" name="SPIRE_Detector_Parameter_Sensitivity_Issue_1_Nov_14_2007.pdf" path="SPIRE_Detector_Parameter_Sensitivity_Issue_1_Nov_14_2007.pdf" size="189448" user="Main.IvanV" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.6" date="1345816649" name="SPIRE_DataLaunchPad_v1.6.pdf" path="SPIRE_DataLaunchPad_v1.6.pdf" size="205212" user="Main.ChrisPearson" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1370854397" name="zeroPointCorr.py.txt" path="zeroPointCorr.py.txt" size="2959" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < | | > > | | |
-
-
Please note that there was a bug in the destriper task included in HIPE 9.0 that may affect your final map, especially if there are bright objects in the observed field. This has been corrected since HIPE 9.1. If your observation falls in the mentioned category, you are strongly advised to update your HIPE installation.
- We also provide access to the latest stable developer build (latest stable CIB).
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Photometer data reduction | |
< < | Overview | > > | Overview | | The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered. | |
< < | New definition of Leve2 products | > > | New definition of Leve2 products | |
- For versions of the HCSS prior to HIPE 10.0, a single point source calibrated (Jy/beam) map was provided in the Level 2 product for each of the PSW, PMW, PLW bands. However, for observations processed with HIPE 10.0 or later, more than one map calibration is made available within the Level 2 product. Maps are provided for the following scenarios for post HIPE 10.0 processing:
| |
- The SPIRE Photometer filter transmission curves, also known as Relative Spectral Response Functions (RSRF) are available here
. For more details, please read the .readme file in this ftp folder.
| |
< < | Data Processing Issues | > > |
Planck-HFI & Herschel-SPIRE cross calibration: absolute offset re-processing
Herschel-SPIRE detectors are only sensitive to relative variations, as a consequence the absolute brightness of the observed region is unknown and maps are constructed such that they have zero median. Planck-HFI detectors are similar to the SPIRE ones, however its observing strategy allows it to (almost) observe a sky's great circle every minute (having a 1 rpm spinning rate). By comparing the sky brightness as measured by COBE-FIRAS at the galactic poles (where the dust emission is lower), HFI is capable of setting an absolute offset to its maps. SPIRE and HFI share two channels with overlapping wavebands: SPIRE-PMW and HFI-857 have a similar filter profile, while SPIRE-PLW and HFI-545 are shifted by $\sim 10$\%.
As of HCSS 10, a new task named zeroPointCorrection is available: this task calculates the absolute offset for a SPIRE map based on cross-calibration with HFI-545 and HFI-857 maps, colour-correcting HFI to SPIRE wavebands assuming a grey body function with fixed beta. At first, Planck data needed by the task were delivered to HSC under special agreement: as a consequence, Herschel users were not able to re-process the absolute offset calculation. However, Planck data became public in April 2013 and it is now possible to exectue the zeroPointCorrection .
Files needed:
- Download the HFI545
and HFI-857 maps from the HSC/SPIRE FTP area . These maps are derived from the ones available in the Planck Legacy Archive, but convolved with an 8 arcmin Gaussian beam in order to circularize the effective maps' beams, plus the maps absolute offset as estimated by the Planck-HFI team via cross-calibration with FIRAS (see Planck Collaboration VIII. 2013, In preparation)
- Download the colour correction table file SpireHfiColourCorrTab_v1.1
The offsets are computed on extdPxW maps, calibrated for extended emission, with extended gain correction applied and in units of MJy/sr (as explained in the section 5.7 of the SPIRE Data Reduction Guide). Hence, the re-processing will start from a level-1 context (which may be the result of merging multiple observations, see e.g. the Photometry Map Merging scirpt available in HIPE under the menu Scripts → SPIRE Useful script ) and then executing the following code:
# The script assumes that:
# 1. a Level1Context is already defined and it is named "level1"
# 2. a Level2Context is already defined and it is named "level2"
# Define properties needed by zeroPointCorrection task
Configuration.setProperty("spire.spg.hfi.colorc", "PATH_TO_FILE/SpireHfiColourCorrTab_v2.2.fits")
Configuration.setProperty("spire.spg.hfi.545map", "PATH_TO_FILE/DX9_map_545_smooth_8arcmin.fits")
Configuration.setProperty("spire.spg.hfi.857map", "PATH_TO_FILE/DX9_map_857_smooth_8arcmin.fits")
# Check if properties are correctly set
if (zeroPointIsRunnable):
level2ZeroPoint = MapContext()
for key in level2.meta.keySet():
level2ZeroPoint.meta[key]=level2.meta[key].copy()
#
# Load relative gain correction file
chanRelGains = obs.calibration.phot.chanRelGain
#
# Create new Level1Context
scansZeroPoint = Level1Context()
scansZeroPoint.meta = level1.meta
#
# Apply relative gain correction, loading the original Level1Context from the "level1" variable
for i in range(level1.getCount()):
psp = level1.getProduct(i)
if psp.type=="PPT": psp.setType("PSP") #for old Level 1 contexts
psp = applyRelativeGains(psp, chanRelGains)
scansZeroPoint.addProduct(psp)
#
# Try to load the de-striper diagnostic products to speed-up re-processing
for array in arrays:
diagref = level2.refs['psrc'+array.upper()+'diag']
if diagref != None:
diag = diagref.product
else:
diag = None
#
# (Re-)run destriper on new Level1Context
newscans,mapZero,diagZero, p4,p5 = destriper(level1=scansZeroPoint, array=array, nThreads=2, \
withMedianCorrected=True, useSink=True, startParameters=diag)
#
# Save diagnostic product, this time with prefix extd, into the "level2" variable
level2ZeroPoint.refs.put(array,ProductRef(mapZero))
level2.refs.put('extd'+array.upper()+'diag', ProductRef(diagZero))
#
# Run the zeroPointCorrection tasks on extdPxW maps
zeroPointMaps, zeroPointParam=zeroPointCorrection(level2=level2ZeroPoint, hfiFwhm=8.0)
#
# Populate the "level2" variable with extdPxW maps, with the computed offset
for array in arrays:
level2.refs.put("extd"+array.upper(),ProductRef(zeroPointMaps.getProduct("extd"+array.upper())))
Data Processing Issues | |
The main issues that you might find in your data are: undetected glitches, thermistor or detector jumps, and bad baseline removal. | |
- Quality flags in the quality context
- Currently, the quality flags at the quality context inside the observation context are just meant for HSC/ICC internal evaluation of the quality of the products and not for the users. In case the data had some serious quality problem, the PI of the program has been contacted about it. Otherwise, only information in the quality summary, when available, should concern the observers.
| |
< < | Known Issues in ODs 1304 & 1305 | > > | Known Issues in ODs 1304 & 1305 | | For (yet) unknown reasons, the three detectors PSW-B5, PSW-E9 and PSW-F8 - that use to behave well during the entire mission - were noisy during the two operational days 1304 and 1305. The result are stripes visible in the final PSW map which the current (HIPE 10) pipeline is not able to correct. The solution is to mask and exclude these detectors from the analysis. This could be done in 2 ways:
- You can use the
SpireMaskEditor GUI as described in sec. 7.4.2 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to Master all samples in all scans (listed as BBID) for the detectors mentioned above.
- Alternatively, you can use the following line of codes:
| |
A listing of the available Dark Sky observations can be found here. | |
< < | Spectral Cube Analysis | > > | Spectral Cube Analysis | |
Spectral cubes are produced by the Spectrometer pipeline for mapping observations. Some tips, suggestions and examples of spectral cube analysis for SPIRE data are provided here. | |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE A&A paper, Griifin et al 2010" date="1295862676" name="aa14519-10.pdf" path="aa14519-10.pdf" size="1353253" user="Main.AnthonyMarston" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1370344174" name="SpireHfiColourCorrTab_v1.1.fits" path="SpireHfiColourCorrTab_v1.1.fits" size="20160" user="Main.LucaConversi" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Cookbooks are provided inside the SPIRE Data Reduction Guide (see above). | |
< < | The standalone "Photometry Cookbook", is no longer maintained - it is being incorporated into the SPIRE DRG - please see the SDRG for photometry cookbook information, and raise a Helpdesk ticket if you find something missing. | > > | The standalone "Photometry Cookbook", is no longer maintained - it is being incorporated into the SPIRE DRG - please see the SDRG for photometry cookbook information, and raise a Helpdesk ticket if you find something missing. | |
SPIRE calibration file versions |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | | | |
> > |
- Documents with relevance to the SPIRE flux calibration:
| |
AOT release notes | |
Photometer calibration | |
< < |
- SPIRE Photometer Calibration:
- Full details of the SPIRE calibration can be found in the SPIRE Observers Manual and in dedicated journal papers (Bendo et al. 2013, North et al. 2013)
- Point Source Flux Calibration ~ ± 7%
- ~ 5% absolute from Neptune model
- ~2% relative from Neptune photometry
- Extended emission Calibration ~ ± 11%
- additional ~4% due to uncertainty in the measured beam area
- Additionally repeatability of measured photometry to flux densities >100mJy ~ 2%
| > > |
- SPIRE Photometer Calibration:
Full details of the SPIRE calibration can be found in the SPIRE Observers Manual and in dedicated publications: the calibration scheme is described in Griffin et al. (2013) and the implementation using Neptune as the primary calibration standard, is described in Bendo et al. (2013).
- Calibration uncertainties, which should be included in addition to the statistical errors of any measurement, are as follows:
- ± 4% absolute from Neptune model (this uncertainty is systematic and correlated across the three bands)
- ± 1.5% (random) from Neptune photometry
- Extended emission calibration
| |
- SPIRE Photometer Beams:
- These are available in the SPIRE calibration context, at the standard map pixel size of (6,10,14) arcsec/pixel for (250,350,500) µm bands, and can be accessed in HIPE after a calibration context has been loaded (see above).
| |
-
- These are also available in the SPIRE calibration context (photRsrf) and can be accessed in HIPE after a calibration context has been loaded (See above).
- Neptune and Uranus models used for the SPIRE photometer flux calibration:
| |
< < |
-
- The ESA2 models currently used in the SPIRE calibration are available here
.
| > > |
-
- The ESA2 models of the SPIRE calibration, used up to HIPE v10 and
spire_cal_10_1 , are available here .
-
The ESA4 models of the SPIRE calibration, used from HIPE v11 and spire_cal_11_0 , are available here .
| |
Spectrometer calibration | |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.7" date="1345816678" name="SPIRE_SpectrometerLaunchPad_v1.7.pdf" path="SPIRE_SpectrometerLaunchPad_v1.7.pdf" size="195133" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="Sensitivity of the SPIRE Detectors to Operating Parameters" date="1369124238" name="SPIRE_Detector_Parameter_Sensitivity_Issue_1_Nov_14_2007.pdf" path="SPIRE_Detector_Parameter_Sensitivity_Issue_1_Nov_14_2007.pdf" size="189448" user="Main.IvanV" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.6" date="1345816649" name="SPIRE_DataLaunchPad_v1.6.pdf" path="SPIRE_DataLaunchPad_v1.6.pdf" size="205212" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v10.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 10.0 build 2747.
| > > | | |
-
-
Please note that there was a bug in the destriper task included in HIPE 9.0 that may affect your final map, especially if there are bright objects in the observed field. This has been corrected since HIPE 9.1. If your observation falls in the mentioned category, you are strongly advised to update your HIPE installation.
- We also provide access to the latest stable developer build (latest stable CIB).
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Photometer calibration | |
> > |
- SPIRE Photometer Calibration:
- Full details of the SPIRE calibration can be found in the SPIRE Observers Manual and in dedicated journal papers (Bendo et al. 2013, North et al. 2013)
- Point Source Flux Calibration ~ ± 7%
- ~ 5% absolute from Neptune model
- ~2% relative from Neptune photometry
- Extended emission Calibration ~ ± 11%
- additional ~4% due to uncertainty in the measured beam area
- Additionally repeatability of measured photometry to flux densities >100mJy ~ 2%
| |
- SPIRE Photometer Beams:
- These are available in the SPIRE calibration context, at the standard map pixel size of (6,10,14) arcsec/pixel for (250,350,500) µm bands, and can be accessed in HIPE after a calibration context has been loaded (see above).
-
The observed beams at much finer scale of 1 arcsec/pixel, as well as the theoretical ones, are available from here . Please read the release note for more details.
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
-
- Currently, the quality flags at the quality context inside the observation context are just meant for HSC/ICC internal evaluation of the quality of the products and not for the users. In case the data had some serious quality problem, the PI of the program has been contacted about it. Otherwise, only information in the quality summary, when available, should concern the observers.
Known Issues in ODs 1304 & 1305 | |
< < |
- For (yet) unknown reasons, the three detectors PSW-B5, PSW-E9 and PSW-F8 - that use to behave well during the entire mission - were noisy during the two operational days 1304 and 1305. The result are stripes visible in the final PSW map which the current (HIPE 10) pipeline is not able to correct. The solution is to mask and exclude these detectors from the analysis. This could be done in 2 ways:
- You can use the
SpireMaskEditor GUI as described in sec. 7.4.2 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to MASTER all
| > > | For (yet) unknown reasons, the three detectors PSW-B5, PSW-E9 and PSW-F8 - that use to behave well during the entire mission - were noisy during the two operational days 1304 and 1305. The result are stripes visible in the final PSW map which the current (HIPE 10) pipeline is not able to correct. The solution is to mask and exclude these detectors from the analysis. This could be done in 2 ways:
- You can use the
SpireMaskEditor GUI as described in sec. 7.4.2 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to Master all samples in all scans (listed as BBID) for the detectors mentioned above.
- Alternatively, you can use the following line of codes:
##### EDIT MASK SCRIPT BEGINS #####
# List of detectors to be masked
bolos = ['PSWB5', 'PSWE9', 'PSWF8']
# Level1 of your observation, assuming the observation context varible is named 'obs'
level1 = obs.level1
# Create new level 1
new_l1 = Level1Context()
for scan in range(0, level1.getCount()):
#
# Load level 1 product, scan by scan
data = level1.refs[scan].product
#
# Change mask for selected detectors in all scans, setting it to MASTER
for bolo in bolos:
data['mask'][bolo].data[:] = 1
#
new_l1.addProduct(data)
##### EDIT MASK SCRIPT ENDS #####
- After either of those cases, you must then re-run level 1 to 2 steps on the newly modified level1 product. If your observation has been already re-reduced with HIPE 10, original and new level1s are already destriped, so you can directly run the naive map-maker on the new level1. Otherwise, you must run the destriper step: check the pipeline script for details.
| |
Source Extraction and Photometry |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
- Quality flags in the quality context
- Currently, the quality flags at the quality context inside the observation context are just meant for HSC/ICC internal evaluation of the quality of the products and not for the users. In case the data had some serious quality problem, the PI of the program has been contacted about it. Otherwise, only information in the quality summary, when available, should concern the observers.
| |
> > | Known Issues in ODs 1304 & 1305
- For (yet) unknown reasons, the three detectors PSW-B5, PSW-E9 and PSW-F8 - that use to behave well during the entire mission - were noisy during the two operational days 1304 and 1305. The result are stripes visible in the final PSW map which the current (HIPE 10) pipeline is not able to correct. The solution is to mask and exclude these detectors from the analysis. This could be done in 2 ways:
- You can use the
SpireMaskEditor GUI as described in sec. 7.4.2 of the SPIRE Data Reduction Guide: write-click on your observation context variable and then select Level1_SpireMaskEditor and set to MASTER all
| | Source Extraction and Photometry
- The current recommended method for photometry
sourceExtractorTimeline task (formerly known as the Timeline Fitter) which works on the detector timelines. The Map based algorithm sourceExtractorSussex (SUSSEXtractor) providers good results and is useful on larger maps where the sourceExtractorTimeline will be significantly slower. sourceExtractorDaophot (DAOphot) also provides a reasonable estimate of the source flux but may require an aperture correction.
| |
Contact the Helpdesk | |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.7" date="1345816678" name="SPIRE_SpectrometerLaunchPad_v1.7.pdf" path="SPIRE_SpectrometerLaunchPad_v1.7.pdf" size="195133" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.6" date="1345816649" name="SPIRE_DataLaunchPad_v1.6.pdf" path="SPIRE_DataLaunchPad_v1.6.pdf" size="205212" user="Main.ChrisPearson" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE A&A paper, Griifin et al 2010" date="1295862676" name="aa14519-10.pdf" path="aa14519-10.pdf" size="1353253" user="Main.AnthonyMarston" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
More details of the changes in each version are given here . | |
< < | Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_10_1") etc. The default (applicable to the Hipe version) can be obtained with cal = spireCal(calTree="spire_cal")
The latest calibration context for SPIRE can be obtained as a .zip file from Latest calibration trees . The zipped file is a pool, so it should be unpacked in the local store folder and then loaded in HIPE with cal = spireCal(pool="spire_cal_10_1") . | > > |
- Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.)
cal = spireCal(calTree="spire_cal_10_1") etc. The default (applicable to the HIPE version in use) can be obtained with cal = spireCal(calTree="spire_cal") . It can then be saved to a local pool right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- Alternatively, the latest calibration tree for SPIRE can be obtained as a jar file from Latest calibration trees
. Then, you have to possibilities to read and save:
- The jar file can be load directly into HIPE with the command:
cal = spireCal(jarFile="PATH_TO_FILE/spire_cal_10_1.jar") . To save it to a local pool, proceed as described above, right-clicking on the cal variable and then selecting from the context menu Send To -> Local Pool.
- The jar file can also be saved directly to a local pool without opening HIPE, running the following command in the terminal command line:
cal_import PATH_TO_FILE/spire_cal_10_1.jar . Then, to load the calibration tree in HIPE, simply type: cal = spireCal(pool="spire_cal_10_1")
| |
See the SPIRE Data Reduction Guide for more details. |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.2.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 9.0 build 3089.
| > > |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v10.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 10.0 build 2747.
| |
-
-
Please note that there was a bug in the destriper task included in HIPE 9.0 that may affect your final map, especially if there are bright objects in the observed field. This has been corrected since HIPE 9.1. If your observation falls in the mentioned category, you are strongly advised to update your HIPE installation.
- We also provide access to the latest stable developer build (latest stable CIB).
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
- Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here:
| |
< < | | > > | | |
- SPIA: The SPIRE Photometer Interactive Analysis (SPIA) package is available as a plug-in for HIPE. SPIA provides a structured GUI based access to the more intricate parts of the scan map photometer pipeline for SPIRE without the immediate need to resort to scripts. More information can be found in the SDRG or on the SPIA web page
| | Overview
The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered. | |
< < |
- Note that SPIRE maps are in units of Jy/beam, and are calibrated in the assumption of a point source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.2 of the SPIRE Observers' Manual .
- The SPIRE Photometer filter transmission curves, also known as Relative Spectral Response Functions (RSRF) are available here
. For more details, please read the .readme file in this ftp folder.
| | New definition of Leve2 products | |
< < |
- For versions of the HCSS prior to HIPE 10.0, a single point source calibrated (Janskys/beam) map was provided in the Level 2 product for each of the PSW, PMW, PLW bands. However, for observations processed with HIPE 10.0 or later, more than one map calibration is made available within the Level 2 product. Maps are provided for the following scenarios for post HIPE 10.0 processing;
| > > |
- For versions of the HCSS prior to HIPE 10.0, a single point source calibrated (Jy/beam) map was provided in the Level 2 product for each of the PSW, PMW, PLW bands. However, for observations processed with HIPE 10.0 or later, more than one map calibration is made available within the Level 2 product. Maps are provided for the following scenarios for post HIPE 10.0 processing:
| |
| |
Extended Emission Destriper Diagnostic |
extdPSWdiag |
- |
|
|
|
| |
> > |
- psrcPxW are the previous PxW maps, calibrated for point source and in units of Jy/beam. Note that to do aperture photometry on such maps you'll first need to convert them to surface brightness (Jy/pixel, MJy/sr, etc.), although it is suggested to directly use the already extended emission calibrated extdPxW maps. Finally, bear in mind that SPIRE itself cannot measure the absolute sky flux, hence psrcPxW maps have an arbitrary offset having zero median.
- ssoPxW maps are corrected for SSO proper motion: maps are in Jy/beam and they are subject to the same photometry rules of the psrcPxW maps.
- extdPxW maps are calibrated for extended emission and provided in units of MJy/sr. These maps are provided with an estimation of the absolute offset via cross-calibration with Planck data.
- In all cases, SPIRE data is calibrated in the assumption of source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.7 of the SPIRE Data Reduction Guide.
- The SPIRE Photometer filter transmission curves, also known as Relative Spectral Response Functions (RSRF) are available here
. For more details, please read the .readme file in this ftp folder.
| | Data Processing Issues
The main issues that you might find in your data are: undetected glitches, thermistor or detector jumps, and bad baseline removal. | |
SPIRE Calibration Tree |
Applicable HIPE Version |
Comment |
| |
< < |
SPIRE_CAL_9_1 |
HIPE v9 |
Final v9 cal tree, currently used in operations. |
| > > |
SPIRE_CAL_10_1 |
HIPE v10 |
Calibration tree currently used in operations |
SPIRE_CAL_9_1 |
HIPE v9 |
Final v9 cal tree |
| |
SPIRE_CAL_8_1 |
HIPE v8 |
Final v8 cal tree |
SPIRE_CAL_7_0 |
HIPE v7 |
Final v7 cal tree. |
SPIRE_CAL_6_1 |
HIPE v6 |
Final v6 cal tree |
| | Contact the Helpdesk
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.7" date="1345816678" name="SPIRE_SpectrometerLaunchPad_v1.7.pdf" path="SPIRE_SpectrometerLaunchPad_v1.7.pdf" size="195133" user="Main.ChrisPearson" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.6" date="1345816649" name="SPIRE_DataLaunchPad_v1.6.pdf" path="SPIRE_DataLaunchPad_v1.6.pdf" size="205212" user="Main.ChrisPearson" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE A&A paper, Griifin et al 2010" date="1295862676" name="aa14519-10.pdf" path="aa14519-10.pdf" size="1353253" user="Main.AnthonyMarston" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Photometer data reduction | |
> > | Overview | | The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered. | |
< < | | |
- Note that SPIRE maps are in units of Jy/beam, and are calibrated in the assumption of a point source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.2 of the SPIRE Observers' Manual .
- The SPIRE Photometer filter transmission curves, also known as Relative Spectral Response Functions (RSRF) are available here
. For more details, please read the .readme file in this ftp folder.
| |
- The SPIRE Photometer filter transmission curves, also known as Relative Spectral Response Functions (RSRF) are available here
. For more details, please read the .readme file in this ftp folder.
| |
> > | New definition of Leve2 products
- For versions of the HCSS prior to HIPE 10.0, a single point source calibrated (Janskys/beam) map was provided in the Level 2 product for each of the PSW, PMW, PLW bands. However, for observations processed with HIPE 10.0 or later, more than one map calibration is made available within the Level 2 product. Maps are provided for the following scenarios for post HIPE 10.0 processing;
Description |
New Name (HIPE10+) |
Original (pre-HIPE10) Name |
Point Source (standard) Maps |
psrcPSW |
PSW |
Extended Emission Maps |
extdPSW |
- |
Solar System Object Maps |
ssoPSW |
- |
Point Source Destriper Diagnostic |
psrcPSWdiag |
pddPSW |
Extended Emission Destriper Diagnostic |
extdPSWdiag |
- |
|
|
|
Data Processing Issues | |
The main issues that you might find in your data are: undetected glitches, thermistor or detector jumps, and bad baseline removal. |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Further information | |
< < | Contact the Helpdesk | > > | Contact the Helpdesk | |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.7" date="1345816678" name="SPIRE_SpectrometerLaunchPad_v1.7.pdf" path="SPIRE_SpectrometerLaunchPad_v1.7.pdf" size="195133" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.1.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 9.0 build 3071.
-
Please note that there was a bug in the destriper task included in HIPE 9.0.0 that may affect your final map, especially if there are bright objects in the observed field. This has been corrected in HIPE 9.1.0. If your observation falls in the mentioned category, you are strongly advised to update your HIPE installation.
| > > |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.2.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 9.0 build 3089.
-
Please note that there was a bug in the destriper task included in HIPE 9.0 that may affect your final map, especially if there are bright objects in the observed field. This has been corrected since HIPE 9.1. If your observation falls in the mentioned category, you are strongly advised to update your HIPE installation.
| |
- We also provide access to the latest stable developer build (latest stable CIB).
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
| |
Contact the Helpdesk | |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.7" date="1345816678" name="SPIRE_SpectrometerLaunchPad_v1.7.pdf" path="SPIRE_SpectrometerLaunchPad_v1.7.pdf" size="195133" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.6" date="1345816649" name="SPIRE_DataLaunchPad_v1.6.pdf" path="SPIRE_DataLaunchPad_v1.6.pdf" size="205212" user="Main.ChrisPearson" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE A&A paper, Griifin et al 2010" date="1295862676" name="aa14519-10.pdf" path="aa14519-10.pdf" size="1353253" user="Main.AnthonyMarston" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | | Software and documentation
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.1.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 9.0 build 3071.
| |
< < |
-
-
Please note that there was a bug in the destriper task included in HIPE 9.0.0 that may affect your final map, especially if there are bright objects in the observed field. This has been corrected in HIPE 9.1.0. If you observation falls in the mentioned category, you are strongly advised to update your HIPE installation.
| > > |
-
-
Please note that there was a bug in the destriper task included in HIPE 9.0.0 that may affect your final map, especially if there are bright objects in the observed field. This has been corrected in HIPE 9.1.0. If your observation falls in the mentioned category, you are strongly advised to update your HIPE installation.
| |
- We also provide access to the latest stable developer build (latest stable CIB).
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.0.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 9.0 build 2974. Please note that there is a bug in the destriper task included in HIPE 9.0.0 that may affect your final map, especially if there are bright objects in the observed field: this will be fixed in the upcoming new release of HIPE!
| > > |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.1.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 9.0 build 3071.
-
Please note that there was a bug in the destriper task included in HIPE 9.0.0 that may affect your final map, especially if there are bright objects in the observed field. This has been corrected in HIPE 9.1.0. If you observation falls in the mentioned category, you are strongly advised to update your HIPE installation.
| |
- We also provide access to the latest stable developer build (latest stable CIB).
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
- SPIRE Photometer Beams:
- These are available in the SPIRE calibration context, at the standard map pixel size of (6,10,14) arcsec/pixel for (250,350,500) µm bands, and can be accessed in HIPE after a calibration context has been loaded (see above).
-
The observed beams at much finer scale of 1 arcsec/pixel, as well as the theoretical ones, are available from here . Please read the release note for more details.
| |
> > |
-
-
A new more detailed analysis of the SPIRE beam profile data was undertaken in 2012, leading to revised values for beam profile solid angles and derivation of a semi empirical wavelength dependent beam profile model. The results at a scale of 1 arcsec/pixel as well as the data needed for the model are available for download. A detailed description of the analysis is given as well.
| |
- SPIRE Photometer filter transmission curves:
- These are also available in the SPIRE calibration context (photRsrf) and can be accessed in HIPE after a calibration context has been loaded (See above).
| |
Contact the Helpdesk | |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.7" date="1345816678" name="SPIRE_SpectrometerLaunchPad_v1.7.pdf" path="SPIRE_SpectrometerLaunchPad_v1.7.pdf" size="195133" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.6" date="1345816649" name="SPIRE_DataLaunchPad_v1.6.pdf" path="SPIRE_DataLaunchPad_v1.6.pdf" size="205212" user="Main.ChrisPearson" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE A&A paper, Griifin et al 2010" date="1295862676" name="aa14519-10.pdf" path="aa14519-10.pdf" size="1353253" user="Main.AnthonyMarston" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
- Note that SPIRE maps are in units of Jy/beam, and are calibrated in the assumption of a point source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.2 of the SPIRE Observers' Manual .
| |
> > |
- The SPIRE Photometer filter transmission curves, also known as Relative Spectral Response Functions (RSRF) are available here
. For more details, please read the .readme file in this ftp folder.
| |
The main issues that you might find in your data are: undetected glitches, thermistor or detector jumps, and bad baseline removal. |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
| |
< < |
| > > |
| |
Photometer data reduction | |
Contact the Helpdesk | |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.5" date="1328875003" name="SPIRE_PhotometerLaunchPad_v1.5.pdf" path="SPIRE_PhotometerLaunchPad_v1.5.pdf" size="207962" user="Main.ChrisPearson" version="2" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.6" date="1331743712" name="SPIRE_PhotometerLaunchPad_v1.6.pdf" path="SPIRE_PhotometerLaunchPad_v1.6.pdf" size="209303" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.6" date="1328388627" name="SPIRE_SpectrometerLaunchPad_v1.6.pdf" path="SPIRE_SpectrometerLaunchPad_v1.6.pdf" size="196595" user="Main.ChrisPearson" version="1" |
| > > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.7" date="1345816678" name="SPIRE_SpectrometerLaunchPad_v1.7.pdf" path="SPIRE_SpectrometerLaunchPad_v1.7.pdf" size="195133" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.6" date="1345816649" name="SPIRE_DataLaunchPad_v1.6.pdf" path="SPIRE_DataLaunchPad_v1.6.pdf" size="205212" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.5" date="1328388567" name="SPIRE_DataLaunchPad_v1.5.pdf" path="SPIRE_DataLaunchPad_v1.5.pdf" size="208221" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.7" date="1345816708" name="SPIRE_PhotometerLaunchPad_v1.7.pdf" path="SPIRE_PhotometerLaunchPad_v1.7.pdf" size="210362" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE A&A paper, Griifin et al 2010" date="1295862676" name="aa14519-10.pdf" path="aa14519-10.pdf" size="1353253" user="Main.AnthonyMarston" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.0.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 9.0 build 2974.
| > > |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.0.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 9.0 build 2974. Please note that there is a bug in the destriper task included in HIPE 9.0.0 that may affect your final map, especially if there are bright objects in the observed field: this will be fixed in the upcoming new release of HIPE!
| |
- We also provide access to the latest stable developer build (latest stable CIB).
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Spectral Cube Analysis | |
< < | Spectral cubes are produced by the Spectrometer pipeline for mapping observations. Some tips, suggestions and examples of spectral cube analysis for SPIRE data are provided here. | > > | Spectral cubes are produced by the Spectrometer pipeline for mapping observations. Some tips, suggestions and examples of spectral cube analysis for SPIRE data are provided here. | |
Cookbooks |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Contact the Helpdesk | |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.5" date="1328875003" name="SPIRE_PhotometerLaunchPad_v1.5.pdf" path="SPIRE_PhotometerLaunchPad_v1.5.pdf" size="207962" user="Main.ChrisPearson" version="2" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.6" date="1331743712" name="SPIRE_PhotometerLaunchPad_v1.6.pdf" path="SPIRE_PhotometerLaunchPad_v1.6.pdf" size="209303" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.6" date="1328388627" name="SPIRE_SpectrometerLaunchPad_v1.6.pdf" path="SPIRE_SpectrometerLaunchPad_v1.6.pdf" size="196595" user="Main.ChrisPearson" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1306492467" name="maskTimelines.py.txt" path="maskTimelines.py.txt" size="5945" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1312967015" name="bendoSourceFit_v0_9.py.txt" path="bendoSourceFit_v0_9.py.txt" size="26358" user="Main.IvanV" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
| > > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.5" date="1328388567" name="SPIRE_DataLaunchPad_v1.5.pdf" path="SPIRE_DataLaunchPad_v1.5.pdf" size="208221" user="Main.ChrisPearson" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.5" date="1328875003" name="SPIRE_PhotometerLaunchPad_v1.5.pdf" path="SPIRE_PhotometerLaunchPad_v1.5.pdf" size="207962" user="Main.ChrisPearson" version="2" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.6" date="1331743712" name="SPIRE_PhotometerLaunchPad_v1.6.pdf" path="SPIRE_PhotometerLaunchPad_v1.6.pdf" size="209303" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photo cookbook" date="1313054871" name="SPIREPhotometryCookbook_jul2011_2.pdf" path="SPIREPhotometryCookbook_jul2011_2.pdf" size="63443" user="Main.IvanV" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
| > > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE A&A paper, Griifin et al 2010" date="1295862676" name="aa14519-10.pdf" path="aa14519-10.pdf" size="1353253" user="Main.AnthonyMarston" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages
| |
> > | Back to main Herschel Public TWiki page | | Introduction
This page provides up-to-date information about using the SPIRE instrument: from preparing observations to reducing your data. This page also provides you with the latest calibration accuracies and known SPIRE calibration issues.
Observing with SPIRE | |
< < | The most up to date information on instrument calibration and performance is given in the SPIRE Observers' Manual. This is the reference document used by all the rest of the SPIRE user guides (eg data reduction guide, cookbooks etc). Sometimes it may happen that outdated values are quoted in some of the documents. In such a case use the values given in the SPIRE Observers' Manual. | > > | The most up to date information on instrument calibration and performance is given in the SPIRE Observers' Manual. This is the reference document used by all the rest of the SPIRE user guides (eg data reduction guide, cookbooks etc). Sometimes it may happen that outdated values are quoted in some of the documents. In such a case use the values given in the SPIRE Observers' Manual. | | | |
< < |
- The SPIRE Observer's Manual (HTML) and PDF (15.5 MB).
We recommend using the PDF version (search and hyperlinks work) because the HTML version has some formatting problems due to the conversion from LaTeX to HTML.
- A quick guide to the SPIRE instrument: SPIRE fact sheet
- Summary papers from the A&A Special Issue:
Some values on the performance are now outdated. Please consult the SPIRE Observers' Manual for most up to date information.
| > > | | |
-
- The Herschel-SPIRE instrument and its in-flight performance, Griffin et al., 2010, A&A, 518, L3, in-flight scientific capabilities of the SPIRE instrument.
- In-flight calibration of the Herschel-SPIRE instrument: Swinyard et al., 2010, A&A, 518, L4
- Detailed documents describing the pipeline algorithms (to be updated soon):
| |
< < | | > > | | |
AOT release notes | |
< < | Photometer
- Photometer point source mode
- Photometer small scan map mode
Spectrometer
- FTS point source mode (sparse)
| | | |
< < |
- FTS mapping mode (intermediate, full)
| > > |
| |
Reducing SPIRE data | |
< < | In order to obtain the best possible Level 2 SPIRE photometry or spectroscopy data, the observations might have to be reprocessed with the latest HIPE User Release. | | Software and documentation | |
< < |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.0.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. FYI: this corresponds to the so-called CIB (continuous integration build) HIPE 9.0 build 2974.
| > > |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.0.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. This corresponds to the developer's CIB (Continuous Integration Build) HIPE 9.0 build 2974.
- We also provide access to the latest stable developer build (latest stable CIB).
- Beware These developer builds do not undergo the same in-depth testing as the user releases do. The latest developer build can be found here.
| | | |
< < |
- We also provide access to the latest stable developer build (a.k.a latest stable CIB), used by the instrument experts at the ICC.
- Beware _These developer builds do not undergo the same in-depth testing as the user releases do. The current latest stable developer build can be found here.
| > > |
- Within HIPE you can access all the SPIRE data reduction and HIPE-user documentation. The SPIRE Data Reduction Guide (SDRG) follows the user pipeline scripts and also explains the details of pipeline processing and data analysis. It is also available online here:
| | | |
< < |
- Within HIPE you can access all the SPIRE data reduction and HIPE-use documentation. For those who wish to read the SPIRE Data Reduction Guide (SDRG) in PDF form, we provide that here: SDRG version 2.1. This version can be used with HIPE v9.0.0 as well as all track 9 of the CIBs. (Note that within the PDF version, document links will not work.) The SDRG follows the pipeline scripts (see "Cookbooks" below) and also explains what you are doing as you pipeline process.
| > > |
- SPIA: The SPIRE Photometer Interactive Analysis (SPIA) package is available as a plug-in for HIPE. SPIA provides a structured GUI based access to the more intricate parts of the scan map photometer pipeline for SPIRE without the immediate need to resort to scripts. More information can be found in the SDRG or on the SPIA web page
| | | |
< < | | | | |
< < |
- SPIA: The SPIRE Photometer Interactive Analysis (SPIA) is available as a plug-in for HIPE. SPIA provides a structured GUI based access to the more intricate parts of the scan map photometer pipeline for SPIRE without the immediate need to resort to scripts. More information can be found on the SPIA web page
| |
The SPIRE Launch Pads
- The SPIRE Launch Pads are single sheet quick entries (like a cheat sheet) into SPIRE data reduction and providing quick references to the relevant sections in the SPIRE Data Reduction Guide. There are launch pads for Data Access, SPIRE Photometer and Spectrometer data reduction.
| |
< < |
| > > |
| |
Photometer data reduction | |
< < | Maps | > > | The best source of information for reducing SPIRE Photometer data is the SPIRE Data Reduction Guide available through the HIPE help. This runs through the User Pipeline scripts step by step, describes several other Useful Scripts, and offers advice for specific issues that might be encountered. | | | |
< < |
- Note that SPIRE maps are in units of Jy/beam, and are calibrated in the assumption of a point source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.2 of the SPIRE Observers' Manual .
- By default, the SPIRE pipeline uses a näive map-maker. In this case, the error map is simply the standard deviation of all the data points falling into a given pixel. As a consequence, error maps contain increased errors associated with binning data from Gaussian sources, producing a torus shape; this is an artefact of the map-making process.
| | | |
< < | Level 2.5 | > > |
- Note that SPIRE maps are in units of Jy/beam, and are calibrated in the assumption of a point source having a spectral index equal to -1, i.e. νSν = const. To calibrate your data for other cases or convert to e.g. Jy/sr, please refer to section 5.2 of the SPIRE Observers' Manual .
| | | |
< < |
- As of HIPE 6.1.1, SPIRE observations may include a new Level 2.5. This product includes maps obtained merging all contiguous observations belonging to the same program and having same observing mode (i.e. small map, large map or Parallel Mode). Maps are produced using the standard pipeline, i.e.:
- query the database to retrieve all the required observations
- merge all Level 1s
- remove the baseline using a median fit from each scan
- build the maps using the näive map-maker
- All the photometer known issues applies to these maps as well. Moreover, note that:
- no astrometry fix is applied, so sources may be blurred/_duplicated_ if the shift between 2 or more observations is big (>5 arcsec);
- in merging together multiple observations of the same field, you may not notice anymore some artifacts such as undetected glitches, temperature drifts or detectors jumps. In both cases, you need to re-reduce the data with the tips suggested below.
- The list of observations used to build the Level 2.5 maps are included in the observations' metadata.
| | | |
< < | Solar System objects | > > | The main issues that you might find in your data are: undetected glitches, thermistor or detector jumps, and bad baseline removal. | | | |
< < |
- When the target is a Solar System Object (SSO) having a proper motion, the spacecraft re-adjusts its position after each scan, in order to always be centred on the target. However, the products retrieved from the Herschel Science Archive have been reduced using a standard pipeline which does not correct for the target's proper motion. As a result, the background of SSO observations will be focused while the SSO itself will appear blurred (for short observations or slow objects) or as a streak (for longer ones or faster objects).
- As of HIPE 8.0, a new script named SSO_MotionCorrection is available under the SPIRE Useful Scripts menu. The script computes the SSO speed in RA & Dec coordinates, applies the required shift to Level 1 timelines, computes the corrected maps and eventually saves the modified products to a local pool. The results are maps centred on the SSO (i.e. the target will appear focused) with a smooth/blurred background. More details can be found in the SPIRE Data Reduction Guide.
Data processing known issues | |
- Stripes in PSW, PMW and/or PLW (Level 2) maps
| |
< < |
-
- All SPIRE photometry pipelines now use by default the destriper, which improves the issue of striping in level 2 maps. Hence observers should expect potential improvements in that respect with version 9.
<-- * Stripes in PSW, PMW and/or PLW (Level 2) maps
-
- Most of the stripes that are present in the final maps are due to a combination of thermal drifts (which in few cases are not efficiently removed) and median baseline subtraction. A similar effect is caused by very bright sources: in this case, the problem resides in the median baseline subtraction only.
- Suggested solutions:
- switch to a baseline subtraction using a polynomial fitting using the optional task
baselineRemovalPolynomial . If there are no jumps in the timelines, you may also try to run the baseline removal on the entire timeline;
- in the case of bright sources, you may try to mask them before running the baseline removal (either median or polynomial): you can use this script as a template.;
- use the SPIRE Destriper: this new task is giving good results in most cases, especially for diffuse emission and extended sources. In the case of Parallel Mode observations, although the destroyer will work on single scans it is always better to merge 2 or more observations together using the map merge script within HIPE. The destriper documentation can be found on the NHSC website
-->
| > > |
-
- All SPIRE photometry pipelines now use the destriper by default, which improves the issue of stripes in Level 2 maps. There should be noticeable improvements in that respect with HIPE version 9. The destriper documentation can be found on the NHSC website
| |
- De-glitcher masks faint sources
| |
< < |
-
- The de-glitcher is a very delicate process. In particular, for data taken in Parallel Mode (sampling at 10Hz) and at high speed (60"/s) the de-glitcher with standard parameters may flag very faint sources as glitches. Bright sources are different from glitches in that they have a Gaussian (i.e. beam/PSF) shape. For faint sources, the sampling rate could be not high enough and hence they have a "delta" shape, which is similar to a small glitch. The user might try to modify the correlation parameter to 0.95: this will decrease the number of detected glitches. In case of high scan rate and low sampling speed one may want to stay with a limited level 1 detection rate and defer to Level 2 deglitching.
- Some sources have saturated the ADC and the corresponding data have been masked
- There is nothing a user can do: the source was simply too bright. If the user has other sources still not observed and of the same intensity, it is suggested to change the AORs to use the bright source mode.
- Thermistor jumps
- As of HIPE 6.0.3, a new module together called signalJumpDetector in place to identify the jump and to exclude the affected thermistor(s).
- This module should not be run with observations in bright mode as it can lead to too many unnecessarily excluded scans. Jumps seem not to occur in bright mode.
- Cooler temperature variations
- After the end of the SPIRE cooler recycle, the temperature is few mK below the plateau (i.e. the most stable value which lasts for about 40h): it takes about 7h to reach it. Between 6 to 7h after the cooler recycle ends, its temperature raises steeply and reaches the plateau. At present, the pipeline is not able to cope with these strong temperature variations (although a correction script is planned for HIPE v.9), hence observations taken during such times may exhibit stripes in the final maps (especially for extragalactic fields). To solve this, the user can try a baseline polynomial fit of order >2 on the entire baseline - or use the destriper.
- NaNs pixels present in the PSW, PMW and/or PLW (Level 2) maps
- This effect, related to data masked for various reasons and poor coverage (not enough redundancy), is more evident in single fast-scan Parallel Mode maps. To avoid NaNs, increase the pixel's dimension (i.e., decrease the map's resolution).
- This effect can also happen with destriped maps. In this case check if increasing the sigma or switching off the Level 2 deglitcher helps.
<-- Especially the HIPE 8 destriper should not be currently used with the Level 2 deglitcher active. -->
<-- * WCS in 3-colour images
-
- In all observation reduced with HIPE 8, the task
createRgbImage puts wrong WCS in the output. Instead of using the WCS provided by the WCS input parameter, this task uses the WCS of one of the input images. This has been fixed in HIPE 9
-->
- Quality flags in the quality context
- Currently, the quality flags at the quality context inside the observation context are just meant for HSC/ICC internal evaluation of the quality of the products and not for the users. In case the data had some serious quality problem, the PI of the program has been contacted about it. Otherwise, only information in the quality summary, when available, should concern the observers.
Tips to re-reduce your data
- Always remember to update to the latest calibration tree compatible with the HIPE built you are using (See the SPIRE Data Reduction Guide, Chapter 3 for a detailed explanation and examples). Assuming the observation is loaded into HIPE as a variable named
obs :
cal = spireCal(calTree="spire_cal")
obs.calibration.update(cal)
- If the observation you retrieved from HSA has been reduced with SPG v. 2.x or less, than start reprocessing from level 0 (i.e., run again the engineering conversion level 0 -> 0.5). In addition, if you want to apply the extended gains correction then reprocessing of the data through the User Pipeline is required for all photometer data processed with HIPE versions earlier than v8.
- Main issues you might find in your data are: undetected glitches, thermistor or detector jumps, bad baseline removal.
- Undetected glitches: you may try to play with the parameters of the
waveletDeglitcher , in particular changing correlationThreshold parameter; other solution is to use the alternative sigmaKappaDeglitcher
<-- * Thermistor jumps: this should be automatically solved re-reducing your observation as of HIPE v.6. If this is not the case, you must exclude the affected thermistor when running the temperatureDriftCorrection adding e.g. pswThermistorSelect='T1'
-
- Failure of Temperature Drift Correction: Due to an update of the Temperature Drift Correction task in the pipeline, the pipeline may fail with an
Index argument 0 is out of range error if run with Calibration Tree spire_cal_6_0 . Please update to at least use spire_cal_6_1 to solve the problem (See the SPIRE Data Reduction Guide, Chapter 3). -->
- Bad baseline removal (see also above) as of Hipe v. 6.x, a new polynomial fit (in comparison to the standard median) for baseline removal has been added as a prototype. Assuming that your Observation Context is stored in a variable named
obs , you can call it as e.g.:
from herschel.spire.ia.pipeline.phot.baseline import BaselineRemovalPolynomialTask
baselineRemovalPolynomial = BaselineRemovalPolynomialTask()
scansBaseline = baselineRemovalPolynomial(input=obs.level1, polyDegree=3)
mapBaseline = naiveScanMapper(input=scansBaseline, array="PLW")
| > > |
-
- For data taken in Parallel Mode in particular (sampling at 10Hz, at high speed 60"/s), the de-glitcher may flag very faint sources as glitches when it is run with standard parameters. Faint sources may have a "delta function" shape due to the low sampling rate, which looks similar to a small glitch. Try modifying the "correlation parameter" to 0.95: this will decrease the number of detected glitches - it may be better to have a limited detection rate in first level deglitching and defer to Level 2 deglitching.
| | | |
< < | | |
Spectrometer data reduction | |
- Faint (<10 Jy) and medium (<100 Jy) strength sources
- Bright sources (>500 Jy)
- Extended sources
| |
> > |
- Observations with few repetitions
| |
For faint sources, the subtraction of instrument, telescope and background emission is particularly important. Optimum subtraction can be performed in several ways (read the SPIRE Data Reduction Guide for details):
- Subtract the Dark Sky spectrum closest to your observation (use the "Background Subtraction" script in HIPE)
- Subtract the spectrum of surrounding detectors (use the "Background Subtraction" script in HIPE)
| |
< < | <-- 3. Substitute the standard teleRsrf calibration file for one derived specifically for the OD of your observation (in the User Pipeline Script in HIPE) --> | |
Dark Sky observations are observed on every SPIRE Spectrometer OD, and are all public in the Archive. | |
< < | A listing of the available Dark Sky observations can be found here.
SPIRE FTS known data processing issues are given here.
<-- In order to obtain the teleRsrf calibration file derived for the OD of your observation and valid for your HIPE/calibration tree version, please raise a Helpdesk ticket (select the "SPIRE FTS" department) specifying the observation that you are trying to process. -->
| > > | Spectral cubes are produced by the Spectrometer pipeline for mapping observations. Some tips, suggestions and examples of spectral cube analysis for SPIRE data are provided here. | |
Cookbooks | |
< < | SPIRE photometry cookbook. | > > | Cookbooks are provided inside the SPIRE Data Reduction Guide (see above). | | | |
< < | The current version of the cookbook is available here and provides practical guidelines on how to do photometry with SPIRE. The cookbook is not HIPE specific. | > > | The standalone "Photometry Cookbook", is no longer maintained - it is being incorporated into the SPIRE DRG - please see the SDRG for photometry cookbook information, and raise a Helpdesk ticket if you find something missing. | |
SPIRE calibration file versions | |
< < | Calibration files for SPIRE can be obtained here:
The available calibration trees for SPIRE are listed below (with the current operational version at the top). More details of the changes in each version are given here . | > > | The available calibration trees for SPIRE are listed below (with the current operational version at the top). | |
SPIRE Calibration Tree |
Applicable HIPE Version |
Comment |
| |
SPIRE_CAL_1_2 |
HIPE v1 |
Phot flux conv based on Ceres |
(SPIRE_CAL_1_1) |
HIPE v1 |
Pre-launch dummy values |
| |
> > | More details of the changes in each version are given here . | | Any of the calibration trees can be retrieved in HIPE from the HSA using (e.g.) | |
< < | cal = spireCal(calTree="spire_cal_9_1") etc. The default (applicable to the HIPE version) can be obtained with cal = spireCal(calTree="spire_cal") | > > | cal = spireCal(calTree="spire_cal_9_1") etc. The default (applicable to the Hipe version) can be obtained with cal = spireCal(calTree="spire_cal")
The latest calibration context for SPIRE can be obtained as a .zip file from Latest calibration trees . The zipped file is a pool, so it should be unpacked in the local store folder and then loaded in HIPE with cal = spireCal(pool="spire_cal_9_1") . | | | |
< < | See the SPIRE Data Reduction Guide for more details. | > > | See the SPIRE Data Reduction Guide for more details. | |
SPIRE calibration and performance
Photometer calibration | |
< < |
- SPIRE Photometer Beams: These are available in the SPIRE calibration context, at the standard map pixel size of (6,10,14) arcsec/pixel for (250,350,500) µm bands, and can be accessed in HIPE after a calibration context has been loaded (see above):
BeamPSW = cal.phot.getBeamProf('PSW')
BeamPMW = cal.phot.getBeamProf('PMW')
BeamPLW = cal.phot.getBeamProf('PLW')
| > > |
- SPIRE Photometer Beams:
- These are available in the SPIRE calibration context, at the standard map pixel size of (6,10,14) arcsec/pixel for (250,350,500) µm bands, and can be accessed in HIPE after a calibration context has been loaded (see above).
-
The observed beams at much finer scale of 1 arcsec/pixel, as well as the theoretical ones, are available from here . Please read the release note for more details.
| | | |
< < | The observed beams at much finer scale of 1 arcsec/pixel, as well as the theoretical ones, are available from here . Please read the release note for more details. | > > |
- SPIRE Photometer filter transmission curves:
- These are also available in the SPIRE calibration context (photRsrf) and can be accessed in HIPE after a calibration context has been loaded (See above).
| | | |
< < |
- SPIRE Photometer filter transmission curves: You can access the filter transmission curves (also known as Relative Spectral Response Function, RSRF) from here
. These are also available in the SPIRE calibration context and can be accessed in HIPE after a calibration context has been loaded (See above):
rsrf = cal.phot.rsrf
- Neptune and Uranus models used for the SPIRE flux calibration: the ESA2 models currently used in the SPIRE calibration are available here
.
| > > |
- Neptune and Uranus models used for the SPIRE photometer flux calibration:
- The ESA2 models currently used in the SPIRE calibration are available here
.
| |
Spectrometer calibration | |
< < | Important FTS information, including calibration, point source and extended source calibration etc, is available in the SPIRE Observers' Manual, Sections 4.2 and 5.3. These two sections are a must-read for anybody processing SPIRE FTS data. | > > | Important FTS information, including details of the calibration, point source and extended source calibration etc, is available in the SPIRE Observers' Manual, Sections 4.2 and 5.3. These two sections are a must-read for anybody processing SPIRE FTS data. | |
Interest groups and scripts | |
Further information | |
< < | | > > | Contact the Helpdesk | |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.6" date="1328388627" name="SPIRE_SpectrometerLaunchPad_v1.6.pdf" path="SPIRE_SpectrometerLaunchPad_v1.6.pdf" size="196595" user="Main.ChrisPearson" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1306492467" name="maskTimelines.py.txt" path="maskTimelines.py.txt" size="5945" user="Main.LucaConversi" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Reducing SPIRE data | |
> > | In order to obtain the best possible Level 2 SPIRE photometry or spectroscopy data, the observations might have to be reprocessed with the latest HIPE User Release. | | Software and documentation
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.0.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. FYI: this corresponds to the so-called CIB (continuous integration build) HIPE 9.0 build 2974.
| |
- As of HIPE 8.0, a new script named SSO_MotionCorrection is available under the SPIRE Useful Scripts menu. The script computes the SSO speed in RA & Dec coordinates, applies the required shift to Level 1 timelines, computes the corrected maps and eventually saves the modified products to a local pool. The results are maps centred on the SSO (i.e. the target will appear focused) with a smooth/blurred background. More details can be found in the SPIRE Data Reduction Guide.
Data processing known issues | |
< < |
- In order to obtain the best possible Level 2 SPIRE photometry data, the observations might have to be reprocessed with the latest HIPE User Release (see above).
| |
- Stripes in PSW, PMW and/or PLW (Level 2) maps
| |
> > |
-
- All SPIRE photometry pipelines now use by default the destriper, which improves the issue of striping in level 2 maps. Hence observers should expect potential improvements in that respect with version 9.
| |
- De-glitcher masks faint sources
- The de-glitcher is a very delicate process. In particular, for data taken in Parallel Mode (sampling at 10Hz) and at high speed (60"/s) the de-glitcher with standard parameters may flag very faint sources as glitches. Bright sources are different from glitches in that they have a Gaussian (i.e. beam/PSF) shape. For faint sources, the sampling rate could be not high enough and hence they have a "delta" shape, which is similar to a small glitch. The user might try to modify the correlation parameter to 0.95: this will decrease the number of detected glitches. In case of high scan rate and low sampling speed one may want to stay with a limited level 1 detection rate and defer to Level 2 deglitching.
| |
A listing of the available Dark Sky observations can be found here. | |
> > | SPIRE FTS known data processing issues are given here. | | <-- In order to obtain the teleRsrf calibration file derived for the OD of your observation and valid for your HIPE/calibration tree version, please raise a Helpdesk ticket (select the "SPIRE FTS" department) specifying the observation that you are trying to process. -->
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v8.2.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. FYI: this corresponds to the so-called CIB (continuous integration build) HIPE 8.0 build 3459.
| > > |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v9.0.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. FYI: this corresponds to the so-called CIB (continuous integration build) HIPE 9.0 build 2974.
| |
- We also provide access to the latest stable developer build (a.k.a latest stable CIB), used by the instrument experts at the ICC.
- Beware _These developer builds do not undergo the same in-depth testing as the user releases do. The current latest stable developer build can be found here.
| |
< < |
- Within HIPE you can access all the SPIRE data reduction and HIPE-use documentation. For those who wish to read the SPIRE Data Reduction Guide (SDRG) in PDF form, we provide that here: SDRG version 2.0. This version can be used with HIPE v8.2.0 as well as all track 8 and track 9 of the CIBs. (Note that within the PDF version, document links will not work.) The SDRG follows the pipeline scripts (see "Cookbooks" below) and also explains what you are doing as you pipeline process.
| > > |
- Within HIPE you can access all the SPIRE data reduction and HIPE-use documentation. For those who wish to read the SPIRE Data Reduction Guide (SDRG) in PDF form, we provide that here: SDRG version 2.1. This version can be used with HIPE v9.0.0 as well as all track 9 of the CIBs. (Note that within the PDF version, document links will not work.) The SDRG follows the pipeline scripts (see "Cookbooks" below) and also explains what you are doing as you pipeline process.
| | | |
- NaNs pixels present in the PSW, PMW and/or PLW (Level 2) maps
- This effect, related to data masked for various reasons and poor coverage (not enough redundancy), is more evident in single fast-scan Parallel Mode maps. To avoid NaNs, increase the pixel's dimension (i.e., decrease the map's resolution).
| |
< < |
-
- This effect can also happen with destriped maps. In this case check if increasing the sigma or switching off the Level 2 deglitcher helps. Especially the HIPE 8 destriper should not be currently used with the Level 2 deglitcher active.
| > > |
-
- This effect can also happen with destriped maps. In this case check if increasing the sigma or switching off the Level 2 deglitcher helps.
<-- Especially the HIPE 8 destriper should not be currently used with the Level 2 deglitcher active. --> | | | |
< < | | > > | | |
- Quality flags in the quality context
- Currently, the quality flags at the quality context inside the observation context are just meant for HSC/ICC internal evaluation of the quality of the products and not for the users. In case the data had some serious quality problem, the PI of the program has been contacted about it. Otherwise, only information in the quality summary, when available, should concern the observers.
| | obs.calibration.update(cal)
| |
< < |
- If the observation you retrieved from HSA has been reduced with SPG v. 2.x or less, than start reprocessing from level 0 (i.e., run again the engineering conversion level 0 -> 0.5). In addition, ff you want to apply the extended gains correction then reprocessing of the data through the User Pipeline is required for all photometer data processed with HIPE versions <8.
| > > |
- If the observation you retrieved from HSA has been reduced with SPG v. 2.x or less, than start reprocessing from level 0 (i.e., run again the engineering conversion level 0 -> 0.5). In addition, if you want to apply the extended gains correction then reprocessing of the data through the User Pipeline is required for all photometer data processed with HIPE versions earlier than v8.
| |
- Main issues you might find in your data are: undetected glitches, thermistor or detector jumps, bad baseline removal.
- Undetected glitches: you may try to play with the parameters of the
waveletDeglitcher , in particular changing correlationThreshold parameter; other solution is to use the alternative sigmaKappaDeglitcher
| |
< < |
-
- Thermistor jumps: this should be automatically solved re-reducing your observation as of HIPE v. 6. If this is not the case, you must exclude the affected thermistor when running the
temperatureDriftCorrection adding e.g. pswThermistorSelect='T1'
- Failure of Temperature Drift Correction: Due to an update of the Temperature Drift Correction task in the pipeline, the pipeline may fail with an
Index argument 0 is out of range error if run with Calibration Tree spire_cal_6_0 . Please update to at least use spire_cal_6_1 to solve the problem (See the SPIRE Data Reduction Guide, Chapter 3).
| > > | <-- * Thermistor jumps: this should be automatically solved re-reducing your observation as of HIPE v.6. If this is not the case, you must exclude the affected thermistor when running the temperatureDriftCorrection adding e.g. pswThermistorSelect='T1'
-
- Failure of Temperature Drift Correction: Due to an update of the Temperature Drift Correction task in the pipeline, the pipeline may fail with an
Index argument 0 is out of range error if run with Calibration Tree spire_cal_6_0 . Please update to at least use spire_cal_6_1 to solve the problem (See the SPIRE Data Reduction Guide, Chapter 3). -->
| |
-
- Bad baseline removal (see also above) as of Hipe v. 6.x, a new polynomial fit (in comparison to the standard median) for baseline removal has been added as a prototype. Assuming that your Observation Context is stored in a variable named
obs , you can call it as e.g.:
| |
< < | | |
from herschel.spire.ia.pipeline.phot.baseline import BaselineRemovalPolynomialTask
baselineRemovalPolynomial = BaselineRemovalPolynomialTask() | | mapBaseline = naiveScanMapper(input=scansBaseline, array="PLW")
| |
< < | | > > | | |
Spectrometer data reduction | |
- Subtract the Dark Sky spectrum closest to your observation (use the "Background Subtraction" script in HIPE)
- Subtract the spectrum of surrounding detectors (use the "Background Subtraction" script in HIPE)
| |
< < |
- Substitute the standard teleRsrf calibration file for one derived specifically for the OD of your observation (in the User Pipeline Script in HIPE)
| > > | <-- 3. Substitute the standard teleRsrf calibration file for one derived specifically for the OD of your observation (in the User Pipeline Script in HIPE) --> | |
Dark Sky observations are observed on every SPIRE Spectrometer OD, and are all public in the Archive.
A listing of the available Dark Sky observations can be found here. | |
< < | In order to obtain the teleRsrf calibration file derived for the OD of your observation and valid for your HIPE/calibration tree version, please raise a Helpdesk ticket (select the "SPIRE FTS" department) specifying the observation that you are trying to process. | > > | <-- In order to obtain the teleRsrf calibration file derived for the OD of your observation and valid for your HIPE/calibration tree version, please raise a Helpdesk ticket (select the "SPIRE FTS" department) specifying the observation that you are trying to process. --> | |
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
SPIRE Launch Pad |
Data Launch Pad |
PDF |
version 1.5 |
SPIRE Launch Pad |
Photometer Launch Pad |
PDF |
version 1.6 |
SPIRE Launch Pad |
Spectrometer Launch Pad |
PDF |
version 1.6 |
| |
< < | | | > > | | |
Photometer data reduction | |
-
- This effect, related to data masked for various reasons and poor coverage (not enough redundancy), is more evident in single fast-scan Parallel Mode maps. To avoid NaNs, increase the pixel's dimension (i.e., decrease the map's resolution).
- This effect can also happen with destriped maps. In this case check if increasing the sigma or switching off the Level 2 deglitcher helps. Especially the HIPE 8 destriper should not be currently used with the Level 2 deglitcher active.
| |
> > |
- WCS in 3-colour images
- In all observation reduced with HIPE 8, the task
createRgbImage puts wrong WCS in the output. Instead of using the WCS provided by the WCS input parameter, this task uses the WCS of one of the input images. This has been fixed in HIPE 9
| |
- Quality flags in the quality context
- Currently, the quality flags at the quality context inside the observation context are just meant for HSC/ICC internal evaluation of the quality of the products and not for the users. In case the data had some serious quality problem, the PI of the program has been contacted about it. Otherwise, only information in the quality summary, when available, should concern the observers.
| | | |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.5" date="1328875003" name="SPIRE_PhotometerLaunchPad_v1.5.pdf" path="SPIRE_PhotometerLaunchPad_v1.5.pdf" size="207962" user="Main.ChrisPearson" version="2" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.6" date="1331743712" name="SPIRE_PhotometerLaunchPad_v1.6.pdf" path="SPIRE_PhotometerLaunchPad_v1.6.pdf" size="209303" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Spectrometer Launch Pad v1.6" date="1328388627" name="SPIRE_SpectrometerLaunchPad_v1.6.pdf" path="SPIRE_SpectrometerLaunchPad_v1.6.pdf" size="196595" user="Main.ChrisPearson" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1306492467" name="maskTimelines.py.txt" path="maskTimelines.py.txt" size="5945" user="Main.LucaConversi" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1312967015" name="bendoSourceFit_v0_9.py.txt" path="bendoSourceFit_v0_9.py.txt" size="26358" user="Main.IvanV" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE in-flight calibration" date="1295887708" name="aa14605-10.pdf" path="aa14605-10.pdf" size="270415" user="Main.IvanV" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304680043" name="Phot_Pipeline_Issue7.pdf" path="Phot_Pipeline_Issue7.pdf" size="464813" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Data Launch Pad v1.5" date="1328388567" name="SPIRE_DataLaunchPad_v1.5.pdf" path="SPIRE_DataLaunchPad_v1.5.pdf" size="208221" user="Main.ChrisPearson" version="1" |
| |
< < |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1304679998" name="Pipe_Description_2.1.pdf" path="Pipe_Description_2.1.pdf" size="2128829" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
| > > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.5" date="1328875003" name="SPIRE_PhotometerLaunchPad_v1.5.pdf" path="SPIRE_PhotometerLaunchPad_v1.5.pdf" size="207962" user="Main.ChrisPearson" version="2" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photometer Launch Pad v1.6" date="1331743712" name="SPIRE_PhotometerLaunchPad_v1.6.pdf" path="SPIRE_PhotometerLaunchPad_v1.6.pdf" size="209303" user="Main.ChrisPearson" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE Photo cookbook" date="1313054871" name="SPIREPhotometryCookbook_jul2011_2.pdf" path="SPIREPhotometryCookbook_jul2011_2.pdf" size="63443" user="Main.IvanV" version="1" |
| |
> > |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1305107081" name="beam_release_note_v1-1.pdf" path="beam_release_note_v1-1.pdf" size="4141606" user="Main.LucaConversi" version="1" |
META FILEATTACHMENT |
attr="" autoattached="1" comment="" date="1330422558" name="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" path="SPIRE-BSS-DOC-002966_SPIRE_Spectrometer_pipeline_description_Issue_4_0_1.pdf" size="812580" user="Main.EdwardPolehampton" version="1" |
| |
META FILEATTACHMENT |
attr="" autoattached="1" comment="SPIRE A&A paper, Griifin et al 2010" date="1295862676" name="aa14519-10.pdf" path="aa14519-10.pdf" size="1353253" user="Main.AnthonyMarston" version="1" |
|
|
META TOPICPARENT |
name="WebHome" |
SPIRE instrument and calibration web pages | |
Software and documentation | |
< < |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v8.1.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. FYI: this corresponds to the so-called CIB (continuous integration build) HIPE 8.0 build 3397.
| > > |
- HIPE (Herschel Interactive Processing Environment): The latest User Release HCSS version that you should use for reducing SPIRE data is HIPE v8.2.0. It can be downloaded from: http://herschel.esac.esa.int/HIPE_download.shtml. FYI: this corresponds to the so-called CIB (continuous integration build) HIPE 8.0 build 3459.
| |
- We also provide access to the latest stable developer build (a.k.a latest stable CIB), used by the instrument experts at the ICC.
- Beware _These developer builds do not undergo the same in-depth testing as the user releases do. The current latest stable developer build can be found here.
| |
< < |
- Within HIPE you can access all the SPIRE data reduction and HIPE-use documentation. For those who wish to read the SPIRE Data Reduction Guide (SDRG) in PDF form, we provide that here: SDRG version 2.0. This version can be used with HIPE v8.1.0 as well as all track 8 and track 9 of the CIBs. (Note that within the PDF version, document links will not work.) The SDRG follows the pipeline scripts (see "Cookbooks" below) and also explains what you are doing as you pipeline process.
| > > |
- Within HIPE you can access all the SPIRE data reduction and HIPE-use documentation. For those who wish to read the SPIRE Data Reduction Guide (SDRG) in PDF form, we provide that here: SDRG version 2.0. This version can be used with HIPE v8.2.0 as well as all track 8 and track 9 of the CIBs. (Note that within the PDF version, document links will not work.) The SDRG follows the pipeline scripts (see "Cookbooks" below) and also explains what you are doing as you pipeline process.
| | | & |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|