The RIMO

Overview

---

The RIMO, or Reduced Instrument Model is a FITS file containing selected instrument characteristics that are needed by users who work with the released data products. It is described in detail in The HFI and LFI RIMO ICD (ref). There will be two RIMOs, one for each instrument, which will follow the same overall structure, but will differ in the details. The type of data in the RIMO can be:

Parameter 

namely scalars to give properties such as a noise level or a representative beam FWHM

Table 

to give, e.g., filter transmission profiles or noise power spectra

Image 

namely 2-D "flat" array, to give, e.g., the beam correlation matrices

The FITS file begins with primary header that contains some keywords that mainly for internal use and no data. The different types of data are written into different BINTABLE (for parameters and tables) or IMAGE (for 2-D arrays) extensions, as described below.

Map-level parameter data

---

The map-level data table contains the effective beam solid angle (total and out to different multiples of the beamFWHM) and noise information. It is written into a BINTABLE extension named MAP_PARAMS whose structure is as follows:

FREQUENCY (String) 

a 3-digit string giving the reference frequency in GHz, i.e., of the form 044 or 217

OMEGA_F, OMEGA_F_ERR (Real*4) 

the full beam solid angle and its uncertainty, in armin²

OMEGA_1, OMEGA_1_DISP (Real*4) 

the beam solid angle out to 1FWHM, and its dispersion, in arcmin²

OMEGA_2, OMEGA_2_DISP (Real*4) 

the beam solid angle out to 2FWHM, and its dispersion, in arcmin^2</sum>

FWHM (Real*4) 

FWHM of a Gaussian beam having the same (total) solid angle, in armin². This is the best value for source flux determination

FWHMGAUS (Real*4) 

FWHM derived from best Gaussian fit to beam maps, in armin². This is the best value for source identification

NOISE (Real*4) 

This is the typical noise/valid observation sample as derived from the high-l spectra of the half-ring maps, in the units of the corresponding map

For the Omega columns, the 'DISP' (for dispersion) column gives an estimate of the spatial variation as a function of position on the sky. This is the variation induced by combining the scanning beam determined from the planet observations with the scanning strategy, as described in Detectors pointing & beam.

Effective band transmission profiles

---

The effective filter bandpasses are given in different BINTABLE extensions. The extension is named BANDPASS_{name}, where name specified the frequency channel. In the case of the maps, the bandpasses are a weighted average of the bandpasses of the detectors that are used to build the map. For details see #planck2013-p03d. The bandpasses are given as 4-column tables containing:

WAVENUMBER (Real*4) 

the wavenumber in cm-1, conversion to GHz is accomplished by multiplying by [math]10^{-7}c[/math] [mks].

TRANSMISSION (Real*4) 

the transmission (normalized to 1 at the max for HFI and to have an integral of 1 for LFI)

ERROR (Real*4) 

the statistical [math]1-\sigma[/math] uncertainty for the transmission profile (not provided for LFI).

FLAG (Integer) 

a flag indicating if the data point is an independent frequency data point (nominally the case), or an FTS instrument line shape (ILS)-interpolated data point. The frequency data has been over-sampled by a factor of ~10 to assist in CO component separation efforts #planck2013-p03a, #planck2013-p03d.

The number of rows will differ among the different extensions, but are the same, by construction, within each extension.

Beam Window Functions

---

Beam window functions and associated error descriptions are written into a BINTABLE for each detection unit, where detection unit consists of an auto or a cross product of one or two frequency maps or detset maps used in the likelihood. Here they are:

• the 6 HFI frequency channels, producing 21 extensions
  • 100, 143, 217, 353, 545, 857
• 26 detsets, producing 351 extensions; the detsets used are, by frequency channel:
  • 100-DS1, 100-DS2,
  • 143-DS1, 143-DS2, 143-5, 143-6, 143-7,
  • 217-DS1, 217-DS2, 217-1, 217-2, 217-3, 217-4,
  • 353-DS1, 353-DS2, 353-1, 353-2, 353-7, 353-8,
  • 545-1, 545-2, 545-4,
  • 857-1, 857-2, 857-3, 857-4

and the extension names are of the form BEAMWF_U1XU2 where U1 and U2 are one (possibly the same) detection unit from one of the main groups above (i.e. there are no cross products between detsets and frequency channels, or between HFI and LFI). Each extension contains the columns:

NOMINAL (Real*4) 

the beam window function proper,

EIGEN_n (Real*4, n=1-5) 

the five the error modes.

and the following keywords

NMODES (Integer) 

the number of EIGEN_* modes,

LMIN and LMAX (Integer) 

the length of NOMINAL vector

LMIN_EM and LMAX_EM (Integer) 

that give the range of the valid samples of the EIGEN_* vectors. Here LMAX_EM is always less than or equal to LMAX, and the values between LMAX_EM+1 and LMAX is set to NaN

CORRMAT (string) 

the name of the extension containing the corresponding beam correlation matrix

Beam Correlation Matrix

---

Two beam correlation matrices are given, in two IMAGE extensions:

CORRBEAM_FREQ (Real*8) 

for the frequency channels (21 units), 105x015 pixel matrix,

CORRBEAM_DSET (Reak*8) 

for the detsets (351 units), 1755x1755 pixel matrix

Each is a symmetric matrix with 1-valued diagonal, made of NBEAMS*NBEAMS blocks, each block being NMODES*NMODES in size. The nth row- (and column-) block entry relates to the B(l) model whose name is indicated in ROWn = BEAMWF_U1XU2 keywords, and the corresponding eigenmodes are stored in a HDU of the same name.

Each extension contains also the following keywords:

NDETS (Integer) 

the number of detector units

NBEAMS (Integer) 

the number of beams = NSETS * (NSETS+1) / 2

NMODES (Integer) 

here 5

L_PLUS (Integer) 

Eigenmode > 0 to break degeneracies

and some other ones for internal data checking and traceability