Difference between revisions of "The HFI DPC"

From Planck Legacy Archive Wiki
Jump to: navigation, search
m
m
 
(57 intermediate revisions by 7 users not shown)
Line 1: Line 1:
The HFI DPC has been organized into different "Levels": 1, 2, 3, 4 and "S". In brief, during operations, L1 feeds the database resulting in time-ordered information (TOI) objects. L2 is the core of the processing, which turns TOIs into clean calibrated sky maps. L3 transforms these maps at specific frequencies into more scientific products, like catalogues, maps and spectra of astrophysical components. L3 can rely on simulation provided by the LS, while L4 refers to delivering the DPC products to ESA.  This processing relies on dedicated software and hardware infrastructures developed pre-launch.
+
The first stage of HFI data processing is performed on-board in order to generate the telemetry, as described in the [[HFI_detection_chain#Data_compression | Data compression]] section. On the ground, the HFI DPC has been organized into different "Levels": 1, 2, 3, 4, and "S". In brief, during operations, L1 feeds the data base, resulting in time-ordered information (TOI) objects. L2 is the core of the processing, which turns TOIs into clean calibrated sky maps. L3 transforms these maps at specific frequencies into more scientific products, like catalogues, maps, and spectra of astrophysical components. L3 can rely on simulation provided by the LS, while L4 refers to delivering the DPC products to ESA.  This processing relies on dedicated software and hardware infrastructures developed pre-launch.
  
 +
The data processing applied for the ''"Early Planck results"'' series of publications was described in {{PlanckPapers|planck2011-1-7}}. The {{PlanckPapers|planck2013-p03}} and its companion papers provide the reference for the processing done for the 2013 data release.
  
 +
<span style="font-size:150%">'''Level 1: building the reference data base during flight operations''' </span>
  
== Level 1: building the reference database during operations ==
+
(L1): consists in receiving the telemetry and ancillary data files and ingesting them into the DPC data base.  This involves decompressing, in some cases changing data formats, computing the time of individual data samples from the time of the compression slices, but otherwise no processing proper. Other steps are:
 +
* science, housekeeping, and ancillary data ingestion;
 +
* timing and pointing interpolation.
 +
This is further described in the [[Pre-processing]] section.
  
(L1): consists in receiving the telemetry and ancillary data files and ingesting them into the DPC database.  This involves decompressing, in some cases changing data formats, computing the time of individual data samples from the time of the compression slices, but otherwise no processing proper. Other steps are:
+
<span style="font-size:150%">'''Level 2: converting temporal information into clean calibrated maps'''</span>
* data ingestion (science, HK, ancillary, other?)
 
* construction of ToS in science data group
 
* pointing interpolation
 
* construction of other TOI and ROI objects from AHF, ...
 
  
This is further described in the [[Pre-processing]] section
+
(L2): this is where the data are processed from timelines into maps. The main processing steps are:
 +
* timeline (or Time-Ordered Information = TOI) processing, which includes conversion from ADUs to engineering units (volts), demodulation, deglitching, conversion from engineering to physical units (watts), removal of known systematic effects (non-linearities, 4-K lines, jumps, ring flagging), removal of the instrumental signature (time transfer function), and temporal noise estimation (see section [[TOI_processing]]);
 +
* pointing and beam construction of each detector (see sections [[Detector pointing]] and [[Beams]]);
 +
* mapmaking and photometric calibration, projecting the TOIs onto all-sky maps, etc (see section [[Map-making]]);
 +
* characterization/validation through angular power spectra (see section [[PowerSpectra]]);
 +
* overal HFI data validation, through difference tests, comparison to detailed simulations, etc. (see section [[HFI-Validation]]).
  
== Level 2: converting temporal information into maps ==
+
The resulting data characteristics are given in the [[Summary]] section.
  
(L2): this is where the data are processed from timelines into maps. The main processing steps are
+
<span style="font-size:150%">'''Level 3: basic analyses of (Level 2) sky temperature maps'''</span>
* Timeline (or Time-Ordered Information = TOI) processing, which includes conversion from ADUs to engineering units (Volts), demodulation, deglitching, conversion from engineering to physical units (Watts), removal of known systematic effects (non-linearities, 4K lines, Jumps, ring flagging), removal of the instrumental signature (time transfer function), temporal noise Estimation. Details [[TOI_processing| here]].
 
* Pointing and beam of each detector. See section [[Pointing%26Beams]].
 
* map-making & photomoetric calibration: projecting the TOIs onto all-sky maps, etc. See section [[Map-making]].
 
* Characterisation/validation through angular power spectra. See section [[PowerSpectra]].
 
* Overal HFI data validation, through difference tests, comparison to detailed simulations, etc., See section [[HFI-Validation]]
 
* The resulting data characteristics are given in section [[Summary]]
 
  
== Level 3: Frequency maps basic analyses ==
+
(L3): This is where the data in the form of frequency maps are converted to catalogues and full-sky astrophysical component maps. Much of this is done in common with the LFI DPC and is further described in the [[HFI/LFI joint data processing | HFI/LFI common sections]].
  
(L3): This is where the data in the form of frequency maps are converted to catalogues and astrophysical component maps. Much of this is done in common with the LFI, and is further described in the [[HL | HFI/LFI common sections ]]
+
<span style="font-size:150%">'''Level S : a common HFI/LFI simulation software'''</span>
  
== Level 4 : Delivering results ==
+
Level S is the so-called "Simulation Level"  software suite, common to both consortia, which, given a sky model (generated by the Planck sky model, <tt>PSM</tt>), detectors pointing and beams, generates the power falling on each detector. It can also provide a simplified description of the noise. It is further described in the HFI/LFI [[HFI/LFI joint data processing| common section]]. HFI specific developments (configuration control and MC bench, specific effects like 4-K lines, glitches, ADC nonlinearity, etc.) are described in [[HFI-Validation | the HFI data validation section]].
  
Level 4 is the "Archive Level". No processing done, but rather exporting, reformating, documenting.
+
<span style="font-size:150%">'''HFI DPC Infrastructures'''</span>
  
== Level S : A common simulation software ==
+
The HFI Data Processing Centre can be thought of as a centralized backbone, providing hardware and software infrastructure to a relatively large number of geographically distributed groups of developers and other research groups in the HFI and LFI core teams. An overview was given in {{PlanckPapers|planck2011-1-7}}.  Particular tasks include:
 +
* code and configuration management;
 +
* data management;
 +
* instrument model (IMO) data base;
 +
* data flow management;
 +
* hardware.
  
Level S is the so-called "Simulation Level", common to both instruments, and further described in the HFI/LFI [[ HL | common section]]. HFI specific developments are described in [[HFI-Validation | the HFI data validation section]].
+
== References ==
 +
<References />
 +
  
== HFI DPC Infrastructures==
 
  
The HFI Data Processing Centre can be thought of as a centralized
+
[[Image:HFI_logo_H.png]]
backbone providing hardware and software infrastructures
 
to a relatively large number of geographically distributed groups
 
of developers and other R&D groups in the HFI and LFI core teams
 
  
Further details were given in the HFI data processing paper of Planck early results series.
 
In particular:
 
* Code and configuration management can be found at {{PEarly|6|page=34}}.
 
* Data management at {{PEarly|6|page=34}}.
 
* Instrument model (IMO) database at {{PEarly|6|page=35}}.
 
* Data flow management at {{PEarly|6|page=35}}.
 
* Hardware at {{PEarly|6|page=36}}.
 
 
[[Image:HFI@IAP.png | HFI reference platform in the IAP basement]]
 
 
 
[[Image:HFI_logo_H.png]]
 
  
[[Category:Data processing]]
+
[[Category:HFI data processing|000]]

Latest revision as of 01:28, 23 May 2015

The first stage of HFI data processing is performed on-board in order to generate the telemetry, as described in the Data compression section. On the ground, the HFI DPC has been organized into different "Levels": 1, 2, 3, 4, and "S". In brief, during operations, L1 feeds the data base, resulting in time-ordered information (TOI) objects. L2 is the core of the processing, which turns TOIs into clean calibrated sky maps. L3 transforms these maps at specific frequencies into more scientific products, like catalogues, maps, and spectra of astrophysical components. L3 can rely on simulation provided by the LS, while L4 refers to delivering the DPC products to ESA. This processing relies on dedicated software and hardware infrastructures developed pre-launch.

The data processing applied for the "Early Planck results" series of publications was described in Planck-Early-VI[1]. The Planck-2013-VI[2] and its companion papers provide the reference for the processing done for the 2013 data release.

Level 1: building the reference data base during flight operations

(L1): consists in receiving the telemetry and ancillary data files and ingesting them into the DPC data base. This involves decompressing, in some cases changing data formats, computing the time of individual data samples from the time of the compression slices, but otherwise no processing proper. Other steps are:

  • science, housekeeping, and ancillary data ingestion;
  • timing and pointing interpolation.

This is further described in the Pre-processing section.

Level 2: converting temporal information into clean calibrated maps

(L2): this is where the data are processed from timelines into maps. The main processing steps are:

  • timeline (or Time-Ordered Information = TOI) processing, which includes conversion from ADUs to engineering units (volts), demodulation, deglitching, conversion from engineering to physical units (watts), removal of known systematic effects (non-linearities, 4-K lines, jumps, ring flagging), removal of the instrumental signature (time transfer function), and temporal noise estimation (see section TOI_processing);
  • pointing and beam construction of each detector (see sections Detector pointing and Beams);
  • mapmaking and photometric calibration, projecting the TOIs onto all-sky maps, etc (see section Map-making);
  • characterization/validation through angular power spectra (see section PowerSpectra);
  • overal HFI data validation, through difference tests, comparison to detailed simulations, etc. (see section HFI-Validation).

The resulting data characteristics are given in the Summary section.

Level 3: basic analyses of (Level 2) sky temperature maps

(L3): This is where the data in the form of frequency maps are converted to catalogues and full-sky astrophysical component maps. Much of this is done in common with the LFI DPC and is further described in the HFI/LFI common sections.

Level S : a common HFI/LFI simulation software

Level S is the so-called "Simulation Level" software suite, common to both consortia, which, given a sky model (generated by the Planck sky model, PSM), detectors pointing and beams, generates the power falling on each detector. It can also provide a simplified description of the noise. It is further described in the HFI/LFI common section. HFI specific developments (configuration control and MC bench, specific effects like 4-K lines, glitches, ADC nonlinearity, etc.) are described in the HFI data validation section.

HFI DPC Infrastructures

The HFI Data Processing Centre can be thought of as a centralized backbone, providing hardware and software infrastructure to a relatively large number of geographically distributed groups of developers and other research groups in the HFI and LFI core teams. An overview was given in Planck-Early-VI[1]. Particular tasks include:

  • code and configuration management;
  • data management;
  • instrument model (IMO) data base;
  • data flow management;
  • hardware.

References[edit]


HFI logo H.png

(Planck) High Frequency Instrument

Data Processing Center

European Space Agency

(Planck) Low Frequency Instrument

Planck Sky Model

analog to digital converter