Difference between revisions of "Survey history"

From Planck Legacy Archive Wiki
Jump to: navigation, search
Line 1: Line 1:
<span style="color:Red">NOTE: Text in red to be removed when filling the contents</span>
==Product description==
<span style="color:Red">A general description of the product, including e.g. figures related to the contents (e.g. maps, tables), and some explanation of its scientific meaning. If there are scientific warnings about the use of the product (User’s caveats), they should also be given here, or at least references to other explanatory documents (papers etc).</span>
==Production process==
<span style="color:Red">Description of the Pipeline used to generate the product. In particular any limitations and approximations used in the data processing should be listed. Avoiding detailed descriptions of methods and referring to other parts of the ES and/or the relevant Planck papers for the details. References however should be quite detailed (i.e. it is not enough to direct the user to a paper, but the relevant section in the paper should be provided).</span>
<span style="color:Red">A list (and brief description to the extent possible) of the input data used to generate this product (down to file names), as well as any external ancillary data sets which were used.</span>
==Related products==
<span style="color:Red">A description of other products that are related and share some commonalities with the product being described here. E.g. if the description is of a generic product (e.g. frequency maps), all the products falling into that type should be listed and referenced.</span>
<span style="color:Red">A detailed description of the data format of each file, including header keywords for fits files, extension names, column names, formats….</span>
===File names===
===Numerical Format===
===Pre-Programmed Pointing Lists===
===Pre-Programmed Pointing Lists===

Revision as of 13:22, 13 March 2013

Pre-Programmed Pointing Lists[edit]

The Pre-Programmed Pointing Lists (PPL) are made by Planck Science Office from the Baseline Scanning Strategy with the help of the Software Planning and Performance Tool. They are sent to MOC/FD for use in making the Augmented Pre-Programmed Pointing Lists (APPL) used for commanding the spacecraft attitude.

The PPL file name is the following: YYYYMMDD_yyyymmdd_NNNN_X.PPL

with YYYYMMDD = start date of the valid span of the PPL file

yyyymmdd = end date of the valid span of the PPL file

NNNN = unique sequence number, in the range 0000 ≤ NNNN ≤ 9999, incrementing sequentially throughout the mission and uniquely identifying each new PPL file that is generated (i.e. no repeated numbers and no gaps in the sequence of PPLs) o 0000-8999 reserved for PSO o 9000-9999 reserved for attitude manoeuvres generated by MOC

X = type of PPL, as follows: o R = Routine (standard 4-week PPL) o C = Contingency (3-day replanning) o L = Long-Term PPL (LTPPL) o S = Special

PPLs contain the following information in ASCII columns:

  • pointing reference number
  • Ecliptic longitude
  • Ecliptic latitude
  • nominal start time for pointing
  • earliest allowed start time
  • latest allowed start time
  • nominal dwell time
  • observation type
  • comments

PPLs can be found in the Planck Legacy Archive in the "Time-Ordered Information: Operational Files" section, ordered normally by periods of a month.

Detailed information about the PPL's can be found here: PPL ICD

Augmented Pre-Programmed Pointing Lists[edit]

APPLs are made by MOC / Flight Dynamics using pointing information (PPLs) from the Planck Science Office.

The APPLs incorporate information about the Operational Days boundaries in order to fit pointings into each OD.

APPLs are grouped ans summarized by MOC to form files called the APPL Summary Files or APS. These are delivered in the Planck Legacy Archive in the "Time-Ordered Information: Operational Files" section, by Operational Day.

Detailed information about the APPL's can be found here: APPL Interface Control Document

Attitude History Files[edit]

The pointing history of Planck is described in the Attitude History Files (AHF) sequence. All the AHF can be found in the Planck Legacy Archive, for three different methods of computation (AHF, DHF, GHF).

The GHF are made using refined pointing information from the Fiber Optics Gyroscope.

Available information concerning the AHF can be found here: AHF Interface Control Document

Focal plane geometry[edit]

The Spacecraft-Instrument Alignment Matrix (SIAM) contains all the geometry information for each detector of both instruments with respect to the main optical frame.

The last updated SIAM is provided in the Planck Legacy Archive in the "Time-Ordered Information: Operational Files" section.

Information about the structure of the SIAM can be found here: SIAM ICD

Orbit file[edit]

The orbit file is produced by the Flight Dynamics team at ESOC and contains the information of the Planck orbital history throughout the whole mission (since launch).

Planck operational state history[edit]

The Planck Operational State History (POSH) provides an easily accessible summary of the status of the Planck spacecraft, throughout the course of its mission. It should be useful to scientists as a complement to the data they are analyzing.

Due to the type and quantity of data that describes the state of a satellite and its instruments, it is common for it to be spread over a large number of files and formats which may have to be retrieved from a large number of systems. In addition there are a significant number of potentially interesting occurrences during the mission which are not found in any one single repository; examples are mission milestones, definitions of operational days and anomalous events. The initial motivation for the creation of the POSH was to provide the state of the spacecraft and its instruments in an easily accessible way at any given time. States to be included were the operational phases and the operational status/mode of each of the major payload components. The intention being that this information could be used to assist not only in the operational work in monitoring the status of the survey but also as a data source that could be consulted whilst analyzing science data.

Two main record types are stored in the POSH:

EVENTS, consisting of occurrences during the mission that can be described by a start and end time (e.g. survey boundaries, anomalies, ODs, manoeuvres). The definition of an event is provided for operational purposes; it may or may not agree with the definition of an event for data analysis purposes (e.g. the boundaries of a survey may be defined in a different way in the pipeline).

HOUSE KEEPING (HK) SUMMARY which consists of some HK timelines with one data point per pointing period (e.g. temperatures, position in the sky, drift rates, sun angles). This data set contains a very compact operational summary of the mission (not an exhaustive list of HK).

Pre-programmed Pointing List

[ESA's] Mission Operation Center [Darmstadt, Germany]

Augmented Preprogrammed Pointing List

Planck Science Office

Operation Day definition is geometric visibility driven as it runs from the start of a DTCP (satellite Acquisition Of Signal) to the start of the next DTCP. Given the different ground stations and spacecraft will takes which station for how long, the OD duration varies but it is basically once a day.

Attitude History File

Spacecraft Instrument Alignment Matrix

European Space Operations Centre (Darmstadt)

House Keeping