comparison: docs/_build/latex/SingleCalculusChain.tex
docs/_build/latex/SingleCalculusChain.tex
- changeset 14
- c675d086f7d2
- parent 13
- 52af8fbed3d7
- child 15
- f51ca1e515ac
equal
deleted
inserted
replaced
| 13:52af8fbed3d7 | 14:c675d086f7d2 |
|---|---|
| 1 % Generated by Sphinx. | |
| 2 \def\sphinxdocclass{report} | |
| 3 \documentclass[letterpaper,10pt,english]{sphinxmanual} | |
| 4 \usepackage[utf8]{inputenc} | |
| 5 \DeclareUnicodeCharacter{00A0}{\nobreakspace} | |
| 6 \usepackage[T1]{fontenc} | |
| 7 \usepackage{babel} | |
| 8 \usepackage{times} | |
| 9 \usepackage[Bjarne]{fncychap} | |
| 10 \usepackage{longtable} | |
| 11 \usepackage{sphinx} | |
| 12 \usepackage{multirow} | |
| 13 | |
| 14 | |
| 15 \title{Single Calculus Chain Documentation} | |
| 16 \date{March 30, 2012} | |
| 17 \release{0.2} | |
| 18 \author{SCC team} | |
| 19 \newcommand{\sphinxlogo}{} | |
| 20 \renewcommand{\releasename}{Release} | |
| 21 \makeindex | |
| 22 | |
| 23 \makeatletter | |
| 24 \def\PYG@reset{\let\PYG@it=\relax \let\PYG@bf=\relax% | |
| 25 \let\PYG@ul=\relax \let\PYG@tc=\relax% | |
| 26 \let\PYG@bc=\relax \let\PYG@ff=\relax} | |
| 27 \def\PYG@tok#1{\csname PYG@tok@#1\endcsname} | |
| 28 \def\PYG@toks#1+{\ifx\relax#1\empty\else% | |
| 29 \PYG@tok{#1}\expandafter\PYG@toks\fi} | |
| 30 \def\PYG@do#1{\PYG@bc{\PYG@tc{\PYG@ul{% | |
| 31 \PYG@it{\PYG@bf{\PYG@ff{#1}}}}}}} | |
| 32 \def\PYG#1#2{\PYG@reset\PYG@toks#1+\relax+\PYG@do{#2}} | |
| 33 | |
| 34 \def\PYG@tok@gd{\def\PYG@tc##1{\textcolor[rgb]{0.63,0.00,0.00}{##1}}} | |
| 35 \def\PYG@tok@gu{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.50,0.00,0.50}{##1}}} | |
| 36 \def\PYG@tok@gt{\def\PYG@tc##1{\textcolor[rgb]{0.00,0.25,0.82}{##1}}} | |
| 37 \def\PYG@tok@gs{\let\PYG@bf=\textbf} | |
| 38 \def\PYG@tok@gr{\def\PYG@tc##1{\textcolor[rgb]{1.00,0.00,0.00}{##1}}} | |
| 39 \def\PYG@tok@cm{\let\PYG@it=\textit\def\PYG@tc##1{\textcolor[rgb]{0.25,0.50,0.56}{##1}}} | |
| 40 \def\PYG@tok@vg{\def\PYG@tc##1{\textcolor[rgb]{0.73,0.38,0.84}{##1}}} | |
| 41 \def\PYG@tok@m{\def\PYG@tc##1{\textcolor[rgb]{0.13,0.50,0.31}{##1}}} | |
| 42 \def\PYG@tok@mh{\def\PYG@tc##1{\textcolor[rgb]{0.13,0.50,0.31}{##1}}} | |
| 43 \def\PYG@tok@cs{\def\PYG@tc##1{\textcolor[rgb]{0.25,0.50,0.56}{##1}}\def\PYG@bc##1{\colorbox[rgb]{1.00,0.94,0.94}{##1}}} | |
| 44 \def\PYG@tok@ge{\let\PYG@it=\textit} | |
| 45 \def\PYG@tok@vc{\def\PYG@tc##1{\textcolor[rgb]{0.73,0.38,0.84}{##1}}} | |
| 46 \def\PYG@tok@il{\def\PYG@tc##1{\textcolor[rgb]{0.13,0.50,0.31}{##1}}} | |
| 47 \def\PYG@tok@go{\def\PYG@tc##1{\textcolor[rgb]{0.19,0.19,0.19}{##1}}} | |
| 48 \def\PYG@tok@cp{\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 49 \def\PYG@tok@gi{\def\PYG@tc##1{\textcolor[rgb]{0.00,0.63,0.00}{##1}}} | |
| 50 \def\PYG@tok@gh{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.00,0.00,0.50}{##1}}} | |
| 51 \def\PYG@tok@ni{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.84,0.33,0.22}{##1}}} | |
| 52 \def\PYG@tok@nl{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.00,0.13,0.44}{##1}}} | |
| 53 \def\PYG@tok@nn{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.05,0.52,0.71}{##1}}} | |
| 54 \def\PYG@tok@no{\def\PYG@tc##1{\textcolor[rgb]{0.38,0.68,0.84}{##1}}} | |
| 55 \def\PYG@tok@na{\def\PYG@tc##1{\textcolor[rgb]{0.25,0.44,0.63}{##1}}} | |
| 56 \def\PYG@tok@nb{\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 57 \def\PYG@tok@nc{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.05,0.52,0.71}{##1}}} | |
| 58 \def\PYG@tok@nd{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.33,0.33,0.33}{##1}}} | |
| 59 \def\PYG@tok@ne{\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 60 \def\PYG@tok@nf{\def\PYG@tc##1{\textcolor[rgb]{0.02,0.16,0.49}{##1}}} | |
| 61 \def\PYG@tok@si{\let\PYG@it=\textit\def\PYG@tc##1{\textcolor[rgb]{0.44,0.63,0.82}{##1}}} | |
| 62 \def\PYG@tok@s2{\def\PYG@tc##1{\textcolor[rgb]{0.25,0.44,0.63}{##1}}} | |
| 63 \def\PYG@tok@vi{\def\PYG@tc##1{\textcolor[rgb]{0.73,0.38,0.84}{##1}}} | |
| 64 \def\PYG@tok@nt{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.02,0.16,0.45}{##1}}} | |
| 65 \def\PYG@tok@nv{\def\PYG@tc##1{\textcolor[rgb]{0.73,0.38,0.84}{##1}}} | |
| 66 \def\PYG@tok@s1{\def\PYG@tc##1{\textcolor[rgb]{0.25,0.44,0.63}{##1}}} | |
| 67 \def\PYG@tok@gp{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.78,0.36,0.04}{##1}}} | |
| 68 \def\PYG@tok@sh{\def\PYG@tc##1{\textcolor[rgb]{0.25,0.44,0.63}{##1}}} | |
| 69 \def\PYG@tok@ow{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 70 \def\PYG@tok@sx{\def\PYG@tc##1{\textcolor[rgb]{0.78,0.36,0.04}{##1}}} | |
| 71 \def\PYG@tok@bp{\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 72 \def\PYG@tok@c1{\let\PYG@it=\textit\def\PYG@tc##1{\textcolor[rgb]{0.25,0.50,0.56}{##1}}} | |
| 73 \def\PYG@tok@kc{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 74 \def\PYG@tok@c{\let\PYG@it=\textit\def\PYG@tc##1{\textcolor[rgb]{0.25,0.50,0.56}{##1}}} | |
| 75 \def\PYG@tok@mf{\def\PYG@tc##1{\textcolor[rgb]{0.13,0.50,0.31}{##1}}} | |
| 76 \def\PYG@tok@err{\def\PYG@bc##1{\fcolorbox[rgb]{1.00,0.00,0.00}{1,1,1}{##1}}} | |
| 77 \def\PYG@tok@kd{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 78 \def\PYG@tok@ss{\def\PYG@tc##1{\textcolor[rgb]{0.32,0.47,0.09}{##1}}} | |
| 79 \def\PYG@tok@sr{\def\PYG@tc##1{\textcolor[rgb]{0.14,0.33,0.53}{##1}}} | |
| 80 \def\PYG@tok@mo{\def\PYG@tc##1{\textcolor[rgb]{0.13,0.50,0.31}{##1}}} | |
| 81 \def\PYG@tok@mi{\def\PYG@tc##1{\textcolor[rgb]{0.13,0.50,0.31}{##1}}} | |
| 82 \def\PYG@tok@kn{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 83 \def\PYG@tok@o{\def\PYG@tc##1{\textcolor[rgb]{0.40,0.40,0.40}{##1}}} | |
| 84 \def\PYG@tok@kr{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 85 \def\PYG@tok@s{\def\PYG@tc##1{\textcolor[rgb]{0.25,0.44,0.63}{##1}}} | |
| 86 \def\PYG@tok@kp{\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 87 \def\PYG@tok@w{\def\PYG@tc##1{\textcolor[rgb]{0.73,0.73,0.73}{##1}}} | |
| 88 \def\PYG@tok@kt{\def\PYG@tc##1{\textcolor[rgb]{0.56,0.13,0.00}{##1}}} | |
| 89 \def\PYG@tok@sc{\def\PYG@tc##1{\textcolor[rgb]{0.25,0.44,0.63}{##1}}} | |
| 90 \def\PYG@tok@sb{\def\PYG@tc##1{\textcolor[rgb]{0.25,0.44,0.63}{##1}}} | |
| 91 \def\PYG@tok@k{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.00,0.44,0.13}{##1}}} | |
| 92 \def\PYG@tok@se{\let\PYG@bf=\textbf\def\PYG@tc##1{\textcolor[rgb]{0.25,0.44,0.63}{##1}}} | |
| 93 \def\PYG@tok@sd{\let\PYG@it=\textit\def\PYG@tc##1{\textcolor[rgb]{0.25,0.44,0.63}{##1}}} | |
| 94 | |
| 95 \def\PYGZbs{\char`\\} | |
| 96 \def\PYGZus{\char`\_} | |
| 97 \def\PYGZob{\char`\{} | |
| 98 \def\PYGZcb{\char`\}} | |
| 99 \def\PYGZca{\char`\^} | |
| 100 \def\PYGZsh{\char`\#} | |
| 101 \def\PYGZpc{\char`\%} | |
| 102 \def\PYGZdl{\char`\$} | |
| 103 \def\PYGZti{\char`\~} | |
| 104 % for compatibility with earlier versions | |
| 105 \def\PYGZat{@} | |
| 106 \def\PYGZlb{[} | |
| 107 \def\PYGZrb{]} | |
| 108 \makeatother | |
| 109 | |
| 110 \begin{document} | |
| 111 | |
| 112 \maketitle | |
| 113 \tableofcontents | |
| 114 \phantomsection\label{index::doc} | |
| 115 | |
| 116 | |
| 117 Contents: | |
| 118 | |
| 119 | |
| 120 \chapter{Introduction} | |
| 121 \label{introduction:introduction}\label{introduction:welcome-to-single-calculus-chain-interface-s-documentation}\label{introduction::doc}\begin{itemize} | |
| 122 \item {} | |
| 123 The Single calculus chain is made of different modules. These modules don't interact directly but only change value in a database. | |
| 124 | |
| 125 \item {} | |
| 126 This interface will allow Earlinet memebers to interact with parts of the database. | |
| 127 | |
| 128 \item {} | |
| 129 One part of the interface (the ``Station admin'' section) permits registering a new station, registerring new lidar systems and configuration, fill in details for the channels that constitute the system and finnaly define the products (extinction, backscatter e.t.c.) that need to be calculated by the SCC. | |
| 130 | |
| 131 \item {} | |
| 132 The second part of the interface is dedicated to the uploading of new measurement files, the configuration of the measurement specific paramters and, finally, the retrieval of the calculated products. | |
| 133 | |
| 134 \item {} | |
| 135 Different types of users, with different level of access permissions can have access in the interface. In this way, higher level of flexibility and security can be achived. | |
| 136 | |
| 137 \end{itemize} | |
| 138 | |
| 139 | |
| 140 \chapter{Tutorial} | |
| 141 \label{tutorial::doc}\label{tutorial:tutorial} | |
| 142 | |
| 143 \section{Introduction} | |
| 144 \label{tutorial/introduction:introduction}\label{tutorial/introduction::doc}\begin{itemize} | |
| 145 \item {} | |
| 146 The Single calculus chain is made of different modules. These modules don't interact directly but only change value in a database. | |
| 147 | |
| 148 \item {} | |
| 149 This interface will allow Earlinet memebers to interact with parts of the database. | |
| 150 | |
| 151 \item {} | |
| 152 One part of the interface (the ``Station admin'' section) permits registering a new station, registerring new lidar systems and configuration, fill in details for the channels that constitute the system and finnaly define the products (extinction, backscatter e.t.c.) that need to be calculated by the SCC. | |
| 153 | |
| 154 \item {} | |
| 155 The second part of the interface is dedicated to the uploading of new measurement files, the configuration of the measurement specific paramters and, finally, the retrieval of the calculated products. | |
| 156 | |
| 157 \item {} | |
| 158 Different types of users, with different level of access permissions can have access in the interface. In this way, higher level of flexibility and security can be achived. | |
| 159 | |
| 160 \end{itemize} | |
| 161 | |
| 162 | |
| 163 \section{Adding a station} | |
| 164 \label{tutorial/adding_station:adding-a-station}\label{tutorial/adding_station::doc} | |
| 165 You can change all your settings throught the \emph{admin section} of the website. | |
| 166 To reach it, click on \textbf{Station admin} link at the main menu of the site. | |
| 167 | |
| 168 \begin{notice}{note}{Note:} | |
| 169 You will need to have an account with admin access privilages to access this part of the site. | |
| 170 See {\hyperref[user_management:user-management]{\emph{User management}}} for details. | |
| 171 \end{notice} | |
| 172 | |
| 173 The first you have to do to start using the single calculus chain is to register your station. | |
| 174 To do this, go the the admin section and click on the \textbf{HOI stations} in the \emph{System settings} panel. | |
| 175 This will take you to a page with a list of all stations that you account has access to. This list should | |
| 176 be empty if this is the first time you add a station. | |
| 177 | |
| 178 To add a new station to the database click on \textbf{Add HOI station} at the top right of the screen. | |
| 179 This will take you to a new page were you can fill in the needed information. The fields in \textbf{bold} | |
| 180 are mandatory and you will need to fill them before you can save you new station. | |
| 181 | |
| 182 For now you will need to fill in the following fields: | |
| 183 \begin{description} | |
| 184 \item[{Name}] \leavevmode | |
| 185 The name of the station | |
| 186 | |
| 187 \item[{Id}] \leavevmode | |
| 188 The earlinet call sign with exactly 2 characters. | |
| 189 | |
| 190 \item[{Institute name}] \leavevmode | |
| 191 The name of the institute that own the system | |
| 192 | |
| 193 \item[{Latitude}] \leavevmode | |
| 194 In degrees north is the latitude of the station. | |
| 195 | |
| 196 \item[{Longitude}] \leavevmode | |
| 197 In degrees east is the longitude of the station. | |
| 198 | |
| 199 \item[{Height asl}] \leavevmode | |
| 200 The altitude of the station in meters above sea level. | |
| 201 | |
| 202 \item[{PI}] \leavevmode | |
| 203 The name of the Principal Investigator of the station. | |
| 204 | |
| 205 \end{description} | |
| 206 | |
| 207 You can leave all the other fields empty. When you are done, press the \textbf{save} button at the bottom right of the page. | |
| 208 This will take you back to the list of your stations. If everything went OK your station you just added should appear | |
| 209 in the list. | |
| 210 | |
| 211 We don't have to make any more changes in this part, so you can click on \textbf{Home} | |
| 212 on the top left of the page to return to the starting page of the \emph{admin section}. | |
| 213 | |
| 214 | |
| 215 \section{Adding a system} | |
| 216 \label{tutorial/adding_system::doc}\label{tutorial/adding_system:adding-a-system} | |
| 217 After adding a station to the database, we need to add a new system. | |
| 218 To do this, click on the \textbf{HOI systems} in the \emph{System settings} panel. | |
| 219 This will take you to a page with a list of all availabe systems that are connected with your stations. This list should | |
| 220 be empty if this is the first time you add a system. | |
| 221 | |
| 222 \begin{notice}{note}{Note:} | |
| 223 In the Single Calculus Chain, a \emph{HOI System} represents a specific configuration of a lidar system. | |
| 224 For example, if you are operating a lidar system and you use different channels during daytime and nightime, | |
| 225 you will need to register \emph{two different} systems in the database, one for each different configuration you use. | |
| 226 \end{notice} | |
| 227 | |
| 228 To add a new system to the database click on \textbf{Add HOI system} at the top right of the screen. | |
| 229 This will take you to a new page were you can fill in the needed information. As before, the fields in \textbf{bold} | |
| 230 are mandatory and you will need to fill them before you can save you new system. | |
| 231 | |
| 232 \begin{notice}{note}{Note:} | |
| 233 Not every field that is present in the database is used in the in the Single Calculs Chain. | |
| 234 Many of them are part of the Handbook of Instruments. | |
| 235 \end{notice} | |
| 236 | |
| 237 For now you will need to fill in the following fields: | |
| 238 \begin{description} | |
| 239 \item[{Name}] \leavevmode | |
| 240 The name of your system. | |
| 241 | |
| 242 \item[{Station (owner)}] \leavevmode | |
| 243 From the drop-down list, select the station which this system belongs to. | |
| 244 | |
| 245 \item[{Configuration}] \leavevmode | |
| 246 The name of the specific configuration. For example you could specify ``night time'' if the system you are registering | |
| 247 correspond to the night-time configuration of your system | |
| 248 | |
| 249 \item[{Pi}] \leavevmode | |
| 250 The principle investigator of this system | |
| 251 | |
| 252 \item[{Height asl}] \leavevmode | |
| 253 The altitude of the system above sea level (in meters). | |
| 254 | |
| 255 \end{description} | |
| 256 | |
| 257 You can leave all the other fields empty. When you are done, press the \textbf{save} button at the bottom right of the page. | |
| 258 This will take you back to the list of your systems. If everything went OK your new system you just added should appear | |
| 259 in the list. | |
| 260 | |
| 261 We don't have to make any more changes in this part, so you can click on \textbf{Home} | |
| 262 on the top left of the page to return to the starting page of the \emph{admin section}. | |
| 263 | |
| 264 | |
| 265 \section{Adding equipment} | |
| 266 \label{tutorial/adding_telescopelaser:adding-equipment}\label{tutorial/adding_telescopelaser::doc} | |
| 267 After adding a system to the database, we need to add at least one telescope and one laser before you add a channel. | |
| 268 | |
| 269 | |
| 270 \subsection{Telescope} | |
| 271 \label{tutorial/adding_telescopelaser:telescope} | |
| 272 To add a new telescope, click on the \textbf{HOI telescopes} in the \emph{System settings} panel. | |
| 273 This will take you to a page with a list of all availabe telescopes that are connected with your station. | |
| 274 This list should be empty if this is the first time you add a telescope. | |
| 275 | |
| 276 To add a new telescope to the database click on \textbf{Add HOI telescope} at the top right of the screen. | |
| 277 This will take you to a new page were you can fill in the needed information. Once again, the fields in \textbf{bold} | |
| 278 are mandatory and you will need to fill them before you can save you new telescope. | |
| 279 | |
| 280 The fields you need to add are: | |
| 281 \begin{description} | |
| 282 \item[{Type}] \leavevmode | |
| 283 The telescope type | |
| 284 | |
| 285 \item[{Diameter}] \leavevmode | |
| 286 The diameter of the primary mirror in mm | |
| 287 | |
| 288 \item[{Focal length}] \leavevmode | |
| 289 The equivalent focal length of the telescope in mm | |
| 290 | |
| 291 \item[{Full overlap height}] \leavevmode | |
| 292 The height where the full overlap is achieved. | |
| 293 | |
| 294 \end{description} | |
| 295 | |
| 296 When you are done, press the \textbf{save} button at the bottom right of the page. If no errors are present, you will return to | |
| 297 the telescope list page. Your new telescope should appear in the list. | |
| 298 | |
| 299 | |
| 300 \subsection{Laser} | |
| 301 \label{tutorial/adding_telescopelaser:laser} | |
| 302 To add a new laser, click on the \textbf{HOI Laser} in the \emph{System settings} panel. | |
| 303 This will take you to a page with a list of all availabe lasers that are connected with your station. | |
| 304 This list should be empty if this is the first time you add a laser. | |
| 305 | |
| 306 To add a new telescope to the database click on \textbf{Add HOI laser} at the top right of the screen. | |
| 307 This will take you to a new page were you can fill in the needed information. The fields in \textbf{bold} | |
| 308 are mandatory and you will need to fill them before you can save you new telescope. | |
| 309 | |
| 310 The fields you need to add are: | |
| 311 \begin{description} | |
| 312 \item[{Manufacturer}] \leavevmode | |
| 313 The manufacturer of the telescope | |
| 314 | |
| 315 \item[{Model}] \leavevmode | |
| 316 The model of the telescope | |
| 317 | |
| 318 \item[{Repetition rate}] \leavevmode | |
| 319 The repetition rate in Hz | |
| 320 | |
| 321 \item[{Type}] \leavevmode | |
| 322 The type of the laser (ex. Nd:YAG) | |
| 323 | |
| 324 \end{description} | |
| 325 | |
| 326 When you are done, press the \textbf{save} button at the bottom right of the page. If no errors are present, you will return to | |
| 327 the laser list page. The new laser you added should be present there. | |
| 328 | |
| 329 | |
| 330 \section{Adding a channel} | |
| 331 \label{tutorial/adding_channels::doc}\label{tutorial/adding_channels:adding-a-channel} | |
| 332 After adding a system, a telescope and a laser to the database, you need to add a new channel. | |
| 333 To do this, click on the \textbf{HOI channels} in the \emph{System settings} panel. | |
| 334 This will take you to a page with a list of all availabe channels that are connected with your lidar systems. | |
| 335 This list should be empty if this is the first time you add a system. | |
| 336 | |
| 337 To add a new channel to the database click on \textbf{Add HOI channel} at the top right of the screen. | |
| 338 This will take you to a new page were you can fill in the needed information. As before, the fields in \textbf{bold} | |
| 339 are mandatory and you will need to fill them before you can save you new system. | |
| 340 | |
| 341 The fileds you have to fill here are more, as many of these are used during the processing of measurements. | |
| 342 | |
| 343 \begin{notice}{warning}{Warning:} | |
| 344 There is a last step, different from the previous cases, when saving a new channel. You need to connect your channel with | |
| 345 a lidar system before you save, or else all your entry will be lost. Read carefully through this document (or directly | |
| 346 the {\hyperref[tutorial/adding_channels:connect-channel-to-system]{\emph{last section}}}) to avoid any problems. | |
| 347 \end{notice} | |
| 348 | |
| 349 | |
| 350 \subsection{Fill in the fields} | |
| 351 \label{tutorial/adding_channels:fill-in-the-fields} | |
| 352 To start using the single calculus chain you will need to fill the following fields: | |
| 353 \begin{description} | |
| 354 \item[{Name}] \leavevmode | |
| 355 The name of the channel ex. ``355'', ``1064 analog'' etc. | |
| 356 | |
| 357 \item[{Telescope}] \leavevmode | |
| 358 The telescope that is used for this channel | |
| 359 | |
| 360 \item[{Laser}] \leavevmode | |
| 361 The laser that is used for this channel | |
| 362 | |
| 363 \item[{Interference filter center}] \leavevmode | |
| 364 The center of the interference filter in nm | |
| 365 | |
| 366 \item[{Interference filter FWHM}] \leavevmode | |
| 367 The FWHM of the interference filter in nm | |
| 368 | |
| 369 \item[{Emission wavelength}] \leavevmode | |
| 370 The emission wavelength of the laser used for this channel | |
| 371 | |
| 372 \item[{Field of view}] \leavevmode | |
| 373 The field of view realated to this channel in mrad | |
| 374 | |
| 375 \item[{Raw range resolution}] \leavevmode | |
| 376 The raw range resolution of the measured data in m | |
| 377 | |
| 378 \item[{Dead time}] \leavevmode | |
| 379 The dead of the detector in ns. You should fill in this in case | |
| 380 of a photon counting detector. | |
| 381 | |
| 382 \item[{Trigger delay}] \leavevmode | |
| 383 The trigger delay value for the channel in ns. Fill in 0 if not needed. | |
| 384 | |
| 385 \item[{Scattering mechanism}] \leavevmode | |
| 386 The scattering mechanism that is involved in this channel. Select the appropriate value from the drop-down list. | |
| 387 | |
| 388 \item[{Dead time correction type}] \leavevmode | |
| 389 The dead time correction type to be applied. Select \emph{Not defined} if none needs to be defined. | |
| 390 | |
| 391 \item[{Background mode}] \leavevmode | |
| 392 The way to calculate the singal background. Select \emph{Not defined} if none needs to be defined. | |
| 393 | |
| 394 \item[{Signal type}] \leavevmode | |
| 395 The type of the singal that is measured, ex. ``elT'' for total elastic, ``vrRN2'' for vibrational-rotational | |
| 396 Raman signal from Nitrogen melecules etc. See {\hyperref[details/adding_channels:signal-types]{\emph{Signal types}}} for details. | |
| 397 | |
| 398 \item[{Detection mode}] \leavevmode | |
| 399 The detection mode of this channel. | |
| 400 | |
| 401 \end{description} | |
| 402 | |
| 403 | |
| 404 \subsection{Connecting to a system} | |
| 405 \label{tutorial/adding_channels:connect-channel-to-system}\label{tutorial/adding_channels:connecting-to-a-system} | |
| 406 Before you finish, you need to attach your channel to one of your systems. To do this, go at the bottom of the page and | |
| 407 select your system from the drop-down list in the \textbf{System channels} area. | |
| 408 | |
| 409 When you are done, press the \textbf{save} button at the bottom right of the page. | |
| 410 This will take you back to the list of your channels. | |
| 411 If everything went OK your new channel you just added should appear in the list. | |
| 412 | |
| 413 | |
| 414 \section{Adding products} | |
| 415 \label{tutorial/adding_products:adding-products}\label{tutorial/adding_products::doc} | |
| 416 Walk-through of adding a product. | |
| 417 | |
| 418 | |
| 419 \section{Processing data} | |
| 420 \label{tutorial/processing_data:processing-data}\label{tutorial/processing_data::doc} | |
| 421 Walk-through of how to upload a file and seeing the results. | |
| 422 | |
| 423 | |
| 424 \chapter{Detailed documentation} | |
| 425 \label{interface_details::doc}\label{interface_details:detailed-documentation} | |
| 426 Contents: | |
| 427 | |
| 428 | |
| 429 \section{Introduction} | |
| 430 \label{details/introduction:introduction}\label{details/introduction::doc} | |
| 431 | |
| 432 \section{Adding stations} | |
| 433 \label{details/adding_station:adding-stations}\label{details/adding_station::doc} | |
| 434 You can add the definition of new systems that belong to the station by clicking on the Hoi System blue line that | |
| 435 appears bollow the main station fields. For more details on the filed you need to fill in see the {\hyperref[details/adding_system:add-new-system]{\emph{Adding systems}}} section. | |
| 436 You can add more stations by clicking on the ``Add another Hoi System'' option. | |
| 437 | |
| 438 \begin{notice}{note}{Note:} | |
| 439 You need to have \emph{Javascript} enebled to add a new station from this page. | |
| 440 \end{notice} | |
| 441 | |
| 442 | |
| 443 \section{Adding systems} | |
| 444 \label{details/adding_system:add-new-system}\label{details/adding_system:adding-systems}\label{details/adding_system::doc} | |
| 445 | |
| 446 \section{Adding channels} | |
| 447 \label{details/adding_channels::doc}\label{details/adding_channels:adding-channels} | |
| 448 | |
| 449 \subsection{Signal types} | |
| 450 \label{details/adding_channels:signal-types}\label{details/adding_channels:id1} | |
| 451 (explain here all the signal type abreviations). | |
| 452 | |
| 453 | |
| 454 \section{Adding products} | |
| 455 \label{details/adding_products:adding-products}\label{details/adding_products::doc} | |
| 456 | |
| 457 \section{Adding other equipment} | |
| 458 \label{details/adding_otherequipment:adding-other-equipment}\label{details/adding_otherequipment::doc} | |
| 459 | |
| 460 \section{The Handbook of instruments} | |
| 461 \label{details/handbook_of_instruments:the-handbook-of-instruments}\label{details/handbook_of_instruments::doc} | |
| 462 | |
| 463 \section{Uploading measuremnents} | |
| 464 \label{details/uploading_measurements:uploading-measuremnents}\label{details/uploading_measurements::doc} | |
| 465 123 | |
| 466 | |
| 467 | |
| 468 \section{View processing results} | |
| 469 \label{details/viewing_measurements:view-processing-results}\label{details/viewing_measurements::doc} | |
| 470 123 | |
| 471 | |
| 472 | |
| 473 \chapter{The SCC netCDF file format} | |
| 474 \label{netcdf_file:the-scc-netcdf-file-format}\label{netcdf_file::doc} | |
| 475 | |
| 476 \section{Rationale} | |
| 477 \label{netcdf_file:rationale} | |
| 478 The Single Calculus Chain (SCC) is composed by two different modules: | |
| 479 \begin{itemize} | |
| 480 \item {} | |
| 481 pre-processing module ( scc\_preprocessing) | |
| 482 | |
| 483 \item {} | |
| 484 optical processing module ( ELDA) | |
| 485 | |
| 486 \end{itemize} | |
| 487 | |
| 488 To perfom aerosol optical retrievals the SCC needs not only the raw | |
| 489 lidar data but also a certain number of parameters to use in both | |
| 490 pre-processing and optical processing stages. The SCC gets these | |
| 491 parameters looking at two different locations: | |
| 492 \begin{itemize} | |
| 493 \item {} | |
| 494 Single Calculus Chain relational database (SCC\_DB) | |
| 495 | |
| 496 \item {} | |
| 497 Input files | |
| 498 | |
| 499 \end{itemize} | |
| 500 | |
| 501 There are some paramenters that can be found only in the input files | |
| 502 (those ones changing from measurement to measurement), others that can | |
| 503 be found only in the SCC\_DB and other ones that can be found in both | |
| 504 these locations. In the last case, if a particular parameter is needed, | |
| 505 the SCC will search first in the input files and then in SCC\_DB. If the | |
| 506 parameter is found in the input files the SCC will keep it without | |
| 507 looking into SCC\_DB. | |
| 508 | |
| 509 The input files have to be submitted to the SCC in NetCDF format. At the | |
| 510 present the SCC can handle four different types of input files: | |
| 511 \begin{enumerate} | |
| 512 \item {} | |
| 513 Raw Lidar Data | |
| 514 | |
| 515 \item {} | |
| 516 Sounding Data | |
| 517 | |
| 518 \item {} | |
| 519 Overlap | |
| 520 | |
| 521 \item {} | |
| 522 Lidar Ratio | |
| 523 | |
| 524 \end{enumerate} | |
| 525 | |
| 526 As already mentioned, the Raw Lidar Data file contains not only the | |
| 527 raw lidar data but also other parameters to use to perform the | |
| 528 pre-processing and optical processing. The Sounding Data file | |
| 529 contains the data coming from a correlative radiosounding and it is used | |
| 530 by the SCC for molecular density calculation. The Overlap file | |
| 531 contains the measured overlap function. The Lidar Ratio file contains | |
| 532 a lidar ratio profile to use in elastic backscatter retrievals. The | |
| 533 Raw Lidar Data file is of course mandatory and the Sounding Data, | |
| 534 Overlap and Lidar Ratio files are optional. If Sounding Data file | |
| 535 is not submitted by the user, the molecular density will be calculated | |
| 536 by the SCC using the “US Standard Atmosphere 1976”. If the Overlap | |
| 537 file is not submitted by the user, the SCC will get the full overlap | |
| 538 height from SCC\_DB and it will produce optical results starting from | |
| 539 this height. If Lidar Ratio file is not submitted by the user, the | |
| 540 SCC will consider a fixed value for lidar ratio got from SCC\_DB. | |
| 541 | |
| 542 The user can decide to submit all these files or any number of them (of | |
| 543 course the file Raw Lidar Data is mandatory). For example the user | |
| 544 can submit together with the Raw Lidar Data file only the Sounding | |
| 545 Data file or only the Overlap file. | |
| 546 | |
| 547 This document provides a detailed explanation about the structure of the | |
| 548 NetCDF input files to use for SCC data submission. All Earlinet groups | |
| 549 should read it carefully because they have to produce such kind of input | |
| 550 files if they want to use the SCC for their standard lidar retrievals. | |
| 551 Every comments or suggestions regarding this document can be sent to | |
| 552 Giuseppe D’Amico by e-mail at \code{damico@imaa.cnr.it} | |
| 553 | |
| 554 This document is available for downloading at \code{www.earlinetasos.org} | |
| 555 | |
| 556 In table tab:rawdata is reported a list of dimensions, variables and | |
| 557 global attributes that can be used in the NetCDF Raw Lidar Data input | |
| 558 file. For each of them it is indicated: | |
| 559 \begin{itemize} | |
| 560 \item {} | |
| 561 The name. For the multidimensional variables also the corresponding | |
| 562 dimensions are reported | |
| 563 | |
| 564 \item {} | |
| 565 A description explaining the meaning | |
| 566 | |
| 567 \item {} | |
| 568 The type | |
| 569 | |
| 570 \item {} | |
| 571 If it is mandatory or optional | |
| 572 | |
| 573 \end{itemize} | |
| 574 | |
| 575 As already mentioned, the SCC can get some parameters looking first in | |
| 576 the Raw Lidar Data input file and then into SCC\_DB. This means that | |
| 577 to use the parameters stored in SCC\_DB the optional variables or | |
| 578 optional global attributes must not appear within Raw Lidar Data | |
| 579 file. This is the suggested and recommended way to use the SCC. Please | |
| 580 include optional parameters in the Raw Lidar Data only as an | |
| 581 exception. | |
| 582 | |
| 583 In table tab:sounding, tab:overlap and tab:lr are reported all the | |
| 584 information about the structure of Sounding Data, Overlap and | |
| 585 Lidar Ratio input files respectively. | |
| 586 | |
| 587 | |
| 588 \section{Example} | |
| 589 \label{netcdf_file:example} | |
| 590 Let’s now consider an example of Raw Lidar Data input file. Suppose | |
| 591 we want to generate NetCDF input file corresponding to a measurement | |
| 592 with the following properties: | |
| 593 | |
| 594 \begin{tabulary}{\linewidth}{|L|L|} | |
| 595 \hline | |
| 596 | |
| 597 Start Date | |
| 598 & | |
| 599 $30^{th}$ January 2009 | |
| 600 \\\hline | |
| 601 | |
| 602 Start Time UT | |
| 603 & | |
| 604 00:00:01 | |
| 605 \\\hline | |
| 606 | |
| 607 Stop Time UT | |
| 608 & | |
| 609 00:05:01 | |
| 610 \\\hline | |
| 611 | |
| 612 Station Name | |
| 613 & | |
| 614 Dummy station | |
| 615 \\\hline | |
| 616 | |
| 617 Earlinet call-sign | |
| 618 & | |
| 619 cc | |
| 620 \\\hline | |
| 621 | |
| 622 Pointing angle | |
| 623 & | |
| 624 5 degrees with respect to the zenith | |
| 625 \\\hline | |
| 626 \end{tabulary} | |
| 627 | |
| 628 | |
| 629 Moreover suppose that this measurement is composed by the following | |
| 630 lidar channels: | |
| 631 \begin{enumerate} | |
| 632 \item {} | |
| 633 1064 lidar channel | |
| 634 | |
| 635 \begin{tabulary}{\linewidth}{|L|L|} | |
| 636 \hline | |
| 637 | |
| 638 Emission wavelength=1064nm | |
| 639 & | |
| 640 Detection wavelength=1064nm | |
| 641 \\\hline | |
| 642 | |
| 643 Time resolution=30s | |
| 644 & | |
| 645 Number of laser shots=1500 | |
| 646 \\\hline | |
| 647 | |
| 648 Number of bins=3000 | |
| 649 & | |
| 650 Detection mode=analog | |
| 651 \\\hline | |
| 652 | |
| 653 Range resolution=7.5m | |
| 654 & | |
| 655 Polarization state=total | |
| 656 \\\hline | |
| 657 \end{tabulary} | |
| 658 | |
| 659 | |
| 660 \item {} | |
| 661 532 cross lidar channel | |
| 662 | |
| 663 \begin{tabulary}{\linewidth}{|L|L|} | |
| 664 \hline | |
| 665 | |
| 666 Emission wavelength=532nm | |
| 667 & | |
| 668 Detection wavelength=532nm | |
| 669 \\\hline | |
| 670 | |
| 671 Time resolution=60s | |
| 672 & | |
| 673 Number of laser shots=3000 | |
| 674 \\\hline | |
| 675 | |
| 676 Number of bins=5000 | |
| 677 & | |
| 678 Detection mode=photoncounting | |
| 679 \\\hline | |
| 680 | |
| 681 Range resolution=15m | |
| 682 & | |
| 683 Polarization state=cross | |
| 684 \\\hline | |
| 685 \end{tabulary} | |
| 686 | |
| 687 | |
| 688 \item {} | |
| 689 532 parallel lidar channel | |
| 690 | |
| 691 \begin{tabulary}{\linewidth}{|L|L|} | |
| 692 \hline | |
| 693 | |
| 694 Emission wavelength=532nm | |
| 695 & | |
| 696 Detection wavelength=532nm | |
| 697 \\\hline | |
| 698 | |
| 699 Time resolution=60s | |
| 700 & | |
| 701 Number of laser shots=3000 | |
| 702 \\\hline | |
| 703 | |
| 704 Number of bins=5000 | |
| 705 & | |
| 706 Detection mode=photoncounting | |
| 707 \\\hline | |
| 708 | |
| 709 Range resolution=15m | |
| 710 & | |
| 711 Polarization state=parallel | |
| 712 \\\hline | |
| 713 \end{tabulary} | |
| 714 | |
| 715 | |
| 716 \item {} | |
| 717 607 $N_2$ vibrational Raman channel | |
| 718 | |
| 719 \begin{tabulary}{\linewidth}{|L|L|} | |
| 720 \hline | |
| 721 | |
| 722 Emission wavelength=532nm | |
| 723 & | |
| 724 Detection wavelength=607nm | |
| 725 \\\hline | |
| 726 | |
| 727 Time resolution=60s | |
| 728 & | |
| 729 Number of laser shots=3000 | |
| 730 \\\hline | |
| 731 | |
| 732 Number of bins=5000 | |
| 733 & | |
| 734 Detection mode=photoncounting | |
| 735 \\\hline | |
| 736 \multicolumn{2}{|l|}{ | |
| 737 Range resolution=15m | |
| 738 }\\\hline | |
| 739 \end{tabulary} | |
| 740 | |
| 741 | |
| 742 \end{enumerate} | |
| 743 | |
| 744 Finally let’s assume we have also performed dark measurements before the | |
| 745 lidar measurements from the 23:50:01 UT up to 23:53:01 UT of | |
| 746 29:math:\emph{\textasciicircum{}mathrmth} January 2009. | |
| 747 | |
| 748 | |
| 749 \subsection{Dimensions} | |
| 750 \label{netcdf_file:dimensions} | |
| 751 Looking at table tab:rawdata we have to fix the following dimensions: | |
| 752 | |
| 753 \begin{Verbatim}[commandchars=\\\{\}] | |
| 754 \PYG{n}{points} | |
| 755 \PYG{n}{channels} | |
| 756 \PYG{n}{time} | |
| 757 \PYG{n}{nb\PYGZus{}of\PYGZus{}time\PYGZus{}scales} | |
| 758 \PYG{n}{scan\PYGZus{}angles} | |
| 759 \PYG{n}{time\PYGZus{}bck} | |
| 760 \end{Verbatim} | |
| 761 | |
| 762 The dimension \code{time} is unlimited so we don’t have to fix it. | |
| 763 | |
| 764 We have 4 lidar channels so: | |
| 765 | |
| 766 \begin{Verbatim}[commandchars=\\\{\}] | |
| 767 \PYG{n}{channels}\PYG{o}{=}\PYG{l+m+mi}{4} | |
| 768 \end{Verbatim} | |
| 769 | |
| 770 Regarding the dimension \code{points} we have only one channel with a | |
| 771 number of vertical bins equal to 3000 (the 1064nm) and all other | |
| 772 channels with 5000 vertical bins. In cases like this the dimension | |
| 773 \code{points} has to be fixed to the maximum number of vertical bins so: | |
| 774 | |
| 775 \begin{Verbatim}[commandchars=\\\{\}] | |
| 776 \PYG{n}{points}\PYG{o}{=}\PYG{l+m+mi}{5000} | |
| 777 \end{Verbatim} | |
| 778 | |
| 779 Moreover only one channel (1064nm) is acquired with a time resolution of | |
| 780 30 seconds, all the other channels have a time resolution of 60 seconds. | |
| 781 This means that we have to define two different time scales. We have to | |
| 782 set: | |
| 783 | |
| 784 \begin{Verbatim}[commandchars=\\\{\}] | |
| 785 \PYG{n}{nb\PYGZus{}of\PYGZus{}time\PYGZus{}scales}\PYG{o}{=}\PYG{l+m+mi}{2} | |
| 786 \end{Verbatim} | |
| 787 | |
| 788 The measurement is performed only at one scan angle (5 degrees with | |
| 789 respect to the zenith) so: | |
| 790 | |
| 791 \begin{Verbatim}[commandchars=\\\{\}] | |
| 792 \PYG{n}{scan\PYGZus{}angles}\PYG{o}{=}\PYG{l+m+mi}{1} | |
| 793 \end{Verbatim} | |
| 794 | |
| 795 We have 3 minutes of dark measurements and two different time scales one | |
| 796 with 60 seconds time resolution and the other one with 30 seconds time | |
| 797 resolution. So we will have 3 different dark profiles for the channels | |
| 798 acquired with the first time scale and 6 for the lidar channels acquired | |
| 799 with the second time scale. We have to fix the dimension \code{time\_bck} as | |
| 800 the maximum between these values: | |
| 801 | |
| 802 \begin{Verbatim}[commandchars=\\\{\}] | |
| 803 \PYG{n}{time\PYGZus{}bck}\PYG{o}{=}\PYG{l+m+mi}{6} | |
| 804 \end{Verbatim} | |
| 805 | |
| 806 | |
| 807 \subsection{Variables} | |
| 808 \label{netcdf_file:variables} | |
| 809 In this section it will be explained how to fill all the possible | |
| 810 variables either mandatory or optional of Raw Lidar Data input file. | |
| 811 \begin{description} | |
| 812 \item[{Raw\_Data\_Start\_Time(time, nb\_of\_time\_scales)}] \leavevmode | |
| 813 This 2 dimensional mandatory array has to contain the acquisition | |
| 814 start time (in seconds from the time given by the global attribute | |
| 815 \code{RawData\_Start\_Time\_UT}) of each lidar profile. In this example we | |
| 816 have two different time scales: one is characterized by steps of 30 | |
| 817 seconds (the 1064nm is acquired with this time scale) the other by | |
| 818 steps of 60 seconds (532cross, 532parallel and 607nm). Moreover the | |
| 819 measurement start time is 00:00:01 UT and the measurement stop time | |
| 820 is 00:05:01 UT. In this case we have to define: | |
| 821 | |
| 822 \begin{Verbatim}[commandchars=\\\{\}] | |
| 823 Raw\_Data\_Start\_Time = | |
| 824 0, 0, | |
| 825 60, 30, | |
| 826 120, 60, | |
| 827 180, 90, | |
| 828 240, 120, | |
| 829 \_, 150, | |
| 830 \_, 180, | |
| 831 \_, 210, | |
| 832 \_, 240, | |
| 833 \_, 270 ; | |
| 834 \end{Verbatim} | |
| 835 | |
| 836 The order used to fill this array defines the correspondence between | |
| 837 the different time scales and the time scale index. In this example | |
| 838 we have a time scale index of 0 for the time scale with steps of 60 | |
| 839 seconds and a time scale index of 1 for the other one. | |
| 840 | |
| 841 \item[{Raw\_Data\_Stop\_Time(time, nb\_of\_time\_scales)}] \leavevmode | |
| 842 The same as previous item but for the data acquisition stop time. | |
| 843 Following a similar procedure we have to define: | |
| 844 | |
| 845 \begin{Verbatim}[commandchars=\\\{\}] | |
| 846 Raw\_Data\_Stop\_Time = | |
| 847 60, 30, | |
| 848 120, 60, | |
| 849 180, 90, | |
| 850 240, 120, | |
| 851 300, 150, | |
| 852 \_, 180, | |
| 853 \_, 210, | |
| 854 \_, 240, | |
| 855 \_, 270, | |
| 856 \_, 300 ; | |
| 857 \end{Verbatim} | |
| 858 | |
| 859 \item[{Raw\_Lidar\_Data(time, channels, points)}] \leavevmode | |
| 860 This 3 dimensional mandatory array has to be filled with the | |
| 861 time-series of raw lidar data. The photoncounting profiles have to | |
| 862 submitted in counts (so as integers) while the analog ones in mV. The | |
| 863 order the user chooses to fill this array defines the correspondence | |
| 864 between channel index and lidar data. | |
| 865 | |
| 866 For example if we fill this array in such way that: | |
| 867 | |
| 868 \begin{tabulary}{\linewidth}{|L|L|} | |
| 869 \hline | |
| 870 | |
| 871 Raw\_Lidar\_Data(time,0,points | |
| 872 & | |
| 873 $\rightarrow$ is the time-series of 1064 nm | |
| 874 \\\hline | |
| 875 | |
| 876 Raw\_Lidar\_Data(time,1,points | |
| 877 & | |
| 878 $\rightarrow$ is the time-series of 532 cross | |
| 879 \\\hline | |
| 880 | |
| 881 Raw\_Lidar\_Data(time,2,points | |
| 882 & | |
| 883 $\rightarrow$ is the time-series of 532 parallel | |
| 884 \\\hline | |
| 885 | |
| 886 Raw\_Lidar\_Data(time,3,points | |
| 887 & | |
| 888 $\rightarrow$ is the time-series of 607 nm | |
| 889 \\\hline | |
| 890 \end{tabulary} | |
| 891 | |
| 892 | |
| 893 from now on the channel index 0 is associated to the 1064 channel, | |
| 894 1 to the 532 cross, 2 to the 532 parallel and 3 to the 607nm. | |
| 895 | |
| 896 \item[{Raw\_Bck\_Start\_Time(time\_bck, nb\_of\_time\_scales)}] \leavevmode | |
| 897 This 2 dimensional optional array has to contain the acquisition | |
| 898 start time (in seconds from the time given by the global attribute | |
| 899 \code{RawBck\_Start\_Time\_UT}) of each dark measurements profile. | |
| 900 Following the same procedure used for the variable | |
| 901 \code{Raw\_Data\_Start\_Time} we have to define: | |
| 902 | |
| 903 \begin{Verbatim}[commandchars=\\\{\}] | |
| 904 Raw\_Bck\_Start\_Time = | |
| 905 0, 0, | |
| 906 60, 30, | |
| 907 120, 60, | |
| 908 \_, 90, | |
| 909 \_, 120, | |
| 910 \_, 150; | |
| 911 \end{Verbatim} | |
| 912 | |
| 913 \item[{Raw\_Bck\_Stop\_Time(time\_bck, nb\_of\_time\_scales)}] \leavevmode | |
| 914 The same as previous item but for the dark acquisition stop time. | |
| 915 Following a similar procedure we have to define: | |
| 916 | |
| 917 \begin{Verbatim}[commandchars=\\\{\}] | |
| 918 Raw\_Bck\_Stop\_Time = | |
| 919 60, 30, | |
| 920 120, 60, | |
| 921 180, 90, | |
| 922 \_, 120, | |
| 923 \_, 150, | |
| 924 \_, 180 ; | |
| 925 \end{Verbatim} | |
| 926 | |
| 927 \item[{Background\_Profile(time\_bck, channels, points)}] \leavevmode | |
| 928 This 3 dimensional optional array has to be filled with the | |
| 929 time-series of the dark measurements data. The photoncounting | |
| 930 profiles have to submitted in counts (so as integers) while the | |
| 931 analog ones in mV. The user has to fill this array following the same | |
| 932 order used in filling the array \code{Raw\_Lidar\_Data}: | |
| 933 | |
| 934 \begin{tabulary}{\linewidth}{|L|L|} | |
| 935 \hline | |
| 936 | |
| 937 Background\_Profile(time\_bck,0,points | |
| 938 & | |
| 939 $\rightarrow$ dark time-series at 1064 nm | |
| 940 \\\hline | |
| 941 | |
| 942 Background\_Profile(time\_bck,1,points | |
| 943 & | |
| 944 $\rightarrow$ dark time-series at 532 cross | |
| 945 \\\hline | |
| 946 | |
| 947 Background\_Profile(time\_bck,2,points | |
| 948 & | |
| 949 $\rightarrow$ dark time-series at 532 parallel | |
| 950 \\\hline | |
| 951 | |
| 952 Background\_Profile(time\_bck,3,points | |
| 953 & | |
| 954 $\rightarrow$ dark time-series at 607 nm | |
| 955 \\\hline | |
| 956 \end{tabulary} | |
| 957 | |
| 958 | |
| 959 \item[{channel\_ID(channels)}] \leavevmode | |
| 960 This mandatory array provides the link between the channel index | |
| 961 within the Raw Lidar Data input file and the channel ID in | |
| 962 SCC\_DB. To fill this variable the user has to know which channel IDs | |
| 963 in SCC\_DB correspond to his lidar channels. For this purpose the | |
| 964 SCC, in its final version will provide to the user a special tool to | |
| 965 get these channel IDs through a Web interface. At the moment this | |
| 966 interface is not yet available and these channel IDs will be | |
| 967 communicated directly to the user by the NA5 people. | |
| 968 | |
| 969 Anyway to continue the example let’s suppose that the four lidar | |
| 970 channels taken into account are mapped into SCC\_DB with the | |
| 971 following channel IDs: | |
| 972 | |
| 973 \begin{tabulary}{\linewidth}{|L|L|} | |
| 974 \hline | |
| 975 | |
| 976 1064 nm | |
| 977 & | |
| 978 $\rightarrow$ channel ID=7 | |
| 979 \\\hline | |
| 980 | |
| 981 532 cross | |
| 982 & | |
| 983 $\rightarrow$ channel ID=5 | |
| 984 \\\hline | |
| 985 | |
| 986 532 parallel | |
| 987 & | |
| 988 $\rightarrow$ channel ID=6 | |
| 989 \\\hline | |
| 990 | |
| 991 607 nm | |
| 992 & | |
| 993 $\rightarrow$ channel ID=8 | |
| 994 \\\hline | |
| 995 \end{tabulary} | |
| 996 | |
| 997 \begin{quote} | |
| 998 | |
| 999 In this case we have to define: | |
| 1000 \end{quote} | |
| 1001 | |
| 1002 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1003 \PYG{n}{channel\PYGZus{}ID} \PYG{o}{=} \PYG{l+m+mi}{7}\PYG{p}{,} \PYG{l+m+mi}{5}\PYG{p}{,} \PYG{l+m+mi}{6}\PYG{p}{,} \PYG{l+m+mi}{8} \PYG{p}{;} | |
| 1004 \end{Verbatim} | |
| 1005 | |
| 1006 \item[{id\_timescale(channels)}] \leavevmode | |
| 1007 This mandatory array is introduced to determine which time scale is | |
| 1008 used for the acquisition of each lidar channel. In particular this | |
| 1009 array defines the link between the channel index and the time scale | |
| 1010 index. In our example we have two different time scales. Filling the | |
| 1011 arrays \code{Raw\_Data\_Start\_Time} and \code{Raw\_Data\_Stop\_Time} we have | |
| 1012 defined a time scale index of 0 for the time scale with steps of 60 | |
| 1013 seconds and a time scale index of 1 for the other one with steps of | |
| 1014 30 seconds. In this way this array has to be set as: | |
| 1015 | |
| 1016 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1017 \PYG{n}{id\PYGZus{}timescale} \PYG{o}{=} \PYG{l+m+mi}{1}\PYG{p}{,} \PYG{l+m+mi}{0}\PYG{p}{,} \PYG{l+m+mi}{0}\PYG{p}{,} \PYG{l+m+mi}{0} \PYG{p}{;} | |
| 1018 \end{Verbatim} | |
| 1019 | |
| 1020 \item[{Laser\_Pointing\_Angle(scan\_angles}] \leavevmode | |
| 1021 This mandatory array contains all the scan angles used in the | |
| 1022 measurement. In our example we have only one scan angle of 5 degrees | |
| 1023 with respect to the zenith, so we have to define: | |
| 1024 | |
| 1025 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1026 \PYG{n}{Laser\PYGZus{}Pointing\PYGZus{}Angle} \PYG{o}{=} \PYG{l+m+mi}{5} \PYG{p}{;} | |
| 1027 \end{Verbatim} | |
| 1028 | |
| 1029 \item[{Laser\_Pointing\_Angle\_of\_Profiles(time, nb\_of\_time\_scales)}] \leavevmode | |
| 1030 This mandatory array is introduced to determine which scan angle is | |
| 1031 used for the acquisition of each lidar profile. In particular this | |
| 1032 array defines the link between the time and time scales indexes and | |
| 1033 the scan angle index. In our example we have a single scan angle that | |
| 1034 has to correspond to the scan angle index 0. So this array has to be | |
| 1035 defined as: | |
| 1036 | |
| 1037 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1038 Laser\_Pointing\_Angle\_of\_Profiles = | |
| 1039 0, 0, | |
| 1040 0, 0, | |
| 1041 0, 0, | |
| 1042 0, 0, | |
| 1043 0, 0, | |
| 1044 \_, 0, | |
| 1045 \_, 0, | |
| 1046 \_, 0, | |
| 1047 \_, 0, | |
| 1048 \_, 0 ; | |
| 1049 \end{Verbatim} | |
| 1050 | |
| 1051 \item[{Laser\_Shots(time, channels)}] \leavevmode | |
| 1052 This mandatory array stores the laser shots accumulated at each time | |
| 1053 for each channel. In our example the number of laser shots | |
| 1054 accumulated is 1500 for the 1064nm channels and 3000 for all the | |
| 1055 other channels. Moreover the laser shots do not change with the time. | |
| 1056 So we have to define this array as: | |
| 1057 | |
| 1058 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1059 Laser\_Shots = | |
| 1060 1500, 3000, 3000, 3000, | |
| 1061 1500, 3000, 3000, 3000, | |
| 1062 1500, 3000, 3000, 3000, | |
| 1063 1500, 3000, 3000, 3000, | |
| 1064 1500, 3000, 3000, 3000, | |
| 1065 1500, \_, \_, \_, | |
| 1066 1500, \_, \_, \_, | |
| 1067 1500, \_, \_, \_, | |
| 1068 1500, \_, \_, \_, | |
| 1069 1500, \_, \_, \_ ; | |
| 1070 \end{Verbatim} | |
| 1071 | |
| 1072 \item[{Emitted\_Wavelength(channels)}] \leavevmode | |
| 1073 This optional array defines the link between the channel index and | |
| 1074 the emission wavelength for each lidar channel. The wavelength has to | |
| 1075 be expressed in nm. This information can be also taken from SCC\_DB. | |
| 1076 In our example we have: | |
| 1077 | |
| 1078 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1079 \PYG{n}{Emitted\PYGZus{}Wavelength} \PYG{o}{=} \PYG{l+m+mi}{1064}\PYG{p}{,} \PYG{l+m+mi}{532}\PYG{p}{,} \PYG{l+m+mi}{532}\PYG{p}{,} \PYG{l+m+mi}{532} \PYG{p}{;} | |
| 1080 \end{Verbatim} | |
| 1081 | |
| 1082 \item[{Detected\_Wavelength(channels)}] \leavevmode | |
| 1083 This optional array defines the link between the channel index and | |
| 1084 the detected wavelength for each lidar channel. Here detected | |
| 1085 wavelength means the value of center of interferential filter | |
| 1086 expressed in nm. This information can be also taken from SCC\_DB. In | |
| 1087 our example we have: | |
| 1088 | |
| 1089 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1090 \PYG{n}{Detected\PYGZus{}Wavelength} \PYG{o}{=} \PYG{l+m+mi}{1064}\PYG{p}{,} \PYG{l+m+mi}{532}\PYG{p}{,} \PYG{l+m+mi}{532}\PYG{p}{,} \PYG{l+m+mi}{607} \PYG{p}{;} | |
| 1091 \end{Verbatim} | |
| 1092 | |
| 1093 \item[{Raw\_Data\_Range\_Resolution(channels)}] \leavevmode | |
| 1094 This optional array defines the link between the channel index and | |
| 1095 the raw range resolution for each channel. If the scan angle is | |
| 1096 different from zero this quantity is different from the vertical | |
| 1097 resolution. More precisely if $\alpha$ is the scan angle used | |
| 1098 and $\Delta z$ is the range resolution the vertical | |
| 1099 resolution is calculated as $\Delta | |
| 1100 z'=\Delta z \cos\alpha$. This array has to be filled with | |
| 1101 $\Delta z$ and not with $\Delta z'$. The unit is | |
| 1102 meters. This information can be also taken from SCC\_DB. In our | |
| 1103 example we have: | |
| 1104 | |
| 1105 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1106 \PYG{n}{Raw\PYGZus{}Data\PYGZus{}Range\PYGZus{}Resolution} \PYG{o}{=} \PYG{l+m+mf}{7.5}\PYG{p}{,} \PYG{l+m+mf}{15.0}\PYG{p}{,} \PYG{l+m+mf}{15.0}\PYG{p}{,} \PYG{l+m+mf}{15.0} \PYG{p}{;} | |
| 1107 \end{Verbatim} | |
| 1108 | |
| 1109 \item[{ID\_Range(channels)}] \leavevmode | |
| 1110 This optional array defines if a particular channel is configured as | |
| 1111 high, low or ultranear range channel. In particular a value 0 | |
| 1112 indicates a low range channel, a value 1 a high range channel and a | |
| 1113 value of 2 an ultranear range channel. If for a particular channel | |
| 1114 you don’t separate between high and low range channel, please set the | |
| 1115 corresponding value to 1. This information can be also taken from | |
| 1116 SCC\_DB. In our case we have to set: | |
| 1117 | |
| 1118 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1119 \PYG{n}{ID\PYGZus{}Range} \PYG{o}{=} \PYG{l+m+mi}{1}\PYG{p}{,} \PYG{l+m+mi}{1}\PYG{p}{,} \PYG{l+m+mi}{1}\PYG{p}{,} \PYG{l+m+mi}{1} \PYG{p}{;} | |
| 1120 \end{Verbatim} | |
| 1121 | |
| 1122 \item[{Scattering\_Mechanism(channels)}] \leavevmode | |
| 1123 This optional array defines the scattering mechanism involved in | |
| 1124 each lidar channel. In particular the following values are adopted: | |
| 1125 | |
| 1126 \begin{tabulary}{\linewidth}{|L|L|} | |
| 1127 \hline | |
| 1128 | |
| 1129 0 | |
| 1130 & | |
| 1131 $\rightarrow$ Total elastic backscatter | |
| 1132 \\\hline | |
| 1133 | |
| 1134 1 | |
| 1135 & | |
| 1136 $\rightarrow$ $N_2$ vibrational Raman backscatter | |
| 1137 \\\hline | |
| 1138 | |
| 1139 2 | |
| 1140 & | |
| 1141 $\rightarrow$ Cross polarization elastic backscatter | |
| 1142 \\\hline | |
| 1143 | |
| 1144 3 | |
| 1145 & | |
| 1146 $\rightarrow$ Parallel polarization elastic backscatter | |
| 1147 \\\hline | |
| 1148 | |
| 1149 4 | |
| 1150 & | |
| 1151 $\rightarrow$ $H_2O$ vibrational Raman backscatter | |
| 1152 \\\hline | |
| 1153 | |
| 1154 5 | |
| 1155 & | |
| 1156 $\rightarrow$ Rotational Raman Stokes line close to elastic line | |
| 1157 \\\hline | |
| 1158 | |
| 1159 6 | |
| 1160 & | |
| 1161 $\rightarrow$ Rotational Raman Stokes line far from elastic line | |
| 1162 \\\hline | |
| 1163 | |
| 1164 7 | |
| 1165 & | |
| 1166 $\rightarrow$ Rotational Raman anti-Stokes line close to elastic line | |
| 1167 \\\hline | |
| 1168 | |
| 1169 8 | |
| 1170 & | |
| 1171 $\rightarrow$ Rotational Raman anti-Stokes line far from elastic line | |
| 1172 \\\hline | |
| 1173 | |
| 1174 9 | |
| 1175 & | |
| 1176 $\rightarrow$ Rotational Raman Stokes and anti-Stokes lines close to elastic line | |
| 1177 \\\hline | |
| 1178 | |
| 1179 10 | |
| 1180 & | |
| 1181 $\rightarrow$ Rotational Raman Stokes and anti-Stokes lines far from elastic line | |
| 1182 \\\hline | |
| 1183 \end{tabulary} | |
| 1184 | |
| 1185 | |
| 1186 This information can be also taken from SCC\_DB. In our example we have: | |
| 1187 | |
| 1188 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1189 \PYG{n}{Scattering\PYGZus{}Mechanism} \PYG{o}{=} \PYG{l+m+mi}{0}\PYG{p}{,} \PYG{l+m+mi}{2}\PYG{p}{,} \PYG{l+m+mi}{3}\PYG{p}{,} \PYG{l+m+mi}{1} \PYG{p}{;} | |
| 1190 \end{Verbatim} | |
| 1191 | |
| 1192 \item[{Acquisition\_Mode(channels)}] \leavevmode | |
| 1193 This optional array defines the acquisition mode (analog or | |
| 1194 photoncounting) involved in each lidar channel. In particular a value | |
| 1195 of 0 means analog mode and 1 photoncounting mode. This information | |
| 1196 can be also taken from SCC\_DB. In our example we have: | |
| 1197 | |
| 1198 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1199 \PYG{n}{Acquisition\PYGZus{}Mode} \PYG{o}{=} \PYG{l+m+mi}{0}\PYG{p}{,} \PYG{l+m+mi}{1}\PYG{p}{,} \PYG{l+m+mi}{1}\PYG{p}{,} \PYG{l+m+mi}{1} \PYG{p}{;} | |
| 1200 \end{Verbatim} | |
| 1201 | |
| 1202 \item[{Laser\_Repetition\_Rate(channels)}] \leavevmode | |
| 1203 This optional array defines the repetition rate in Hz used to | |
| 1204 acquire each lidar channel. This information can be also taken from | |
| 1205 SCC\_DB. In our example we are supposing we have only one laser with | |
| 1206 a repetition rate of 50 Hz so we have to set: | |
| 1207 | |
| 1208 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1209 \PYG{n}{Laser\PYGZus{}Repetition\PYGZus{}Rate} \PYG{o}{=} \PYG{l+m+mi}{50}\PYG{p}{,} \PYG{l+m+mi}{50}\PYG{p}{,} \PYG{l+m+mi}{50}\PYG{p}{,} \PYG{l+m+mi}{50} \PYG{p}{;} | |
| 1210 \end{Verbatim} | |
| 1211 | |
| 1212 \item[{Dead\_Time(channels)}] \leavevmode | |
| 1213 This optional array defines the dead time in ns associated to each | |
| 1214 lidar channel. The SCC will use the values given by this array to | |
| 1215 correct the photoncounting signals for dead time. Of course for | |
| 1216 analog signals no dead time correction will be applied (for analog | |
| 1217 channels the corresponding dead time values have to be set to | |
| 1218 undefined value). This information can be also taken from SCC\_DB. In | |
| 1219 our example the 1064 nm channel is acquired in analog mode so the | |
| 1220 corresponding dead time value has to be undefined. If we suppose a | |
| 1221 dead time of 10 ns for all other channels we have to set: | |
| 1222 | |
| 1223 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1224 \PYG{n}{Dead\PYGZus{}Time} \PYG{o}{=} \PYG{n}{\PYGZus{}}\PYG{p}{,} \PYG{l+m+mi}{10}\PYG{p}{,} \PYG{l+m+mi}{10}\PYG{p}{,} \PYG{l+m+mi}{10} \PYG{p}{;} | |
| 1225 \end{Verbatim} | |
| 1226 | |
| 1227 \item[{Dead\_Time\_Corr\_Type(channels}] \leavevmode | |
| 1228 This optional array defines which kind of dead time correction has | |
| 1229 to be applied on each photoncounting channel. The SCC will correct | |
| 1230 the data supposing a not-paralyzable channel if a value of 0 is found | |
| 1231 while a paralyzable channel is supposed if a value of 1 is found. Of | |
| 1232 course for analog signals no dead time correction will be applied and | |
| 1233 so the corresponding values have to be set to undefined value. This | |
| 1234 information can be also taken from SCC\_DB. In our example the 1064 | |
| 1235 nm channel is acquired in analog mode so the corresponding has to be | |
| 1236 undefined. If we want to consider all the photoncounting signals as | |
| 1237 not-paralyzable ones: we have to set: | |
| 1238 | |
| 1239 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1240 \PYG{n}{Dead\PYGZus{}Time\PYGZus{}Corr\PYGZus{}Type} \PYG{o}{=} \PYG{n}{\PYGZus{}}\PYG{p}{,} \PYG{l+m+mi}{0}\PYG{p}{,} \PYG{l+m+mi}{0}\PYG{p}{,} \PYG{l+m+mi}{0} \PYG{p}{;} | |
| 1241 \end{Verbatim} | |
| 1242 | |
| 1243 \item[{Trigger\_Delay(channels)}] \leavevmode | |
| 1244 This optional array defines the delay (in ns) of the middle of the | |
| 1245 first rangebin with respect to the output laser pulse for each lidar | |
| 1246 channel. The SCC will use the values given by this array to correct | |
| 1247 for trigger delay. This information can be also taken from SCC\_DB. | |
| 1248 Let’s suppose that in our example all the photoncounting channels are | |
| 1249 not affected by this delay and only the analog channel at 1064nm is | |
| 1250 acquired with a delay of 50ns. In this case we have to set: | |
| 1251 | |
| 1252 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1253 \PYG{n}{Trigger\PYGZus{}Delay} \PYG{o}{=} \PYG{l+m+mi}{50}\PYG{p}{,} \PYG{l+m+mi}{0}\PYG{p}{,} \PYG{l+m+mi}{0}\PYG{p}{,} \PYG{l+m+mi}{0} \PYG{p}{;} | |
| 1254 \end{Verbatim} | |
| 1255 | |
| 1256 \item[{Background\_Mode(channels}] \leavevmode | |
| 1257 This optional array defines how the atmospheric background has to be | |
| 1258 subtracted from the lidar channel. Two options are available for the | |
| 1259 calculation of atmospheric background: | |
| 1260 \begin{enumerate} | |
| 1261 \item {} | |
| 1262 Average in the far field of lidar channel. In this case the value | |
| 1263 of this variable has to be 1 | |
| 1264 | |
| 1265 \item {} | |
| 1266 Average within pre-trigger bins. In this case the value of this | |
| 1267 variable has to be 0 | |
| 1268 | |
| 1269 \end{enumerate} | |
| 1270 | |
| 1271 This information can be also taken from SCC\_DB. Let’s suppose in our | |
| 1272 example we use the pre-trigger for the 1064nm channel and the far | |
| 1273 field for all other channels. In this case we have to set: | |
| 1274 | |
| 1275 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1276 \PYG{n}{Background\PYGZus{}Mode} \PYG{o}{=} \PYG{l+m+mi}{0}\PYG{p}{,} \PYG{l+m+mi}{1}\PYG{p}{,} \PYG{l+m+mi}{1}\PYG{p}{,} \PYG{l+m+mi}{1} \PYG{p}{;} | |
| 1277 \end{Verbatim} | |
| 1278 | |
| 1279 \item[{Background\_Low(channels)}] \leavevmode | |
| 1280 This mandatory array defines the minimum altitude (in meters) to | |
| 1281 consider in calculating the atmospheric background for each channel. | |
| 1282 In case pre-trigger mode is used the corresponding value has to be | |
| 1283 set to the rangebin to be used as lower limit (within pre-trigger | |
| 1284 region) for background calculation. In our example, if we want to | |
| 1285 calculate the background between 30000 and 50000 meters for all | |
| 1286 photoncounting channels and we want to use the first 500 pre-trigger | |
| 1287 bins for the background calculation for the 1064nm channel we have to | |
| 1288 set: | |
| 1289 | |
| 1290 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1291 \PYG{n}{Background\PYGZus{}Low}\PYG{o}{=} \PYG{l+m+mi}{0}\PYG{p}{,} \PYG{l+m+mi}{30000}\PYG{p}{,} \PYG{l+m+mi}{30000}\PYG{p}{,} \PYG{l+m+mi}{30000} \PYG{p}{;} | |
| 1292 \end{Verbatim} | |
| 1293 | |
| 1294 \item[{Background\_High(channels)}] \leavevmode | |
| 1295 This mandatory array defines the maximum altitude (in meters) to | |
| 1296 consider in calculating the atmospheric background for each channel. | |
| 1297 In case pre-trigger mode is used the corresponding value has to be | |
| 1298 set to the rangebin to be used as upper limit (within pre-trigger | |
| 1299 region) for background calculation. In our example, if we want to | |
| 1300 calculate the background between 30000 and 50000 meters for all | |
| 1301 photoncounting channels and we want to use the first 500 pre-trigger | |
| 1302 bins for the background calculation for the 1064nm channel we have to | |
| 1303 set: | |
| 1304 | |
| 1305 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1306 \PYG{n}{Background\PYGZus{}High} \PYG{o}{=} \PYG{l+m+mi}{500}\PYG{p}{,} \PYG{l+m+mi}{50000}\PYG{p}{,} \PYG{l+m+mi}{50000}\PYG{p}{,} \PYG{l+m+mi}{50000} \PYG{p}{;} | |
| 1307 \end{Verbatim} | |
| 1308 | |
| 1309 \item[{Molecular\_Calc}] \leavevmode | |
| 1310 This mandatory variable defines the way used by SCC to calculate the | |
| 1311 molecular density profile. At the moment two options are available: | |
| 1312 \begin{enumerate} | |
| 1313 \item {} | |
| 1314 US Standard Atmosphere 1976. In this case the value of this | |
| 1315 variable has to be 0 | |
| 1316 | |
| 1317 \item {} | |
| 1318 Radiosounding. In this case the value of this variable has to be 1 | |
| 1319 | |
| 1320 \end{enumerate} | |
| 1321 | |
| 1322 If we decide to use the option 1. we have to provide also the | |
| 1323 measured pressure and temperature at lidar station level. Indeed if | |
| 1324 we decide to use the option 2. a radiosounding file has to be | |
| 1325 submitted separately in NetCDF format (the structure of this file is | |
| 1326 summarized in table tab:sounding). Let’s suppose we want to use the | |
| 1327 option 1. so: | |
| 1328 | |
| 1329 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1330 \PYG{n}{Molecular\PYGZus{}Calc} \PYG{o}{=} \PYG{l+m+mi}{0} \PYG{p}{;} | |
| 1331 \end{Verbatim} | |
| 1332 | |
| 1333 \item[{Pressure\_at\_Lidar\_Station}] \leavevmode | |
| 1334 Because we have chosen the US Standard Atmosphere for calculation of | |
| 1335 the molecular density profile we have to give the pressure in hPa at | |
| 1336 lidar station level: | |
| 1337 | |
| 1338 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1339 \PYG{n}{Pressure\PYGZus{}at\PYGZus{}Lidar\PYGZus{}Station} \PYG{o}{=} \PYG{l+m+mi}{1010} \PYG{p}{;} | |
| 1340 \end{Verbatim} | |
| 1341 | |
| 1342 \item[{Temperature\_at\_Lidar\_Station}] \leavevmode | |
| 1343 Because we have chosen the US Standard Atmosphere for calculation of | |
| 1344 the molecular density profile we have to give the temperature in C at | |
| 1345 lidar station level: | |
| 1346 | |
| 1347 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1348 \PYG{n}{Temperature\PYGZus{}at\PYGZus{}Lidar\PYGZus{}Station} \PYG{o}{=} \PYG{l+m+mf}{19.8} \PYG{p}{;} | |
| 1349 \end{Verbatim} | |
| 1350 | |
| 1351 \item[{Depolarization\_Factor(channels)}] \leavevmode | |
| 1352 This array is required only for lidar systems that use the two | |
| 1353 depolarization channels for the backscatter retrieval. It represents | |
| 1354 the factor $f$ to calculate the total backscatter signal | |
| 1355 $S_t$ combining its cross $S_c$ and parallel | |
| 1356 $S_p$ components: $S_t=S_p+fS_c$. This factor is | |
| 1357 mandatory only for systems acquiring $S_c$ and $S_p$ | |
| 1358 and not $S_t$. For systems acquiring $S_c$, | |
| 1359 $S_p$ and $S_t$ this factor is optional and it will | |
| 1360 be used only for depolarizaton ratio calculation. Moreover only the | |
| 1361 values of the array corresponding to cross polarization channels will | |
| 1362 be considered; all other values will be not taken into account and | |
| 1363 should be set to undefined value. In our example for the wavelength | |
| 1364 532nm we have only the cross and the parallel components and not the | |
| 1365 total one. So we have to give the value of this factor only in | |
| 1366 correspondence of the 532nm cross polarization channel that | |
| 1367 corresponds to the channel index 1. Suppose that this factor is 0.88. | |
| 1368 Moreover, because we don’t have any other depolarization channels we | |
| 1369 have also to set all other values of the array to undefined value. | |
| 1370 | |
| 1371 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1372 \PYG{n}{Depolarization\PYGZus{}Factor} \PYG{o}{=} \PYG{n}{\PYGZus{}}\PYG{p}{,}\PYG{l+m+mf}{0.88}\PYG{p}{,}\PYG{n}{\PYGZus{}}\PYG{p}{,}\PYG{n}{\PYGZus{}} \PYG{p}{;} | |
| 1373 \end{Verbatim} | |
| 1374 | |
| 1375 \item[{LR\_Input(channels)}] \leavevmode | |
| 1376 This array is required only for lidar channels for which elastic | |
| 1377 backscatter retrieval has to be performed. It defines the lidar ratio | |
| 1378 to be used within this retrieval. Two options are available: | |
| 1379 \begin{enumerate} | |
| 1380 \item {} | |
| 1381 The user can submit a lidar ratio profile. In this case the value | |
| 1382 of this variable has to be 0. | |
| 1383 | |
| 1384 \item {} | |
| 1385 A fixed value of lidar ratio can be used. In this case the value | |
| 1386 of this variable has to be 1. | |
| 1387 | |
| 1388 \end{enumerate} | |
| 1389 | |
| 1390 If we decide to use the option 1. a lidar ratio file has to be | |
| 1391 submitted separately in NetCDF format (the structure of this file is | |
| 1392 summarized in table tab:lr). If we decide to use the option 2. the | |
| 1393 fixed value of lidar ratio will be taken from SCC\_DB. In our example | |
| 1394 we have to give a value of this array only for the 1064nm lidar | |
| 1395 channel because for the 532nm we will be able to retrieve a Raman | |
| 1396 backscatter coefficient. In case we want to use the fixed value | |
| 1397 stored in SCC\_DB we have to set: | |
| 1398 | |
| 1399 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1400 \PYG{n}{LR\PYGZus{}Input} \PYG{o}{=} \PYG{l+m+mi}{1}\PYG{p}{,}\PYG{n}{\PYGZus{}}\PYG{p}{,}\PYG{n}{\PYGZus{}}\PYG{p}{,}\PYG{n}{\PYGZus{}} \PYG{p}{;} | |
| 1401 \end{Verbatim} | |
| 1402 | |
| 1403 \item[{DAQ\_Range(channels)}] \leavevmode | |
| 1404 This array is required only if one or more lidar signals are | |
| 1405 acquired in analog mode. It gives the analog scale in mV used to | |
| 1406 acquire the analog signals. In our example we have only the 1064nm | |
| 1407 channel acquired in analog mode. If we have used a 100mV analog scale | |
| 1408 to acquire this channel we have to set: | |
| 1409 | |
| 1410 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1411 \PYG{n}{DAQ\PYGZus{}Range} \PYG{o}{=} \PYG{l+m+mi}{100}\PYG{p}{,}\PYG{n}{\PYGZus{}}\PYG{p}{,}\PYG{n}{\PYGZus{}}\PYG{p}{,}\PYG{n}{\PYGZus{}} \PYG{p}{;} | |
| 1412 \end{Verbatim} | |
| 1413 | |
| 1414 \end{description} | |
| 1415 | |
| 1416 | |
| 1417 \subsection{Global attributes} | |
| 1418 \label{netcdf_file:global-attributes}\begin{description} | |
| 1419 \item[{Measurement\_ID}] \leavevmode | |
| 1420 This mandatory global attribute defines the measurement ID | |
| 1421 corresponding to the actual lidar measurement. It is a string | |
| 1422 composed by 12 characters. The first 8 characters give the start date | |
| 1423 of measurement in the format YYYYMMDD. The next 2 characters give the | |
| 1424 Earlinet call-sign of the station. The last 2 characters are used to | |
| 1425 distinguish between different time-series within the same date. In | |
| 1426 our example we have to set: | |
| 1427 | |
| 1428 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1429 \PYG{n}{Measurement\PYGZus{}ID}\PYG{o}{=} \PYG{l+s}{"}\PYG{l+s}{20090130cc00}\PYG{l+s}{"} \PYG{p}{;} | |
| 1430 \end{Verbatim} | |
| 1431 | |
| 1432 \item[{RawData\_Start\_Date}] \leavevmode | |
| 1433 This mandatory global attribute defines the start date of lidar | |
| 1434 measurements in the format YYYYMMDD. In our case we have: | |
| 1435 | |
| 1436 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1437 \PYG{n}{RawData\PYGZus{}Start\PYGZus{}Date} \PYG{o}{=} \PYG{l+s}{"}\PYG{l+s}{20090130}\PYG{l+s}{"} \PYG{p}{;} | |
| 1438 \end{Verbatim} | |
| 1439 | |
| 1440 \item[{RawData\_Start\_Time\_UT}] \leavevmode | |
| 1441 This mandatory global attribute defines the UT start time of lidar | |
| 1442 measurements in the format HHMMSS. In our case we have: | |
| 1443 | |
| 1444 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1445 \PYG{n}{RawData\PYGZus{}Start\PYGZus{}Time\PYGZus{}UT} \PYG{o}{=} \PYG{l+s}{"}\PYG{l+s}{000001}\PYG{l+s}{"} \PYG{p}{;} | |
| 1446 \end{Verbatim} | |
| 1447 | |
| 1448 \item[{RawData\_Stop\_Time\_UT{}`{}`}] \leavevmode | |
| 1449 This mandatory global attribute defines the UT stop time of lidar | |
| 1450 measurements in the format HHMMSS. In our case we have: | |
| 1451 | |
| 1452 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1453 \PYG{n}{RawData\PYGZus{}Stop\PYGZus{}Time\PYGZus{}UT} \PYG{o}{=} \PYG{l+s}{"}\PYG{l+s}{000501}\PYG{l+s}{"} \PYG{p}{;} | |
| 1454 \end{Verbatim} | |
| 1455 | |
| 1456 \item[{RawBck\_Start\_Date}] \leavevmode | |
| 1457 This optional global attribute defines the start date of dark | |
| 1458 measurements in the format YYYYMMDD. In our case we have: | |
| 1459 | |
| 1460 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1461 \PYG{n}{RawBck\PYGZus{}Start\PYGZus{}Date} \PYG{o}{=} \PYG{l+s}{"}\PYG{l+s}{20090129}\PYG{l+s}{"} \PYG{p}{;} | |
| 1462 \end{Verbatim} | |
| 1463 | |
| 1464 \item[{RawBck\_Start\_Time\_UT}] \leavevmode | |
| 1465 This optional global attribute defines the UT start time of dark | |
| 1466 measurements in the format HHMMSS. In our case we have: | |
| 1467 | |
| 1468 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1469 \PYG{n}{RawBck\PYGZus{}Start\PYGZus{}Time\PYGZus{}UT} \PYG{o}{=} \PYG{l+s}{"}\PYG{l+s}{235001}\PYG{l+s}{"} \PYG{p}{;} | |
| 1470 \end{Verbatim} | |
| 1471 | |
| 1472 \item[{RawBck\_Stop\_Time\_UT}] \leavevmode | |
| 1473 This optional global attribute defines the UT stop time of dark | |
| 1474 measurements in the format HHMMSS. In our case we have: | |
| 1475 | |
| 1476 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1477 \PYG{n}{RawBck\PYGZus{}Stop\PYGZus{}Time\PYGZus{}UT} \PYG{o}{=} \PYG{l+s}{"}\PYG{l+s}{235301}\PYG{l+s}{"} \PYG{p}{;} | |
| 1478 \end{Verbatim} | |
| 1479 | |
| 1480 \end{description} | |
| 1481 | |
| 1482 | |
| 1483 \section{Example of file (CDL format)} | |
| 1484 \label{netcdf_file:example-of-file-cdl-format} | |
| 1485 To summarize we have the following NetCDF Raw Lidar Data file (in CDL | |
| 1486 format): | |
| 1487 | |
| 1488 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1489 dimensions: | |
| 1490 points = 5000 ; | |
| 1491 channels = 4 ; | |
| 1492 time = UNLIMITED ; // (10 currently) | |
| 1493 nb\_of\_time\_scales = 2 ; | |
| 1494 scan\_angles = 1 ; | |
| 1495 time\_bck = 6 ; | |
| 1496 variables: | |
| 1497 int channel\_ID(channels) ; | |
| 1498 int Laser\_Repetition\_Rate(channels) ; | |
| 1499 double Laser\_Pointing\_Angle(scan\_angles) ; | |
| 1500 int ID\_Range(channels) ; | |
| 1501 int Scattering\_Mechanism(channels) ; | |
| 1502 double Emitted\_Wavelength(channels) ; | |
| 1503 double Detected\_Wavelength(channels) ; | |
| 1504 double Raw\_Data\_Range\_Resolution(channels) ; | |
| 1505 int Background\_Mode(channels) ; | |
| 1506 double Background\_Low(channels) ; | |
| 1507 double Background\_High(channels) ; | |
| 1508 int Molecular\_Calc ; | |
| 1509 double Pressure\_at\_Lidar\_Station ; | |
| 1510 double Temperature\_at\_Lidar\_Station ; | |
| 1511 int id\_timescale(channels) ; | |
| 1512 double Dead\_Time(channels) ; | |
| 1513 int Dead\_Time\_Corr\_Type(channels) ; | |
| 1514 int Acquisition\_Mode(channels) ; | |
| 1515 double Trigger\_Delay(channels) ; | |
| 1516 int LR\_Input(channels) ; | |
| 1517 int Laser\_Pointing\_Angle\_of\_Profiles(time, nb\_of\_time\_scales) ; | |
| 1518 int Raw\_Data\_Start\_Time(time, nb\_of\_time\_scales) ; | |
| 1519 int Raw\_Data\_Stop\_Time(time, nb\_of\_time\_scales) ; | |
| 1520 int Raw\_Bck\_Start\_Time(time\_bck, nb\_of\_time\_scales) ; | |
| 1521 int Raw\_Bck\_Stop\_Time(time\_bck, nb\_of\_time\_scales) ; | |
| 1522 int Laser\_Shots(time, channels) ; | |
| 1523 double Raw\_Lidar\_Data(time, channels, points) ; | |
| 1524 double Background\_Profile(time\_bck, channels, points) ; | |
| 1525 double DAQ\_Range(channels) ; | |
| 1526 | |
| 1527 // global attributes: | |
| 1528 :Measurement\_ID = "20090130cc00" ; | |
| 1529 :RawData\_Start\_Date = "20090130" ; | |
| 1530 :RawData\_Start\_Time\_UT = "000001" ; | |
| 1531 :RawData\_Stop\_Time\_UT = "000501" ; | |
| 1532 :RawBck\_Start\_Date = "20090129" ; | |
| 1533 :RawBck\_Start\_Time\_UT = "235001" ; | |
| 1534 :RawBck\_Stop\_Time\_UT = "235301" ; | |
| 1535 | |
| 1536 data: | |
| 1537 | |
| 1538 channel\_ID = 7, 5, 6, 8 ; | |
| 1539 | |
| 1540 Laser\_Repetition\_Rate = 50, 50, 50, 50 ; | |
| 1541 | |
| 1542 Laser\_Pointing\_Angle = 5 ; | |
| 1543 | |
| 1544 ID\_Range = 1, 1, 1, 1 ; | |
| 1545 | |
| 1546 Scattering\_Mechanism = 0, 2, 3, 1 ; | |
| 1547 | |
| 1548 Emitted\_Wavelength = 1064, 532, 532, 532 ; | |
| 1549 | |
| 1550 Detected\_Wavelength = 1064, 532, 532, 607 ; | |
| 1551 | |
| 1552 Raw\_Data\_Range\_Resolution = 7.5, 15, 15, 15 ; | |
| 1553 | |
| 1554 Background\_Mode = 0, 1, 1, 1 ; | |
| 1555 | |
| 1556 Background\_Low = 0, 30000, 30000, 30000 ; | |
| 1557 | |
| 1558 Background\_High = 500, 50000, 50000, 50000 ; | |
| 1559 | |
| 1560 Molecular\_Calc = 0 ; | |
| 1561 | |
| 1562 Pressure\_at\_Lidar\_Station = 1010 ; | |
| 1563 | |
| 1564 Temperature\_at\_Lidar\_Station = 19.8 ; | |
| 1565 | |
| 1566 id\_timescale = 1, 0, 0, 0 ; | |
| 1567 | |
| 1568 Dead\_Time = \_, 10, 10, 10 ; | |
| 1569 | |
| 1570 Dead\_Time\_Corr\_Type = \_, 0, 0, 0 ; | |
| 1571 | |
| 1572 Acquisition\_Mode = 0, 1, 1, 1 ; | |
| 1573 | |
| 1574 Trigger\_Delay = 50, 0, 0, 0 ; | |
| 1575 | |
| 1576 LR\_Input = 1,\_,\_,\_ ; | |
| 1577 | |
| 1578 DAQ\_Range = 100,\_,\_,\_ ; | |
| 1579 | |
| 1580 Laser\_Pointing\_Angle\_of\_Profiles = | |
| 1581 0, 0, | |
| 1582 0, 0, | |
| 1583 0, 0, | |
| 1584 0, 0, | |
| 1585 0, 0, | |
| 1586 \_, 0, | |
| 1587 \_, 0, | |
| 1588 \_, 0, | |
| 1589 \_, 0, | |
| 1590 \_, 0 ; | |
| 1591 | |
| 1592 | |
| 1593 Raw\_Data\_Start\_Time = | |
| 1594 0, 0, | |
| 1595 60, 30, | |
| 1596 120, 60, | |
| 1597 180, 90, | |
| 1598 240, 120, | |
| 1599 \_, 150, | |
| 1600 \_, 180, | |
| 1601 \_, 210, | |
| 1602 \_, 240, | |
| 1603 \_, 270 ; | |
| 1604 | |
| 1605 Raw\_Data\_Stop\_Time = | |
| 1606 60, 30, | |
| 1607 120, 60, | |
| 1608 180, 90, | |
| 1609 240, 120, | |
| 1610 300, 150, | |
| 1611 \_, 180, | |
| 1612 \_, 210, | |
| 1613 \_, 240, | |
| 1614 \_, 270, | |
| 1615 \_, 300 ; | |
| 1616 | |
| 1617 | |
| 1618 Raw\_Bck\_Start\_Time = | |
| 1619 0, 0, | |
| 1620 60, 30, | |
| 1621 120, 60, | |
| 1622 \_, 90, | |
| 1623 \_, 120, | |
| 1624 \_, 150; | |
| 1625 | |
| 1626 | |
| 1627 Raw\_Bck\_Stop\_Time = | |
| 1628 60, 30, | |
| 1629 120, 60, | |
| 1630 180, 90, | |
| 1631 \_, 120, | |
| 1632 \_, 150, | |
| 1633 \_, 180 ; | |
| 1634 | |
| 1635 | |
| 1636 Laser\_Shots = | |
| 1637 1500, 3000, 3000, 3000, | |
| 1638 1500, 3000, 3000, 3000, | |
| 1639 1500, 3000, 3000, 3000, | |
| 1640 1500, 3000, 3000, 3000, | |
| 1641 1500, 3000, 3000, 3000, | |
| 1642 1500, \_, \_, \_, | |
| 1643 1500, \_, \_, \_, | |
| 1644 1500, \_, \_, \_, | |
| 1645 1500, \_, \_, \_, | |
| 1646 1500, \_, \_, \_ ; | |
| 1647 | |
| 1648 | |
| 1649 Raw\_Lidar\_Data = ... | |
| 1650 | |
| 1651 Background\_Profile = ... | |
| 1652 \end{Verbatim} | |
| 1653 | |
| 1654 Please keep in mind that in case you submit a file like the previous one | |
| 1655 all the parameters present in it will be used by the SCC even if you | |
| 1656 have different values for the same parameters within the SCC\_DB. If you | |
| 1657 want to use the values already stored in SCC\_DB (this should be the | |
| 1658 usual way to use SCC) the Raw Lidar Data input file has to be | |
| 1659 modified as follows: | |
| 1660 | |
| 1661 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1662 dimensions: | |
| 1663 points = 5000 ; | |
| 1664 channels = 4 ; | |
| 1665 time = UNLIMITED ; // (10 currently) | |
| 1666 nb\_of\_time\_scales = 2 ; | |
| 1667 scan\_angles = 1 ; | |
| 1668 time\_bck = 6 ; | |
| 1669 variables: | |
| 1670 int channel\_ID(channels) ; | |
| 1671 double Laser\_Pointing\_Angle(scan\_angles) ; | |
| 1672 double Background\_Low(channels) ; | |
| 1673 double Background\_High(channels) ; | |
| 1674 int Molecular\_Calc ; | |
| 1675 double Pressure\_at\_Lidar\_Station ; | |
| 1676 double Temperature\_at\_Lidar\_Station ; | |
| 1677 int id\_timescale(channels) ; | |
| 1678 int Laser\_Pointing\_Angle\_of\_Profiles(time, nb\_of\_time\_scales) ; | |
| 1679 int Raw\_Data\_Start\_Time(time, nb\_of\_time\_scales) ; | |
| 1680 int Raw\_Data\_Stop\_Time(time, nb\_of\_time\_scales) ; | |
| 1681 int Raw\_Bck\_Start\_Time(time\_bck, nb\_of\_time\_scales) ; | |
| 1682 int Raw\_Bck\_Stop\_Time(time\_bck, nb\_of\_time\_scales) ; | |
| 1683 int LR\_Input(channels) ; | |
| 1684 int Laser\_Shots(time, channels) ; | |
| 1685 double Raw\_Lidar\_Data(time, channels, points) ; | |
| 1686 double Background\_Profile(time\_bck, channels, points) ; | |
| 1687 double DAQ\_Range(channels) ; | |
| 1688 | |
| 1689 // global attributes: | |
| 1690 :Measurement\_ID = "20090130cc00" ; | |
| 1691 :RawData\_Start\_Date = "20090130" ; | |
| 1692 :RawData\_Start\_Time\_UT = "000001" ; | |
| 1693 :RawData\_Stop\_Time\_UT = "000501" ; | |
| 1694 :RawBck\_Start\_Date = "20090129" ; | |
| 1695 :RawBck\_Start\_Time\_UT = "235001" ; | |
| 1696 :RawBck\_Stop\_Time\_UT = "235301" ; | |
| 1697 | |
| 1698 data: | |
| 1699 | |
| 1700 channel\_ID = 7, 5, 6, 8 ; | |
| 1701 | |
| 1702 Laser\_Pointing\_Angle = 5 ; | |
| 1703 | |
| 1704 Background\_Low = 0, 30000, 30000, 30000 ; | |
| 1705 | |
| 1706 Background\_High = 500, 50000, 50000, 50000 ; | |
| 1707 | |
| 1708 Molecular\_Calc = 0 ; | |
| 1709 | |
| 1710 Pressure\_at\_Lidar\_Station = 1010 ; | |
| 1711 | |
| 1712 Temperature\_at\_Lidar\_Station = 19.8 ; | |
| 1713 | |
| 1714 id\_timescale = 1, 0, 0, 0 ; | |
| 1715 | |
| 1716 LR\_Input = 1,\_,\_,\_ ; | |
| 1717 | |
| 1718 DAQ\_Range = 100,\_,\_,\_ ; | |
| 1719 | |
| 1720 Laser\_Pointing\_Angle\_of\_Profiles = | |
| 1721 0, 0, | |
| 1722 0, 0, | |
| 1723 0, 0, | |
| 1724 0, 0, | |
| 1725 0, 0, | |
| 1726 \_, 0, | |
| 1727 \_, 0, | |
| 1728 \_, 0, | |
| 1729 \_, 0, | |
| 1730 \_, 0 ; | |
| 1731 | |
| 1732 | |
| 1733 Raw\_Data\_Start\_Time = | |
| 1734 0, 0, | |
| 1735 60, 30, | |
| 1736 120, 60, | |
| 1737 180, 90, | |
| 1738 240, 120, | |
| 1739 \_, 150, | |
| 1740 \_, 180, | |
| 1741 \_, 210, | |
| 1742 \_, 240, | |
| 1743 \_, 270 ; | |
| 1744 | |
| 1745 Raw\_Data\_Stop\_Time = | |
| 1746 60, 30, | |
| 1747 120, 60, | |
| 1748 180, 90, | |
| 1749 240, 120, | |
| 1750 300, 150, | |
| 1751 \_, 180, | |
| 1752 \_, 210, | |
| 1753 \_, 240, | |
| 1754 \_, 270, | |
| 1755 \_, 300 ; | |
| 1756 | |
| 1757 | |
| 1758 Raw\_Bck\_Start\_Time = | |
| 1759 0, 0, | |
| 1760 60, 30, | |
| 1761 120, 60, | |
| 1762 \_, 90, | |
| 1763 \_, 120, | |
| 1764 \_, 150; | |
| 1765 | |
| 1766 | |
| 1767 Raw\_Bck\_Stop\_Time = | |
| 1768 60, 30, | |
| 1769 120, 60, | |
| 1770 180, 90, | |
| 1771 \_, 120, | |
| 1772 \_, 150, | |
| 1773 \_, 180 ; | |
| 1774 | |
| 1775 | |
| 1776 Laser\_Shots = | |
| 1777 1500, 3000, 3000, 3000, | |
| 1778 1500, 3000, 3000, 3000, | |
| 1779 1500, 3000, 3000, 3000, | |
| 1780 1500, 3000, 3000, 3000, | |
| 1781 1500, 3000, 3000, 3000, | |
| 1782 1500, \_, \_, \_, | |
| 1783 1500, \_, \_, \_, | |
| 1784 1500, \_, \_, \_, | |
| 1785 1500, \_, \_, \_, | |
| 1786 1500, \_, \_, \_ ; | |
| 1787 | |
| 1788 | |
| 1789 Raw\_Lidar\_Data = ... | |
| 1790 | |
| 1791 Background\_Profile = ... | |
| 1792 \end{Verbatim} | |
| 1793 | |
| 1794 This example file contains the minimum collection of mandatory | |
| 1795 information that has to be found within the Raw Lidar Data input | |
| 1796 file. If it is really necessary, the user can decide to add to these | |
| 1797 mandatory parameters any number of additional parameters considered in | |
| 1798 the previous example. | |
| 1799 | |
| 1800 Finally, suppose we want to make the following changes with respect to | |
| 1801 the previous example: | |
| 1802 \begin{enumerate} | |
| 1803 \item {} | |
| 1804 use a sounding file for molecular density calculation instead of “US | |
| 1805 Standar Atmosphere 1976” | |
| 1806 | |
| 1807 \item {} | |
| 1808 supply a lidar ratio profile to use in elastic backscatter retrieval | |
| 1809 instead of a fixed value | |
| 1810 | |
| 1811 \item {} | |
| 1812 provide a overlap function for overlap correction | |
| 1813 | |
| 1814 \end{enumerate} | |
| 1815 | |
| 1816 In this case we have to generate the following NetCDF additional files: | |
| 1817 \begin{description} | |
| 1818 \item[{rs\_20090130cc00.nc}] \leavevmode | |
| 1819 The name of Sounding Data file has to be computed as follows: | |
| 1820 \code{"rs\_"{}`{}`+{}`{}`Measurement\_ID} | |
| 1821 The structure of this file is summarized in table tab:sounding. | |
| 1822 | |
| 1823 \item[{ov\_20090130cc00.nc}] \leavevmode | |
| 1824 The name of Overlap file has to be computed as follows: | |
| 1825 \code{"ov\_"{}`{}`+{}`{}`Measurement\_ID} | |
| 1826 The structure of this file is summarized in table tab:overlap. | |
| 1827 | |
| 1828 \item[{lr\_20090130cc00.nc}] \leavevmode | |
| 1829 The name of Lidar Ratio file has to be computed as follows: | |
| 1830 \code{"lr\_"{}`{}`+{}`{}`Measurement\_ID} | |
| 1831 The structure of this file is summarized in table tab:lr. | |
| 1832 | |
| 1833 \end{description} | |
| 1834 | |
| 1835 Moreover we need to apply the following changes to the Raw Lidar Data | |
| 1836 input file: | |
| 1837 \begin{enumerate} | |
| 1838 \item {} | |
| 1839 Change the value of the variable \code{Molecular\_Calc} as follows: | |
| 1840 | |
| 1841 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1842 \PYG{n}{Molecular\PYGZus{}Calc} \PYG{o}{=} \PYG{l+m+mi}{1} \PYG{p}{;} | |
| 1843 \end{Verbatim} | |
| 1844 | |
| 1845 Of course the variables \code{Pressure\_at\_Lidar\_Station} and | |
| 1846 \code{Temperature\_at\_Lidar\_Station} are not necessary anymore. | |
| 1847 | |
| 1848 \item {} | |
| 1849 Change the values of the array \code{LR\_Input} as follows: | |
| 1850 | |
| 1851 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1852 \PYG{n}{LR\PYGZus{}Input} \PYG{o}{=} \PYG{l+m+mi}{0}\PYG{p}{,}\PYG{n}{\PYGZus{}}\PYG{p}{,}\PYG{n}{\PYGZus{}}\PYG{p}{,}\PYG{n}{\PYGZus{}} \PYG{p}{;} | |
| 1853 \end{Verbatim} | |
| 1854 | |
| 1855 \item {} | |
| 1856 Add the global attribute \code{Sounding\_File\_Name} | |
| 1857 | |
| 1858 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1859 \PYG{n}{Sounding\PYGZus{}File\PYGZus{}Name} \PYG{o}{=} \PYG{l+s}{"}\PYG{l+s}{rs\PYGZus{}20090130cc00.nc}\PYG{l+s}{"} \PYG{p}{;} | |
| 1860 \end{Verbatim} | |
| 1861 | |
| 1862 \end{enumerate} | |
| 1863 \begin{enumerate} | |
| 1864 \setcounter{enumi}{4} | |
| 1865 \item {} | |
| 1866 Add the global attribute \code{LR\_File\_Name} | |
| 1867 | |
| 1868 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1869 \PYG{n}{LR\PYGZus{}File\PYGZus{}Name} \PYG{o}{=} \PYG{l+s}{"}\PYG{l+s}{lr\PYGZus{}20090130cc00.nc}\PYG{l+s}{"} \PYG{p}{;} | |
| 1870 \end{Verbatim} | |
| 1871 | |
| 1872 \item {} | |
| 1873 Add the global attribute \code{Overlap\_File\_Name} | |
| 1874 | |
| 1875 \begin{Verbatim}[commandchars=\\\{\}] | |
| 1876 \PYG{n}{Overlap\PYGZus{}File\PYGZus{}Name} \PYG{o}{=} \PYG{l+s}{"}\PYG{l+s}{ov\PYGZus{}20090130cc00.nc}\PYG{l+s}{"} \PYG{p}{;} | |
| 1877 \end{Verbatim} | |
| 1878 | |
| 1879 \end{enumerate} | |
| 1880 | |
| 1881 | |
| 1882 \chapter{User management} | |
| 1883 \label{user_management:user-management}\label{user_management::doc}\label{user_management:id1} | |
| 1884 | |
| 1885 \section{Acount types} | |
| 1886 \label{user_management:acount-types} | |
| 1887 | |
| 1888 \section{Requesting a new account} | |
| 1889 \label{user_management:requesting-a-new-account} | |
| 1890 | |
| 1891 \section{User account security} | |
| 1892 \label{user_management:user-account-security} | |
| 1893 | |
| 1894 \chapter{Indices and tables} | |
| 1895 \label{index:indices-and-tables}\begin{itemize} | |
| 1896 \item {} | |
| 1897 \emph{genindex} | |
| 1898 | |
| 1899 \item {} | |
| 1900 \emph{modindex} | |
| 1901 | |
| 1902 \item {} | |
| 1903 \emph{search} | |
| 1904 | |
| 1905 \end{itemize} | |
| 1906 | |
| 1907 | |
| 1908 | |
| 1909 \renewcommand{\indexname}{Index} | |
| 1910 \printindex | |
| 1911 \end{document} |
