DatesObs

From Planck PLA 2015 Wiki
Jump to: navigation, search

Overview

The DatesObs files are not official Planck products but have been made available for the convenience of the community. They contain timing information split by survey, gridded by HEALPIX pixel, and sampled by UTCUniversal Time Coordinate(d) day. They are intended for investigation of inter-survey source variability, comparison with external observations, and understanding of the survey strategy.

File Format

There are 54 files; 6 HFI(Planck) High Frequency Instrument bands x 5 surveys & 3 LFI(Planck) Low Frequency Instrument bands x 8 surveys. They are named:

HFI(Planck) High Frequency Instrument_DatesObs_fff_Nside_R2.nn_survey_k.fits.gz

where fff is the usual 3-digit description of the channel frequency.

The files themselves are in FITSFlexible Image Transfer Specification format, and gzipped, with data in the first extension

  • RING-ordered HEALPIX
  • NSIDE 1024 for LFI(Planck) Low Frequency Instrument, and 2048 for HFI(Planck) High Frequency Instrument

They contain two fields:

  • DATESOBS - string - comma-separated list of UTCUniversal Time Coordinate(d) days in YYMMDD format on which the pixel was observed
  • NUMOBS - integer - the number of UTCUniversal Time Coordinate(d) days on which the pixel was observed

Unobserved pixels have been left blank.

Generation

The DATESOBS files were generated by projecting the line-of-sight of each detector onto the sky on a ring-by-ring basis. Inputs were the satellite spin-axis and the opening angle of each detector. Position is thus accurate to nearest pixel center and timing to the start of each ring - rings over midnight are only counted for the day in which they begin.

Note no beam information was used, just closest line-of-sight. The list of dates within a beam width is thus the union of the date information for all pixels within the appropriate area.

Pixels were counted observed if hit by a single detector within each instrument band; there was no consideration of intra-band coverage.

Detectors not used in production of the frequency maps were excluded.

Finally the data have been masked by the per-survey SkyMap hit-maps in order to remove areas which were flagged during the processing (mainly planet crossings). No ring cuts were applied so some anomalous rings are included.

Healpix IDL read_fits_map

Note the datesobs files cannot be read by Healpix's IDL read_fits_map routine as it is not expecting string content. There is no problem with the standard AstroLib mrdfits.

Full-sky map of the number of observations in the first survey.