Changeset 1167 in Sophya for trunk/DocHFI_L2
- Timestamp:
- Aug 30, 2000, 11:50:47 PM (25 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/DocHFI_L2/wbsl2.tex
r1166 r1167 14 14 15 15 % Extension de symboles mathematiques 16 \usepackage{amssymb}16 % \usepackage{amssymb} 17 17 \usepackage{amsmath} 18 18 … … 27 27 \newcommand{\bbold}{\boldsymbol{b}} 28 28 \newcommand{\dbold}{\boldsymbol{d}} 29 %\newcommand{\bnu}{\nu}30 %\newcommand{\dbold}{d}31 %\newcommand{\bbold}{b}32 29 33 30 \begin{document} … … 50 47 } 51 48 52 \titlepfd{PL-HFI-LAL-PW-L200 1}{2.0}49 \titlepfd{PL-HFI-LAL-PW-L2002}{1.2} 53 50 54 51 \end{titlepage} … … 61 58 \item Version 1.1 (April 2000 - CVS version 1.2) \\ 62 59 Draft updated using the document prepared at ISCTM and IfA (Edinburgh) 63 \item Version 2.0 (August 2000 - CVS version 1.3) \\60 \item Version 1.2 (August 2000 - CVS version 1.4) \\ 64 61 Inclusion of a section describing notation and conventions, 65 62 flow charts. A more detailed description of deliverables is also included. … … 81 78 POSDAC will run the Level 2 data processing pipeline and have overall 82 79 responsibility for the collaborative work involved in its 83 design and implementation. LPAC will a major role for in the80 design and implementation. LPAC will a play major role for in the 84 81 activities that iterate and overlap between Level 2 85 82 and Level 3 (for which the Cambridge Planck Analysis Centre, 86 CPAC, plays the role analogous to POSDAC at Level 2) 83 CPAC, plays the role analogous to POSDAC at Level 2). 84 IPAC (at Caltech) and Canada (?) are the two other major 85 laboratories involved in the development of HFI level 2 86 software. 87 87 88 88 \section{HFI L2 processing software packages} … … 96 96 \item[]\gph{422} TOI processing 97 97 \item[]\gph{423} Polarised TOI processing 98 \item[]\gph{424} Basic2-D map reconstruction from TOI's99 \item[]\gph{425} Optimal 2-D map reconstruction100 \item[]\gph{426} Optimal 2-D polarised map reconstruction98 \item[]\gph{424} 2-D map reconstruction from TOI's 99 \item[]\gph{425} Polarised 2-D map reconstruction from TOI's 100 \item[]\gph{426} Optimal 2-D map reconstruction and analysis 101 101 \item[]\gph{427} Early Compact Source Catalogue 102 102 \item[]\gph{428} General software architecture and support modules … … 104 104 \end{itemize} 105 105 106 The package \gph 424should provide a resonably fast and simple106 The package \gph{424} should provide a resonably fast and simple 107 107 method for reconstructing 2-D maps from cleaned TOI's (from 108 \gph 422 and \gph423), removing systematic effects (destriping)108 \gph{422} and \gph{423}), removing systematic effects (destriping) 109 109 and deconvolving the antenna beam pattern. An iterative method 110 110 is foreseen, capable of dealing with partial knowledge of 111 instrument caracteristics. 112 The optimal 2-D map reconstruction packages (\gph425 and \gph426) 111 instrument caracteristics. \gph{425} would contain the 112 complementary functionalities needed for reconstructing 113 polarisation maps, using data from polarised channels. 114 The optimal 2-D map reconstruction packages (\gph{426}) 113 115 will implement the best feasible method for analysing the whole 114 116 data set from the HFI instrument and building the full sky frequency 115 117 maps. 118 119 \par 120 In addition to the specific Level 2 workpackages, the following items 121 are also related to the L2 data processing: 116 122 117 123 \begin{itemize} … … 135 141 \ngph{421} & 5 & \ngph{426} & ? \\ 136 142 % 137 \ngph{422} & 15 & \ngph{427} & 5\\143 \ngph{422} & 15 & \ngph{427} & 10 \\ 138 144 % 139 \ngph{423} & 1 5& \ngph{428} & 30 \\145 \ngph{423} & 10 & \ngph{428} & 30 \\ 140 146 % 141 \ngph{424} & 20& \ngph{429} & 10 \\147 \ngph{424} & 15 & \ngph{429} & 10 \\ 142 148 % 143 \ngph{425} & ?& & \\149 \ngph{425} & 10 & & \\ 144 150 % & & & \\ 145 151 % … … 148 154 \ngph{360} & 2 & \ngph{180} & 1 \\ 149 155 \hline \hline 150 \multicolumn{2}{c}{\bf Total} & \multicolumn{2}{c}{\bf 11 0+ ?} \\156 \multicolumn{2}{c}{\bf Total} & \multicolumn{2}{c}{\bf 115 + ?} \\ 151 157 \hline 152 158 \end{tabular} … … 166 172 \begin{itemize} 167 173 \item[] {\bf Coordinates:} The spacecraft attitude is defined by the spin 168 axis direction $SA (\theta, \phi)$. $\psi$ is the third angle defining 169 the position of the spacecraft and thus a given detectors view 170 direction and beam pattern orientation. 174 axis direction $\overrightarrow{\Omega}(\theta, \phi)$. 175 $\psi$ is the third angle defining the position of the spacecraft 176 and thus a given detectors view direction and beam pattern orientation. 177 The spin velocity would be denoted $\omega_z$ or $omega_{\psi}$. \\ 171 178 A given sky direction is denoted $(\alpha,\delta)$ in equatorial coordinates, 172 179 $(l,b)$ in Galactic coordinates or $(\lambda,\beta)$ in ecliptic coordinate. 180 173 181 \item[] {\bf Detector:} A given HFI bolometer read-out channel. The corresponding 174 signal is denoted $\dbold(t)$ or $\bbold(t)$ $\dbold^j(t)$ or $\bbold^j(t)$ where $j$ is the 175 bolometer number. 182 signal is denoted $\dbold(t)$ or $\bbold(t)$ $\dbold^j(t)$ or $\bbold^j(t)$ 183 where $j$ is the bolometer number. 184 176 185 \item[] {\bf Frequency channel:} The set of detectors working in the 177 186 same frequency range. This information is only obtained by combining 178 187 information from several detectors in the corresponding frequency band. 179 The subscript $\bnu$ is used to denote a frequency channel. The sky map 180 in a given frequency band would be written as $Sky (\theta,\phi) \vert ^{\bnu}$. 181 \item[] {\bf Scan:} The time interval corresponding to a nominal spin axis 182 direction 183 184 \end{itemize} 188 The subscript $\bnu$ is used to denote a frequency channel. 189 190 \item[] {\bf Scan:} The time interval corresponding to a given nominal 191 spin axis direction 192 193 \item[] {\bf Sky map:} The reconstructed signal in a given pixelisation 194 scheme from a single or a set of detectors. The sky map in a given 195 frequency channel is denoted $sky(\theta,\phi) \vert ^{\bnu}$. 196 \end{itemize} 197 185 198 186 199 \subsection{Processing steps} 200 201 Unpacking the telemetry packets, uncompressing the science data, 202 time ordering the data and archiving the data in a format usable 203 by the L2 pipeline is the responsability of Level 1. Detailed 204 description of L1 software and processing steps is beyond the scope 205 of this document. {\bf DS0} denotes the complete data set used 206 as input by level 1. {\bf DS0} contains the instrument 207 science and House-keeping (HSK) data telemetry packets, as well 208 as the auxiliary data (orbit and attitude). 209 {\bf DS1} is the processed data from level 1 containing the TOI's 210 (Time Ordered Information). 211 $$ \boldmath{L1} : \text{DS0} \longrightarrow \text{DS1} $$ 212 213 DS1 data set : 214 \begin{itemize} 215 \item Raw Time Ordered bolometer signals : $b_{raw}^j(t)$ 216 \item Time Ordered House-keeping data : $HSK(t)$ 217 \item Associated orbit and attitude data : 218 $XYZ(t) , \overrightarrow{\Omega}(t) , \psi(t)$ 219 (spin axis direction $(\theta, \phi)(t)$ 220 \end{itemize} 221 222 {\bf DS0:} Science and House-keeping (HSK) telemetry packets \\ 223 {\bf DS1:} Time ordered - Uncompressed Science data bundeled 224 with the corresponding house-keeping data. \\ 225 {\bf DS2-2} Cleaned, photometrically calibrated Time ordered data \\ 187 226 188 227
Note:
See TracChangeset
for help on using the changeset viewer.