Mercurial > public > sccdocs / file comparison

comparison: docs/depolarization/depolarization.rst

docs/depolarization/depolarization.rst

changeset 70
31295554bf20
parent 68
f697817dad5f
child 71
26d9dac079e9
equal deleted inserted replaced
69:380d41368260 70:31295554bf20
1 .. role:: underline
2 :class: underline
3
4 .. role:: red
5
6
7
1 1. Particle Linear Depolarization Ratio Implementation 8 1. Particle Linear Depolarization Ratio Implementation
2 ====================================================== 9 ======================================================
3 10
4 The most important improvement included in the SCC v4.0 is the implementation of a new optical product which is the particle linear depolarization ratio. 11 The most important improvement included in the SCC v4.0 is the implementation of a new optical product which is the particle linear depolarization ratio.
5 12
25 #. *Elastic backscatter and linear depolarization ratio 32 #. *Elastic backscatter and linear depolarization ratio
26 (product\_type\_id=8).* 33 (product\_type\_id=8).*
27 34
28 The first product in the above list is used only for calibration while the other two are used for the calculation of *PLDR*. Basically, in most of the cases, the products 2 and 3 are equivalent to the corresponding backscatter product types with the exception that also the following new variables are available: 35 The first product in the above list is used only for calibration while the other two are used for the calculation of *PLDR*. Basically, in most of the cases, the products 2 and 3 are equivalent to the corresponding backscatter product types with the exception that also the following new variables are available:
29 36
30 .. code-block:: python 37 ::
31 38
32 double VolumeDepol(Length) ; 39 double VolumeDepol(Length) ;
33 double ErrorVolumeDepol(Length) ; 40 double ErrorVolumeDepol(Length) ;
34 ErrorVolumeDepol:long\_name = "absolute error of VolumeDepol" ; 41 ErrorVolumeDepol:long\_name = "absolute error of VolumeDepol" ;
35 double ParticleDepol(Length) ; 42 double ParticleDepol(Length) ;
50 For what it concerns the method c) it, basically, requires to solve the equation: 57 For what it concerns the method c) it, basically, requires to solve the equation:
51 58
52 .. math:: 59 .. math::
53 \alpha_s P_s + \alpha_p P_p = P 60 \alpha_s P_s + \alpha_p P_p = P
54 61
55 in two different of atmospheric layers with considerably different *VLDR*. So to calibrate in this way the implementation of automatic layer identification in the SCC is required. As at moment this feature is not yet available within the SCC *ONLY* the method b) is considered. 62 in two different of atmospheric layers with considerably different *VLDR*. So to calibrate in this way the implementation of automatic layer identification in the SCC is required. As at moment this feature is not yet available within the SCC :underline:`ONLY` the method b) is considered.
56 63
57 1.3 SCC procedure to calculate the PLDRP 64 1.3 SCC procedure to calculate the PLDRP
58 ---------------------------------------- 65 ----------------------------------------
59 66
60 According to what mentioned before the SCC calculates the *PLDR* through the following steps: 67 According to what mentioned before the SCC calculates the *PLDR* through the following steps:
61 68
62 #. The user needs to create a new system configuration in the SCC\_DB including only lidar channels used for the calibration. One (or more) *Linear polarization calibration (product\_type\_id=6)* product should be associated to this new configuration (see section 3.2 for more details); 69 #. The user needs to create a new system configuration in the SCC\_DB including only lidar channels used for the calibration. One (or more) *Linear polarization calibration (product\_type\_id=6)* product should be associated to this new configuration (see section 3.2 for more details);
63 70
64 #. This new system configuration should contain only the polarization channels in the configuration used for the calibration (for example rotated in the polarization plane of +45 degrees). A channel in calibration measurement configuration should have a *DIFFERENT* channel ID from the channel ID corresponding to the same channel in standard measurement configuration. For example, if a system has two polarization channels which in standard measurement configuration correspond to the channel ID=1 and 2 respectively, the same physical channels under calibration measurement configuration should correspond to different channel IDs (let's say ID=3 and 4 for the +45 degrees polarization rotated channels and ID=5 and 6 for the -45 degrees polarization rotated ones in case D90 calibration method is used). Moreover, the polarization channels should be labeled correctly using the new signal types available (*+45elPT, +45elPR, -45elPT, -45elPR, +45elPTnr, +45elPTfr, +45elPRnr, +45elPRfr, -45elPTnr, -45elPTfr, -45elPRnr, -45elPRfr).* For more details see section 3.2; 71 #. This new system configuration should contain only the polarization channels in the configuration used for the calibration (for example rotated in the polarization plane of +45 degrees). A channel in calibration measurement configuration should have a :underline:`DIFFERENT` channel ID from the channel ID corresponding to the same channel in standard measurement configuration. For example, if a system has two polarization channels which in standard measurement configuration correspond to the channel ID=1 and 2 respectively, the same physical channels under calibration measurement configuration should correspond to different channel IDs (let's say ID=3 and 4 for the +45 degrees polarization rotated channels and ID=5 and 6 for the -45 degrees polarization rotated ones in case D90 calibration method is used). Moreover, the polarization channels should be labeled correctly using the new signal types available (*+45elPT, +45elPR, -45elPT, -45elPR, +45elPTnr, +45elPTfr, +45elPRnr, +45elPRfr, -45elPTnr, -45elPTfr, -45elPRnr, -45elPRfr).* For more details see section 3.2;
65 72
66 #. In SCC v4.0 the polarization channels are *NOT* labeled on the base of their polarization state (as it was done in the SCC v3.11) but *ALWAYS* as transmitted and reflected channels. So the channels that in SCC v3.11 were labeled as *elCP, elCPnr, elCPfr, elPP, elPPnr elPPfr* will be labeled in SCC v4.0 as *elPR, elPRnr elPRfr elPT, elPTnr elPTfr* where the letter *T* stands from transmitted and the letter *R* for reflected. 73 #. In SCC v4.0 the polarization channels are :underline:`NOT` labeled on the base of their polarization state (as it was done in the SCC v3.11) but :underline:`ALWAYS` as transmitted and reflected channels. So the channels that in SCC v3.11 were labeled as *elCP, elCPnr, elCPfr, elPP, elPPnr elPPfr* will be labeled in SCC v4.0 as *elPR, elPRnr elPRfr elPT, elPTnr elPTfr* where the letter *T* stands from transmitted and the letter *R* for reflected.
67 74
68 :WARNING: In switching from the SCC v3.11 to SCC v4.0 the following modifications have been made on *ALL* channels of *ALL* registered configurations: 75 :WARNING: In switching from the SCC v3.11 to SCC v4.0 the following modifications have been made on :underline:`ALL` channels of :underline:`ALL` registered configurations:
69 *elPP→elPR* 76 *elPP→elPR*
70 77
71 *elCP→elPT* 78 *elCP→elPT*
72 79
73 *elPPnr→elPRnr* 80 *elPPnr→elPRnr*
165 | parallel | 1 | 1 | 1 | 1 | 172 | parallel | 1 | 1 | 1 | 1 |
166 +----------------------+-----------------------------+-----------------+-----------------+-----------------+ 173 +----------------------+-----------------------------+-----------------+-----------------+-----------------+
167 | cross | 1 | -1 | 1 | -1 | 174 | cross | 1 | -1 | 1 | -1 |
168 +----------------------+-----------------------------+-----------------+-----------------+-----------------+ 175 +----------------------+-----------------------------+-----------------+-----------------+-----------------+
169 176
170 The *apparent calibration factor (:math:`\eta^*`), *the calibration factor correction* (*K*) and the *polarization cross-talk correction parameters* are stored by **ELPP** module in the intermediate NetCDF files using the following variables: 177 The *apparent calibration factor* (:math:`\eta^*`), *the calibration factor correction* (*K*) and the *polarization cross-talk correction parameters* are stored by **ELPP** module in the intermediate NetCDF files using the following variables:
171
172 testing the inline code :code:`test`
173 178
174 - :code:`Polarization_Channel_Gain_Factor` (*apparent calibration factor* - :math:`\eta^*` ) 179 - :code:`Polarization_Channel_Gain_Factor` (*apparent calibration factor* - :math:`\eta^*` )
175 - :code:`Polarization_Channel_Gain_Factor_Correction` (*calib. factor corr.* – *K*) 180 - :code:`Polarization_Channel_Gain_Factor_Correction` (*calib. factor corr.* – *K*)
176 - :code:`G_T` 181 - :code:`G_T`
177 - :code:`H_T` 182 - :code:`H_T`
183 2. Changes of the SCC input format 188 2. Changes of the SCC input format
184 ================================== 189 ==================================
185 190
186 The following minor changes have been applied to raw SCC data format: 191 The following minor changes have been applied to raw SCC data format:
187 192
188 #. The optional variable *ID\_Range* has been *REMOVED*; 193 #. The optional variable *ID\_Range* has been :underline:`REMOVED`;
189 #. The *OPTIONAL* variable :code:`int Signal\_Type(channels)` has been added. The possible values are the same available in the SCC\_DB: 194 #. The :underline:`OPTIONAL` variable :code:`int Signal\_Type(channels)` has been added. The possible values are the same available in the SCC\_DB:
190 195
191 :code:`0` :math:`\rightarrow` :code:`elT` 196 :code:`0` :math:`\rightarrow` :code:`elT`
192 197
193 :code:`1` :math:`\rightarrow` :code:`elTnr` 198 :code:`1` :math:`\rightarrow` :code:`elTnr`
194 199
254 259
255 :code:`32` :math:`\rightarrow` :code:`-45elPRnr` 260 :code:`32` :math:`\rightarrow` :code:`-45elPRnr`
256 261
257 :code:`33` :math:`\rightarrow` :code:`-45elPRfr` 262 :code:`33` :math:`\rightarrow` :code:`-45elPRfr`
258 263
259 :WARNING: It this variable is found in the SCC input file the corresponding settings in the SCC database will be *overwritten*. Unless you don't have any valid reason to overwrite the database value this variable should not be used. 264 :WARNING: It this variable is found in the SCC input file the corresponding settings in the SCC database will be :underline:`OVERWRITTEN`. Unless you don't have any valid reason to overwrite the database value this variable should not be used.
260 265
261 3. The variables: 266 3. The variables:
262 267
263 .. code-block:: python 268 ::
264 269
265 double Pol\_Calib\_Range\_Min(channels) 270 double Pol\_Calib\_Range\_Min(channels)
266 double Pol\_Calib\_Range\_Max(channels) 271 double Pol\_Calib\_Range\_Max(channels)
267 272
268 have been added. Both these variable are *MANDATORY* for any calibration raw dataset. These variable should be included only the polarization calibration measurements and should specify the altitude range (meters) in which the polarization calibration should be made. For more details see section 3.3; 273 have been added. Both these variable are :underline:`MANDATORY` for any calibration raw dataset. These variable should be included only the polarization calibration measurements and should specify the altitude range (meters) in which the polarization calibration should be made. For more details see section 3.3;
269 274
270 4. The variable :code:`Depolarization_Factor` has been *REMOVED*. 275 4. The variable :code:`Depolarization_Factor` has been :underline:`REMOVED`.
271 276
272 The SCC v3.11 used this variable to get polarization calibration factor for the calculation of the total signal out of cross and parallels ones. As the SCC v4.0 is able to calculate the same parameter by itself, the use of this variable is *NOT* possible anymore. The recommended way to get a valid and quality assured depolarization calibration factor is to submit to the SCC v4.0 a polarization calibration dataset and let the SCC to calculate such factor. 277 The SCC v3.11 used this variable to get polarization calibration factor for the calculation of the total signal out of cross and parallels ones. As the SCC v4.0 is able to calculate the same parameter by itself, the use of this variable is *NOT* possible anymore. The recommended way to get a valid and quality assured depolarization calibration factor is to submit to the SCC v4.0 a polarization calibration dataset and let the SCC to calculate such factor.
273 278
274 To make this change more smooth and to provide the users with the possibility to continue to analyze their data with the SCC v4.0 even if a calibration dataset has not been submitted yet, it will be possible for a *LIMITED* period of time to submit the calibration constant via the SCC web interface. The SCC will keep track of the used calibration method (automatic or manual). 279 To make this change more smooth and to provide the users with the possibility to continue to analyze their data with the SCC v4.0 even if a calibration dataset has not been submitted yet, it will be possible for a :underline:`LIMITED` period of time to submit the calibration constant via the SCC web interface. The SCC will keep track of the used calibration method (automatic or manual).
275 280
276 :WARNING: After this transition period *ONLY* automatic calibration will be allowed! 281 :WARNING: After this transition period :underline:`ONLY` automatic calibration will be allowed!
277 282
278 5. The new *OPTIONAL* variable: 283 5. The new :underline:`OPTIONAL` variable:
279 284
280 :code:`string channel\_string\_ID(channels)` 285 :code:`string channel\_string\_ID(channels)`
281 286
282 has been introduced. 287 has been introduced.
283 288
285 290
286 The procedure implemented in the SCC v4.0 to recognize the lidar channel within the raw lidar data is fully backward compatible (old format files are accepted as they are by SCC v4.0). 291 The procedure implemented in the SCC v4.0 to recognize the lidar channel within the raw lidar data is fully backward compatible (old format files are accepted as they are by SCC v4.0).
287 292
288 :WARNING: Please note that the definition of the new string variable requires netCDF-4 format! The type *string* is not supported in netCDF-3 format! 293 :WARNING: Please note that the definition of the new string variable requires netCDF-4 format! The type *string* is not supported in netCDF-3 format!
289 294
290 Real Example 295 3. Real Example
291 ============ 296 ===============
292 297
293 This section describes all the practical steps the users need to follow 298 This section describes all the practical steps the users need to follow to switch from SCC v3.11 to new SCC v4.0.
294 to switch from SCC v3.11 to new SCC v4.0. 299
295 300 :IMPORTANT:
296 **IMPORTANT:** 301 If your lidar system is not equipped with any polarization channels :underline:`NO` changes are required. In this case, the SCC v4.0 should work using the same input files and the same database configurations you have used with the SCC v3.11. Anyway as in the SCC v4.0 several bugs have been fixed,it is recommended to re-run all the measurement IDs you have submitted. For doing that you just need to reprocess all your data without the need to submit raw data files already uploaded on the server.
297 302
298 If your lidar system is not equipped with any polarization channels *NO* 303 The practical example reported below describes the modifications required to use the SCC v4.0 for lidar systems equipped with polarization channels.
299 changes are required. In this case, the SCC v4.0 should work using the 304
300 same input files and the same database configurations you have used with 305 3.1 Modification of polarization channel parameters
301 the SCC v3.11. Anyway as in the SCC v4.0 several bugs have been fixed, 306 ---------------------------------------------------
302 it is recommended to re-run all the measurement IDs you have submitted. 307
303 For doing that you just need to reprocess all your data without the need 308 In what it follows it is assumed you already have registered one or more lidar configurations in the SCC database and that such configurations have been already used to produce optical products (aerosol extinction and/or backscatter coefficients) by means of the SCC v3.11.
304 to submit raw data files already uploaded on the server. 309
305 310 Let's assume your 3+2 system is registered in the SCC database and the settings used by the SCC v3.11 are the ones summarized in table 3.1.
306 The practical example reported below describes the modifications 311
307 required to use the SCC v4.0 for lidar systems equipped with 312 :Table 3.1: Example of configuration in SCC v3.11
308 polarization channels.
309
310 Modification of polarization channel parameters
311 -----------------------------------------------
312
313 In what it follows it is assumed you already have registered one or more
314 lidar configurations in the SCC database and that such configurations
315 have been already used to produce optical products (aerosol extinction
316 and/or backscatter coefficients) by means of the SCC v3.11.
317
318 Let's assume your 3+2 system is registered in the SCC database and the
319 settings used by the SCC v3.11 are the ones summarized in table 3.1.
320
321 **Table 3.1:** Example of configuration in SCC v3.11
322 313
323 +----------------+--------------+----------------+-------------+-----------+ 314 +----------------+--------------+----------------+-------------+-----------+
324 | Channel Name | Channel ID | Channel Type | nighttime | daytime | 315 | Channel Name | Channel ID | Channel Type | nighttime | daytime |
325 +----------------+--------------+----------------+-------------+-----------+ 316 +----------------+--------------+----------------+-------------+-----------+
326 | 355 | 1 | elT |  |  | 317 | 355 | 1 | elT | x | x |
327 +----------------+--------------+----------------+-------------+-----------+ 318 +----------------+--------------+----------------+-------------+-----------+
328 | 387 | 2 | vrRN2 |  | | 319 | 387 | 2 | vrRN2 | x | |
329 +----------------+--------------+----------------+-------------+-----------+ 320 +----------------+--------------+----------------+-------------+-----------+
330 | 532 cross | 3 | elCP |  |  | 321 | 532 cross | 3 | elCP | x | x |
331 +----------------+--------------+----------------+-------------+-----------+ 322 +----------------+--------------+----------------+-------------+-----------+
332 | 532 parallel | 4 | elPP |  |  | 323 | 532 parallel | 4 | elPP | x | x |
333 +----------------+--------------+----------------+-------------+-----------+ 324 +----------------+--------------+----------------+-------------+-----------+
334 | 607 | 5 | vrRN2 |  | | 325 | 607 | 5 | vrRN2 | x | |
335 +----------------+--------------+----------------+-------------+-----------+ 326 +----------------+--------------+----------------+-------------+-----------+
336 | 1064 | 6 | elT |  |  | 327 | 1064 | 6 | elT | x | x |
337 +----------------+--------------+----------------+-------------+-----------+ 328 +----------------+--------------+----------------+-------------+-----------+
338 329
339 We assume there are 2 system configurations called “nighttime” and 330 We assume there are 2 system configurations called “nighttime” and “daytime”. The nighttime configuration contains all the available lidar channels (in order to calculate, for example, the aerosol extinction at 355 and 532nm and the aerosol backscatter at 355, 532 and 1064nm) while in daytime conditions only elastic channels are used (only elastic backscatter coefficients are generated).
340 “daytime”. The nighttime configuration contains all the available lidar 331
341 channels (in order to calculate, for example, the aerosol extinction at 332 To make these settings working with SCC v4.0 it is needed to modify :underline:ONLY` the products properties involving the polarization channels (532 cross and parallel). All the products not involving the polarization channels :underline:`DO NOT` need any modification and should work in the SCC v4.0 exactly as they did in SCC v3.11. In the example above the aerosol extinction and backscatter coefficient at 355nm, the extinction at 532nm as well as the backscatter coefficient at 1064nm do not required any
342 355 and 532nm and the aerosol backscatter at 355, 532 and 1064nm) while 333 modification. Let's focus on the modifications needed for the calculation of backscatter at 532nm.
343 in daytime conditions only elastic channels are used (only elastic 334
344 backscatter coefficients are generated). 335 .. figure:: figure3.1.png
345 336 :height: 369
346 To make these settings working with SCC v4.0 it is needed to modify 337 :width: 1037
347 *ONLY* the products properties involving the polarization channels (532 338 :scale: 100 %
348 cross and parallel). All the products not involving the polarization 339 :align: center
349 channels *DO NOT* need any modification and should work in the SCC v4.0 340
350 exactly as they did in SCC v3.11. In the example above the aerosol 341 **Figure 3.1**: How to select signal types
351 extinction and backscatter coefficient at 355nm, the extinction at 532nm 342
352 as well as the backscatter coefficient at 1064nm do not required any 343 The first modification concerns the settings of the channel type for the 532 cross and 532 parallel polarization channels. Starting from SCC v4.0 polarization channels are identified as transmitted and reflected polarization channels and not on the base of their polarization state. So suppose if we suppose the cross polarized channel is transmitted by a polarizer beam splitter cube and the parallel is reflected the value reported in table 3.1 should be modified as they appear in table 3.2. So using the SCC web interface, the signal type of the 532 cross channel should be changed from :code:`elCP` to :code:`elPT` and in the same way the 532 parallel channel should be changed from :code:`elPP` to :code:`elPR` (see figure 3.1).
353 modification. Let's focus on the modifications needed for the
354 calculation of backscatter at 532nm.
355
356 |image0| How to select signal types
357
358 The first modification concerns the settings of the channel type for the
359 532 cross and 532 parallel polarization channels. Starting from SCC v4.0
360 polarization channels are identified as transmitted and reflected
361 polarization channels and not on the base of their polarization state.
362 So suppose if we suppose the cross polarized channel is transmitted by a
363 polarizer beam splitter cube and the parallel is reflected the value
364 reported in table 3.1 should be modified as they appear in table 3.2. So
365 using the SCC web interface, the signal type of the 532 cross channel
366 should be changed from elCP to elPT and and in the same way the 532
367 parallel channel should be changed from elPP to elPR (see figure 3.1).
368 344
369 **Table 3.2:** The same of table 3.1 but with new channel types 345 **Table 3.2:** The same of table 3.1 but with new channel types
370 introduced in SCC v4.0 346 introduced in SCC v4.0
371 347
372 +----------------+--------------+----------------+-------------+-----------+ 348 +----------------+--------------+----------------+-------------+-----------+
373 | Channel Name | Channel ID | Channel Type | nighttime | daytime | 349 | Channel Name | Channel ID | Channel Type | nighttime | daytime |
374 +----------------+--------------+----------------+-------------+-----------+ 350 +----------------+--------------+----------------+-------------+-----------+
375 | 355 | 1 | elT |  |  | 351 | 355 | 1 | elT | x | x |
376 +----------------+--------------+----------------+-------------+-----------+ 352 +----------------+--------------+----------------+-------------+-----------+
377 | 387 | 2 | vrRN2 |  | | 353 | 387 | 2 | vrRN2 | x | |
378 +----------------+--------------+----------------+-------------+-----------+ 354 +----------------+--------------+----------------+-------------+-----------+
379 | 532 cross | 3 | **elPT** |  |  | 355 | 532 cross | 3 | :red:`elPT` | x | x |
380 +----------------+--------------+----------------+-------------+-----------+ 356 +----------------+--------------+----------------+-------------+-----------+
381 | 532 parallel | 4 | **elPR** |  |  | 357 | 532 parallel | 4 | :red:`elPR` | x | x |
382 +----------------+--------------+----------------+-------------+-----------+ 358 +----------------+--------------+----------------+-------------+-----------+
383 | 607 | 5 | vrRN2 |  | | 359 | 607 | 5 | vrRN2 | x | |
384 +----------------+--------------+----------------+-------------+-----------+ 360 +----------------+--------------+----------------+-------------+-----------+
385 | 1064 | 6 | elT |  |  | 361 | 1064 | 6 | elT | x | x |
386 +----------------+--------------+----------------+-------------+-----------+ 362 +----------------+--------------+----------------+-------------+-----------+
387 363
388 The other change about the polarization channels required to run the SCC 364 The other change about the polarization channels required to run the SCC v4.0 is the definition of the polarization crosstalk parameters for all the polarization channels available. Such parameters can be defined for each polarization channel using the SCC web interface (see figure 3.2). In particular among the channel parameters there is a new tab called *Polarization crosstalk parameters* where it is possible to insert the values from for the parameters *G* and *H* and the corresponding statistical and systematic errors if available. In case you have measured *G* and *H* for your polarization channels please insert the corresponding values there. Otherwise you can insert the ideal values as reported in table 1.1.
389 v4.0 is the definition of the polarization crosstalk parameters for all 365
390 the polarization channels available. Such parameters can be defined for 366 .. figure:: figure3.2.png
391 each polarization channel using the SCC web interface (see figure 3.2). 367 :height: 479
392 In particular among the channel parameters there is a new tab called 368 :width: 1890
393 *Polarization crosstalk parameters* where it is possible to insert the 369 :scale: 100 %
394 values from for the parameters *G* and *H* and the corresponding 370 :align: center
395 statistical and systematic errors if available. In case you have 371
396 measured *G* and *H* for your polarization channels please insert the 372 **Figure 3.2:** Polarization crosstalk parameters tab in channel properties (SCC v4.0).
397 corresponding values there. Otherwise you can insert the ideal values as 373
398 reported in table 1.1. 374 3.2 Definition of new calibration configuration and product
399 375 -----------------------------------------------------------
400 |image1| *Polarization crosstalk parameters* tab in channel properties 376
401 (SCC v4.0). 377 In this section we will see how to set the polarization calibration parameters: the calibration constant (called :math:`\eta^*`*` in section 1.3) and the correction to calibration constant (called K in section 1.3). In order to provide such parameters you need to define a new system configuration to be used :underline:`ONLY` for calibration purposes. Such new configuration should include the polarization channels in the measurement configuration used for the calibration. Let's suppose we want to use the :math:`\Delta90` calibration method.
402 378
403 Definition of new calibration configuration and product 379 In this case we need to define a new configuration (called for example “depol_calibration”) as reported in the table 3.3. As you can see the configuration “depol\_calibration” includes 4 “new” channels. Actually the channels “532 cross +45 degrees” (channel ID=10) and “532 cross -45 degrees” (channel ID=12) refer to the same physical channel “532 cross” reported with channel ID=3 in table 3.2. Anyway we need to define two new channel IDs to identify the “532 cross” channel in the two polarization rotated configurations (+45 and -45 degrees) needed to apply the D90 calibration method. The same is true for the “532 parallel” channel. The polarization rotated channels should be labeled with the corresponding signal type as reported in table 3.3 (see figure
404 -------------------------------------------------------
405
406 In this section we will see how to set the polarization calibration
407 parameters: the calibration constant (called h\ :sup:`\*` in section
408 1.3) and the correction to calibration constant (called K in section
409 1.3).
410
411 In order to provide such parameters you need to define a new system
412 configuration to be used *only* for calibration purposes. Such new
413 configuration should include the polarization channels in the
414 measurement configuration used for the calibration. Let's suppose we
415 want to use the D90 calibration method.
416
417 In this case we need to define a new configuration (called for example
418 “depol\_calibration”) as reported in the table 3.3. As you can see the
419 configuration “depol\_calibration” includes 4 “new” channels. Actually
420 the channels “532 cross +45 degrees” (channel ID=10) and “532 cross -45
421 degrees” (channel ID=12) refer to the same physical channel “532 cross”
422 reported with channel ID=3 in table 3.2. Anyway we need to define two
423 new channel IDs to identify the “532 cross” channel in the two
424 polarization rotated configurations (+45 and -45 degrees) needed to
425 apply the D90 calibration method. The same is true for the “532
426 parallel” channel. The polarization rotated channels should be labeled
427 with the corresponding signal type as reported in table 3.3 (see figure
428 3.1). 380 3.1).
429 381
430 **Table 3.3:** Polarization calibration configurations assuming D90 382 **Table 3.3:** Polarization calibration configurations assuming D90
431 calibration method 383 calibration method
432 384
433 +----------------------------+--------------+----------------+----------------------+ 385 +----------------------------+--------------+----------------+----------------------+
434 | Channel Name | Channel ID | Channel Type | depol\_calibration | 386 | Channel Name | Channel ID | Channel Type | depol_calibration |
435 +----------------------------+--------------+----------------+----------------------+ 387 +----------------------------+--------------+----------------+----------------------+
436 | 532 cross +45 degrees | 10 | +45elPT |  | 388 | 532 cross +45 degrees | 10 | +45elPT | x |
437 +----------------------------+--------------+----------------+----------------------+ 389 +----------------------------+--------------+----------------+----------------------+
438 | 532 parallel +45 degrees | 11 | +45elPR |  | 390 | 532 parallel +45 degrees | 11 | +45elPR | x |
439 +----------------------------+--------------+----------------+----------------------+ 391 +----------------------------+--------------+----------------+----------------------+
440 | 532 cross -45 degrees | 12 | -45elPT |  | 392 | 532 cross -45 degrees | 12 | -45elPT | x |
441 +----------------------------+--------------+----------------+----------------------+ 393 +----------------------------+--------------+----------------+----------------------+
442 | 532 parallel -45 degrees | 13 | -45elPR |  | 394 | 532 parallel -45 degrees | 13 | -45elPR | x |
443 +----------------------------+--------------+----------------+----------------------+ 395 +----------------------------+--------------+----------------+----------------------+
444 396
445 Finally we should add to the configuration “depol\_calibration” a 397 Finally we should add to the configuration “depol_calibration” a product “*Linear polarization calibration”* to be used for the calibration. According to the example given above and to the usecase document attached we should use an usecase=4 for this example.
446 product “\ *Linear polarization calibration”* to be used for the 398
447 calibration. According to the example given above and to the usecase 399 Other “*Linear polarization calibration”* options to be specified are reported in figure 3.3. The most important factor you should insert here is the *Pol calibration correction factor* (K). The ideal value for this parameter is 1. Anyway if you have measured the parameter K please fill in the measured value and the corresponding measurement errors.
448 document attached we should use an usecase=4 for this example. 400
449 401 .. figure:: figure3.3.png
450 Other “\ *Linear polarization calibration”* options to be specified are 402 :height: 495
451 reported in figure 3.3. The most important factor you should insert here 403 :width: 1887
452 is the *Pol calibration correction factor* (K). The ideal value for this 404 :scale: 100 %
453 parameter is 1. Anyway if you have measured the parameter K please fill 405 :align: center
454 in the measured value and the corresponding measurement errors. 406
455 407 **Figure 3.3:** Options for *Linear polarization calibration product*.
456 |image2| Options for *Linear polarization calibration product*. 408
457 409 As you can see it is possible to fill in only the K correction factor and not the calibration constant :math:`\eta^*`.
458 As you can see it is possible to fill in only the K correction factor 410
459 and not the calibration constant h\ :sup:`\*`. 411 Actually for a :underline:`LIMITED` period of time it will be possible to fill in also the constant :math:`\eta^*` using a temporary tab called *Polarization calibration constant*. This has been done to provide the users with the possibility to continue to use the SCC even if an automatic calibration made by the SCC was not submitted yet. Anyway after a transition period it will be :underline:`NOT` possible to provide calibration constant using this procedure and the parameter :math:`\eta^*` can be calculated :underline:`ONLY` by the SCC as result of the submission of a proper calibration raw input dataset. The format of this input file is the same as the standard SCC input file. The only difference is that is should contain calibration measurements instead of standard measurements. Following our example, such file should contain the measurement performed at +45 and -45 degrees at 532nm. Also the channel IDs in the file should reflect the ones reported in table 3.3.
460
461 Actually for a *LIMITED* period of time it will be possible to fill in
462 also the constant h\ :sup:`\*` using a temporary tab called
463 *Polarization calibration constant*. This has been done to provide the
464 users with the possibility to continue to use the SCC even if an
465 automatic calibration made by the SCC was not submitted yet. Anyway
466 after a transition period it will be *not* possible to provide
467 calibration constant using this procedure and the parameter h\ :sup:`\*`
468 can be calculated *ONLY* by the SCC as result of the submission of a
469 proper calibration raw input dataset. The format of this input file is
470 the same as the standard SCC input file. The only difference is that is
471 should contain calibration measurements instead of standard
472 measurements. Following our example, such file should contain the
473 measurement performed at +45 and -45 degrees at 532nm. Also the channel
474 IDs in the file should reflect the ones reported in table 3.3.
475 412
476 Moreover this raw input file has to contain the variables: 413 Moreover this raw input file has to contain the variables:
477 414 ::
478 *double Pol\_Calib\_Range\_Min(channels)* 415
479 416 double Pol_Calib_Range_Min(channels)
480 *double Pol\_Calib\_Range\_Max(channels) * 417 double Pol_Calib\_Range_Max(channels)
481 418
482 where to specify the altitude ranges in meters in which the polarization 419 where to specify the altitude ranges in meters in which the polarization calibration should be done.
483 calibration should be done.
484 420
485 According to the table 3.3 this file should be something similar to: 421 According to the table 3.3 this file should be something similar to:
486 422 ::
487 dimensions: 423
488 424 dimensions:
489 channels = 4 ; 425 channels = 4 ;
490 426 nb\_of\_time\_scales = 1 ;
491 nb\_of\_time\_scales = 1 ; 427 points = 16380 ;
492 428 scan\_angles = 1 ;
493 points = 16380 ; 429 time = UNLIMITED ; // (3 currently)
494 430 variables:
495 scan\_angles = 1 ; 431 int channel\_ID(channels) ;
496 432 double Background\_Low(channels) ;
497 time = UNLIMITED ; // (3 currently) 433 double Background\_High(channels) ;
498 434 int id\_timescale(channels) ;
499 variables: 435 double Laser\_Pointing\_Angle(scan\_angles) ;
500 436 int Molecular\_Calc ;
501 int channel\_ID(channels) ; 437 int Laser\_Pointing\_Angle\_of\_Profiles(time, nb\_of\_time\_scales) ;
502 438 int Raw\_Data\_Start\_Time(time, nb\_of\_time\_scales) ;
503 double Background\_Low(channels) ; 439 int Raw\_Data\_Stop\_Time(time, nb\_of\_time\_scales) ;
504 440 int Laser\_Shots(time, channels) ;
505 double Background\_High(channels) ; 441 double Raw\_Lidar\_Data(time, channels, points) ;
506 442 double Pressure\_at\_Lidar\_Station ;
507 int id\_timescale(channels) ; 443 double Temperature\_at\_Lidar\_Station ;
508 444 double Pol\_Calib\_Range\_Min(channels) ;
509 double Laser\_Pointing\_Angle(scan\_angles) ; 445 double Pol\_Calib\_Range\_Max(channels) ;
510 446
511 int Molecular\_Calc ; 447 // global attributes:
512 448 :System = "mysystem" ;
513 int Laser\_Pointing\_Angle\_of\_Profiles(time, nb\_of\_time\_scales) ; 449 :Longitude\_degrees\_east = 15.723771 ;
514 450 :RawData\_Start\_Time\_UT = "220000" ;
515 int Raw\_Data\_Start\_Time(time, nb\_of\_time\_scales) ; 451 :RawData\_Start\_Date = "20130620" ;
516 452 :Measurement\_ID = "20130620po00" ;
517 int Raw\_Data\_Stop\_Time(time, nb\_of\_time\_scales) ; 453 :Altitude\_meter\_asl = 760. ;
518 454 :RawData\_Stop\_Time\_UT = "230333" ;
519 int Laser\_Shots(time, channels) ; 455 :Latitude\_degrees\_north = 40.601039 ;
520 456
521 double Raw\_Lidar\_Data(time, channels, points) ; 457 data:
522 458 channel\_ID = 10, 11, 12, 13 ;
523 double Pressure\_at\_Lidar\_Station ; 459
524 460 Background\_Low = 30000, 30000, 30000, 30000 ;
525 double Temperature\_at\_Lidar\_Station ; 461
526 462 Background\_High = 50000, 50000, 50000, 50000 ;
527 double Pol\_Calib\_Range\_Min(channels) ; 463
528 464 id\_timescale = 0, 0, 0, 0 ;
529 double Pol\_Calib\_Range\_Max(channels) ; 465
530 466 Laser\_Pointing\_Angle = 0 ;
531 // global attributes: 467
532 468 Molecular\_Calc = 0 ;
533 :System = "mysystem" ; 469
534 470 Laser\_Pointing\_Angle\_of\_Profiles =
535 :Longitude\_degrees\_east = 15.723771 ; 471 0,
536 472 0,
537 :RawData\_Start\_Time\_UT = "220000" ; 473 0 ;
538 474
539 :RawData\_Start\_Date = "20130620" ; 475 Raw\_Data\_Start\_Time =
540 476 0,
541 :Measurement\_ID = "20130620po00" ; 477 300,
542 478 600 ;
543 :Altitude\_meter\_asl = 760. ; 479
544 480 Raw\_Data\_Stop\_Time =
545 :RawData\_Stop\_Time\_UT = "230333" ; 481 210,
546 482 510,
547 :Latitude\_degrees\_north = 40.601039 ; 483 810 ;
548 484
549 data: 485 Laser\_Shots =
550 486 1200, 1200, 1200, 1200,
551 channel\_ID = 10, 11, 12, 13 ; 487 1200, 1200, 1200, 1200,
552 488 1200, 1200, 1200, 1200 ;
553 Background\_Low = 30000, 30000, 30000, 30000 ; 489
554 490 Pressure\_at\_Lidar\_Station = 1010 ;
555 Background\_High = 50000, 50000, 50000, 50000 ; 491
556 492 Temperature\_at\_Lidar\_Station = 14 ;
557 id\_timescale = 0, 0, 0, 0 ; 493
558 494 Pol\_Calib\_Range\_Min = 1000, 1000, 1000, 1000 ;
559 Laser\_Pointing\_Angle = 0 ; 495
560 496 Pol\_Calib\_Range\_Min = 2000, 2000, 2000, 2000 ;
561 Molecular\_Calc = 0 ; 497
562 498 Raw\_Lidar\_Data = …...;
563 Laser\_Pointing\_Angle\_of\_Profiles = 499
564 500 The file above assume the following calibration measurements have been done:
565 0, 501
566 502 1. First +45 degrees acquisition followed by a corresponding -45 degrees acquisition
567 0, 503
568 504 a. Measurement at +45 degrees
569 0 ; 505
570 506 Start Time: 20130620 22:00:00
571 Raw\_Data\_Start\_Time = 507
572 508 Stop Time: 20130620 22:01:00
573 0, 509
574 510 Shots: 1200
575 300, 511
576 512 b. Measurement at -45 degrees
577 600 ; 513
578 514 Start Time: 20130620 22:02:30
579 Raw\_Data\_Stop\_Time = 515
580 516 Stop Time: 20130620 22:03:30
581 210, 517
582 518 Shots: 1200
583 510, 519
584 520 2. Second +45 degrees acquisition followed by a corresponding -45 degrees acquisition
585 810 ; 521
586 522 a. Measurement at +45 degrees
587 Laser\_Shots = 523
588 524 Start Time: 20130620 22:05:00
589 1200, 1200, 1200, 1200, 525
590 526 Stop Time: 20130620 22:06:00
591 1200, 1200, 1200, 1200, 527
592 528 Shots: 1200
593 1200, 1200, 1200, 1200 ; 529
594 530 b. Measurement at -45 degrees
595 Pressure\_at\_Lidar\_Station = 1010 ; 531
596 532 Start Time: 20130620 22:07:30
597 Temperature\_at\_Lidar\_Station = 14 ; 533
598 534 Stop Time: 20130620 22:08:30
599 Pol\_Calib\_Range\_Min = 1000, 1000, 1000, 1000 ; 535
600 536 Shots: 1200
601 Pol\_Calib\_Range\_Min = 2000, 2000, 2000, 2000 ; 537
602 538 3. Third +45 degrees acquisition followed by a corresponding -45 degrees acquisition
603 Raw\_Lidar\_Data = …...; 539
604 540 a. Measurement at +45 degrees
605 The file above assume the following calibration measurements have been 541
606 done: 542 Start Time: 20130620 22:10:00
607 543
608 1. First +45 degrees acquisition followed by a corresponding -45 degrees 544 Stop Time: 20130620 22:11:00
609 acquisition 545
610 546 Shots: 1200
611 a. Measurement at +45 degrees 547
612 548 b. Measurement at -45 degrees
613 Start Time: 20130620 22:00:00 549
614 550 Start Time: 20130620 22:12:30
615 Stop Time: 20130620 22:01:00 551
616 552 Stop Time: 20130620 22:13:30
617 Shots: 1200 553
618 554 Shots: 1200
619 a. Measurement at -45 degrees 555
620 556 As you can see there are 3 cycles of consecutive measurements at +45 and -45 degrees. That way the dimension :code:`time` is set to 3.
621 Start Time: 20130620 22:02:30 557
622 558 The first +/-45 degrees measurement starts at “20130620 22:00:00” (start time of the first +45 measurement) and stops at “20130620 22:03:30” (stop time of the fist -45 measurement). As a consequence, according to the values of the global attributes :code:`RawData\_Start\_Date` and :code:`RawData_Start_Time_UT` we have to set:
623 Stop Time: 20130620 22:03:30 559
624 560 :code:`Raw_Data_Start_Time[0]=0` (start of the first +45 measurement in
625 Shots: 1200 561 seconds since :code:`RawData_Start_Time\_UT`)
626 562
627 1. Second +45 degrees acquisition followed by a corresponding -45 563 :code:`Raw_Data_Stop_Time[0]=210` (stop of the first -45 measurement in
628 degrees acquisition 564 seconds since :code:`RawData_Start_Time_UT`)
629
630 a. Measurement at +45 degrees
631
632 Start Time: 20130620 22:05:00
633
634 Stop Time: 20130620 22:06:00
635
636 Shots: 1200
637
638 a. Measurement at -45 degrees
639
640 Start Time: 20130620 22:07:30
641
642 Stop Time: 20130620 22:08:30
643
644 Shots: 1200
645
646 1. Third +45 degrees acquisition followed by a corresponding -45 degrees
647 acquisition
648
649 a. Measurement at +45 degrees
650
651 Start Time: 20130620 22:10:00
652
653 Stop Time: 20130620 22:11:00
654
655 Shots: 1200
656
657 a. Measurement at -45 degrees
658
659 Start Time: 20130620 22:12:30
660
661 Stop Time: 20130620 22:13:30
662
663 Shots: 1200
664
665 As you can see there are 3 cycles of consecutive measurements at +45 and
666 -45 degrees. That's way the dimension time is set to 3.
667
668 The first +/-45 degrees measurement starts at “20130620 22:00:00” (start
669 time of the first +45 measurement) and stops at “20130620 22:03:30”
670 (stop time of the fist -45 measurement). As a consequence, according to
671 the values of the global attributes RawData\_Start\_Date and
672 RawData\_Start\_Time\_UT we have to set:
673
674 Raw\_Data\_Start\_Time[0]=0 (start of the first +45 measurement in
675 seconds since RawData\_Start\_Time\_UT)
676
677 Raw\_Data\_Stop\_Time[0]=210 (stop of the first -45 measurement in
678 seconds since RawData\_Start\_Time\_UT)
679 565
680 Following a similar procedure for the other 2 cycles we have: 566 Following a similar procedure for the other 2 cycles we have:
681 567
682 Raw\_Data\_Start\_Time[1]=300 (start of the second +45 measurement in 568 :code:`Raw_Data_Start_Time[1]=300` (start of the second +45 measurement in seconds since :code:`RawData_Start_Time_UT`)
683 seconds since RawData\_Start\_Time\_UT) 569
684 570 :code:`Raw_Data_Stop_Time[1]=510` (stop of the second -45 measurement in seconds since :code:`RawData_Start_Time\_UT`)
685 Raw\_Data\_Stop\_Time[1]=510 (stop of the second -45 measurement in 571
686 seconds since RawData\_Start\_Time\_UT) 572 :code:`Raw_Data_Start_Time[2]=600` (start of the third +45 measurement in seconds since :code:`RawData_Start_Time_UT`)
687 573
688 Raw\_Data\_Start\_Time[2]=600 (start of the third +45 measurement in 574 :code:`Raw_Data_Stop_Time[2]=810` (stop of the third -45 measurement in seconds since :code:`RawData_Start_Time_UT`)
689 seconds since RawData\_Start\_Time\_UT) 575
690 576 Moreover, according to the order of the channels in the :code:`channel_ID` variable, the :code:`Raw_Lidar_Data` array should be filled as it follows:
691 Raw\_Data\_Stop\_Time[2]=810 (stop of the third -45 measurement in 577
692 seconds since RawData\_Start\_Time\_UT) 578 :code:`Raw_Lidar_Data[0][0][points]` :math:`\rightarrow` 1\ :sup:`st` measured transmitted signal at +45 degrees
693 579
694 Moreover, according to the order of the channels in the channel\_ID 580 :code:`Raw_Lidar_Data[0][1][points]` :math:`\rightarrow` 1\ :sup:`st` measured transmitted signal at +45 degrees
695 variable, the Raw\_Lidar\_Data array should be filled as it follows: 581
696 582 :code:`Raw_Lidar_Data[0][2][points]` :math:`\rightarrow` 1\ :sup:`st` measured transmitted signal at -45 degrees
697 Raw\_Lidar\_Data[0][0][points] → 1\ :sup:`st` measured transmitted 583
698 signal at +45 degrees 584 :code:`Raw_Lidar_Data[0][3][points]` :math:`\rightarrow` 1\ :sup:`st` measured transmitted signal at -45 degrees
699 585
700 Raw\_Lidar\_Data[0][1][points] → 1\ :sup:`st` measured reflected signal 586 :code:`Raw_Lidar_Data[1][0][points]` :math:`\rightarrow` 2\ :sup:`nd` measured transmitted signal at +45 degrees
701 at +45 degrees 587
702 588 :code:`Raw_Lidar_Data[1][1][points]` :math:`\rightarrow` 2\ :sup:`nd` measured transmitted signal at +45 degrees
703 Raw\_Lidar\_Data[0][2][points] → 1\ :sup:`st` measured transmitted 589
704 signal at -45 degrees 590 :code:`Raw_Lidar_Data[1][2][points]` :math:`\rightarrow` 2\ :sup:`nd` measured transmitted signal at -45 degrees
705 591
706 Raw\_Lidar\_Data[0][3][points] → 1\ :sup:`st` measured reflected signal 592 :code:`Raw_Lidar_Data[1][3][points]` :math:`\rightarrow` 2\ :sup:`nd` measured transmitted signal at -45 degrees
707 at -45 degrees 593
708 594 :code:`Raw_Lidar_Data[2][0][points]` :math:`\rightarrow` 3\ :sup:`rd` measured transmitted signal at +45 degrees
709 Raw\_Lidar\_Data[1][0][points] → 2\ :sup:`nd` measured transmitted 595
710 signal at +45 degrees 596 :code:`Raw_Lidar_Data[2][1][points]` :math:`\rightarrow` 3\ :sup:`rd` measured transmitted signal at +45 degrees
711 597
712 Raw\_Lidar\_Data[1][1][points] → 2\ :sup:`nd` measured reflected signal 598 :code:`Raw_Lidar_Data[2][2][points]` :math:`\rightarrow` 3\ :sup:`rd` measured transmitted signal at -45 degrees
713 at +45 degrees 599
714 600 :code:`Raw_Lidar_Data[2][3][points]` :math:`\rightarrow` 3\ :sup:`rd` measured transmitted signal at -45 degrees
715 Raw\_Lidar\_Data[1][2][points] → 2\ :sup:`nd` measured transmitted 601
716 signal at -45 degrees 602 Once this file has been created it needs to be submitted to the SCC and linked to the configuration “depol\_calibration”. The result of the SCC analysis on this file will be the calculation of the calibration constant h\ :sup:`\*` that will be logged into the SCC database and can be used to calibrate Raman/Elastic backscat ter products (see section 3.3).
717 603
718 Raw\_Lidar\_Data[1][3][points] → 2\ :sup:`nd` measured reflected signal 604 3.3 Definition of “Raman/Elastic backscatter and linear depolarization ratio”
719 at -45 degrees
720
721 Raw\_Lidar\_Data[2][0][points] → 3\ :sup:`rd` measured transmitted
722 signal at +45 degrees
723
724 Raw\_Lidar\_Data[2][1][points] → 3\ :sup:`rd` measured reflected signal
725 at +45 degrees
726
727 Raw\_Lidar\_Data[2][2][points] → 3\ :sup:`rd` measured transmitted
728 signal at -45 degrees
729
730 Raw\_Lidar\_Data[2][3][points] → 3\ :sup:`rd` measured reflected signal
731 at -45 degrees
732
733 Once this file has been created it needs to be submitted to the SCC and
734 linked to the configuration “depol\_calibration”. The result of the SCC
735 analysis on this file will be the calculation of the calibration
736 constant h\ :sup:`\*` that will be logged into the SCC database and can
737 be used to calibrate Raman/Elastic backscat ter products (see section
738 3.3).
739
740 **Definition of “Raman/Elastic backscatter and linear depolarization ratio”**
741 ----------------------------------------------------------------------------- 605 -----------------------------------------------------------------------------
742 606
743 In order to calculate the *PLDR* we need to modify the polarization 607 In order to calculate the *PLDR* we need to modify the polarization related products linked to the “standard” measurement configurations (the configuration called “nighttime” and/or “daytime” in table 3.2).
744 related products linked to the “standard” measurement configurations 608
745 (the configuration called “nighttime” and/or “daytime” in table 3.2). 609 Let's suppose we have defined the following products (defined already in SCC v3.11):
746
747 Let's suppose we have defined the following products (defined already in
748 SCC v3.11):
749 610
750 **Table 3.4:** Example of products configuration in SCC v3.11 611 **Table 3.4:** Example of products configuration in SCC v3.11
751 612
752 +-----------------------+--------------+-----------------------+-------------+-----------+ 613 +-----------------------+--------------+-----------------------+-------------+-----------+
753 | Product Name | Product ID | Product Type | nighttime | daytime | 614 | Product Name | Product ID | Product Type | nighttime | daytime |
754 +-----------------------+--------------+-----------------------+-------------+-----------+ 615 +-----------------------+--------------+-----------------------+-------------+-----------+
755 | Raman backscatter | 1 | Raman backscatter |  | | 616 | Raman backscatter | 1 | Raman backscatter | x | |
756 | | | | | | 617 | | | | | |
757 | 355nm | | | | | 618 | 355nm | | | | |
758 +-----------------------+--------------+-----------------------+-------------+-----------+ 619 +-----------------------+--------------+-----------------------+-------------+-----------+
759 | Extinction | 2 | Extinction |  | | 620 | Extinction | 2 | Extinction | x | |
760 | | | | | | 621 | | | | | |
761 | 387nm | | | | | 622 | 387nm | | | | |
762 +-----------------------+--------------+-----------------------+-------------+-----------+ 623 +-----------------------+--------------+-----------------------+-------------+-----------+
763 | Raman backscatter | 3 | Raman backscatter |  | | 624 | Raman backscatter | 3 | Raman backscatter | x | |
764 | | | | | | 625 | | | | | |
765 | 532nm | | | | | 626 | 532nm | | | | |
766 +-----------------------+--------------+-----------------------+-------------+-----------+ 627 +-----------------------+--------------+-----------------------+-------------+-----------+
767 | Extinction | 4 | Extinction |  | | 628 | Extinction | 4 | Extinction | x | |
768 | | | | | | 629 | | | | | |
769 | 532nm | | | | | 630 | 532nm | | | | |
770 +-----------------------+--------------+-----------------------+-------------+-----------+ 631 +-----------------------+--------------+-----------------------+-------------+-----------+
771 | Elastic backscatter | 5 | Elastic backscatter | |  | 632 | Elastic backscatter | 5 | Elastic backscatter | | x |
772 | | | | | | 633 | | | | | |
773 | 355nm | | | | | 634 | 355nm | | | | |
774 +-----------------------+--------------+-----------------------+-------------+-----------+ 635 +-----------------------+--------------+-----------------------+-------------+-----------+
775 | Elastic backscatter | 6 | Elastic backscatter | |  | 636 | Elastic backscatter | 6 | Elastic backscatter | | x |
776 | | | | | | 637 | | | | | |
777 | 532nm | | | | | 638 | 532nm | | | | |
778 +-----------------------+--------------+-----------------------+-------------+-----------+ 639 +-----------------------+--------------+-----------------------+-------------+-----------+
779 | Elastic backscatter | 7 | Elastic backscatter |  |  | 640 | Elastic backscatter | 7 | Elastic backscatter | x | x |
780 | | | | | | 641 | | | | | |
781 | 1064nm | | | | | 642 | 1064nm | | | | |
782 +-----------------------+--------------+-----------------------+-------------+-----------+ 643 +-----------------------+--------------+-----------------------+-------------+-----------+
783 644
784 Product ID=1, 2, 4, 5, 7 do not need any modification as they do not 645 Product ID=1, 2, 4, 5, 7 do not need any modification as they do not involve polarization channels. The only product that need to be modified are the Product ID=3 and 6. To produce b532 files containing also *PLDR* we need to modify the “nighttime” and “daytime” configurations to include a product of type “Raman bakscatter and linear depolarization ratio” or “Elastic bakscatter and linear depolarization ratio” respectively. So the configuration reported in table 3.4 should be
785 involve polarization channels. The only product that need to be modified
786 are the Product ID=3 and 6. To produce b532 files containing also *PLDR*
787 we need to modify the “nighttime” and “daytime” configurations to
788 include a product of type “Raman bakscatter and linear depolarization
789 ratio” or “Elastic bakscatter and linear depolarization ratio”
790 respectively. So the configuration reported in table 3.4 should be
791 changed to match what is included in table 3.5. 646 changed to match what is included in table 3.5.
792 647
793 **Table 3.5:** The same of table 3.4 but with new product types 648 **Table 3.5:** The same of table 3.4 but with new product types introduced in SCC v4.0
794 introduced in SCC v4.0
795 649
796 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ 650 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+
797 | Product Name | Product ID | Product Type | nighttime | daytime | 651 | Product Name | Product ID | Product Type | nighttime | daytime |
798 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ 652 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+
799 | Raman backscatter | 1 | Raman backscatter |  | | 653 | Raman backscatter | 1 | Raman backscatter | x | |
800 | | | | | | 654 | | | | | |
801 | 355nm | | | | | 655 | 355nm | | | | |
802 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ 656 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+
803 | Extinction | 2 | Extinction |  | | 657 | Extinction | 2 | Extinction | x | |
804 | | | | | | 658 | | | | | |
805 | 387nm | | | | | 659 | 387nm | | | | |
806 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ 660 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+
807 | Raman backscatter | 10 | **Raman backscatter and linear depolarization ratio** |  | | 661 | Raman backscatter | 10 | :red:`Raman backscatter and linear depolarization ratio` | x | |
808 | | | | | | 662 | | | | | |
809 | 532nm | | | | | 663 | 532nm | | | | |
810 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ 664 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+
811 | Extinction | 4 | Extinction |  | | 665 | Extinction | 4 | Extinction | x | |
812 | | | | | | 666 | | | | | |
813 | 532nm | | | | | 667 | 532nm | | | | |
814 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ 668 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+
815 | Elastic backscatter | 5 | Elastic backscatter | |  | 669 | Elastic backscatter | 5 | Elastic backscatter | | x |
816 | | | | | | 670 | | | | | |
817 | 355nm | | | | | 671 | 355nm | | | | |
818 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ 672 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+
819 | Elastic backscatter | 11 | **Elastic backscatter and linear depolarization ratio** | |  | 673 | Elastic backscatter | 11 | :red:`Elastic backscatter and linear depolarization ratio`| | x |
820 | | | | | | 674 | | | | | |
821 | 532nm | | | | | 675 | 532nm | | | | |
822 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ 676 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+
823 | Elastic backscatter | 7 | Elastic backscatter |  |  | 677 | Elastic backscatter | 7 | Elastic backscatter | x | x |
824 | | | | | | 678 | | | | | |
825 | 1064nm | | | | | 679 | 1064nm | | | | |
826 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ 680 +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+
827 681
828 As you can see in table 3.5, the old product IDs=3 and 6 (present in 682 As you can see in table 3.5, the old product IDs=3 and 6 (present in table 3.4) have been replaced with the new product ID=10 and 11 to guarantee the calculation of *PLDR*.
829 table 3.4) have been replaced with the new product ID=10 and 11 to 683
830 guarantee the calculation of *PLDR*. 684 It is important to set among the product options of the product ID=10 and 11 which calibration product we want to use for calibration (see section 3.2). This can be done using the SCC web interface setting the appropriate setting in the tab *Polarization calibration products* (see figure 3.4). According to the current example you should set here the calibration product defined in section 3.2.
831 685
832 It is important to set among the product options of the product ID=10 686 .. figure:: figure3.4.png
833 and 11 which calibration product we want to use for calibration (see 687 :height: 102
834 section 3.2). This can be done using the SCC web interface setting the 688 :width: 1895
835 appropriate setting in the tab *Polarization calibration products* (see 689 :scale: 100 %
836 figure 3.4). According to the current example you should set here the 690 :align: center
837 calibration product defined in section 3.2. 691
838 692 **Figure 3.4:** How to link a product to calibrate with a calibration product.
839 |image3| How to link a product to calibrate with a calibration product. 693
840 694 :WARNING: Please not that also *Raman/Elastic backscatter products* need to be linked to a calibration product because the calibration constant and the corresponding correction factor is needed to calculate the total signal out of the two polarization components even if the *PLDR* is not involved in the product calculation.
841 **WARNING:** Please not that also *Raman/Elastic backscatter products*
842 need to be linked to a calibration product because the calibration
843 constant and the corresponding correction factor is needed to calculate
844 the total signal out of the two polarization components even if the
845 *PLDR* is not involved in the product calculation.
846
847 .. |image0| image:: ./media/image1.png
848 :width: 6.69514in
849 :height: 2.40764in
850 .. |image1| image:: ./media/image2.png
851 :width: 6.69306in
852 :height: 1.71458in
853 .. |image2| image:: ./media/image3.png
854 :width: 6.69306in
855 :height: 1.77431in
856 .. |image3| image:: ./media/image4.png
857 :width: 6.69306in
858 :height: 0.36389in

EARLINET Repository: SCC Documentation

mercurial