docs/depolarization/depolarization.rst

changeset 76
41c3dda6e81d
parent 75
5a6f17df5339
parent 74
01da2b469c84
child 77
41bcdbc4191b
equal deleted inserted replaced
75:5a6f17df5339 76:41c3dda6e81d
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). 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).
331 331
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 **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 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 **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
333 modification. Let's focus on the modifications needed for the calculation of backscatter at 532nm. 333 modification. Let's focus on the modifications needed for the calculation of backscatter at 532nm.
334 334
335 .. figure:: ../media/figure3.1.png 335 .. figure:: media/figure3.1.png
336 :height: 369 336 :height: 369
337 :width: 1037 337 :width: 1037
338 :scale: 100 % 338 :scale: 100 %
339 :align: center 339 :align: center
340 340
361 | 1064 | 6 | elT | x | x | 361 | 1064 | 6 | elT | x | x |
362 +----------------+--------------+----------------+-------------+-----------+ 362 +----------------+--------------+----------------+-------------+-----------+
363 363
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. 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.
365 365
366 .. figure:: ../media/figure3.2.png 366 .. figure:: media/figure3.2.png
367 :height: 479 367 :height: 479
368 :width: 1890 368 :width: 1890
369 :scale: 100 % 369 :scale: 100 %
370 :align: center 370 :align: center
371 371
396 396
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. 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.
398 398
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. 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.
400 400
401 .. figure:: ../media/figure3.3.png 401 .. figure:: media/figure3.3.png
402 :height: 495 402 :height: 495
403 :width: 1887 403 :width: 1887
404 :scale: 100 % 404 :scale: 100 %
405 :align: center 405 :align: center
406 406
681 681
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*. 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*.
683 683
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. 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.
685 685
686 .. figure:: ../media/figure3.4.png 686 .. figure:: media/figure3.4.png
687 :height: 102 687 :height: 102
688 :width: 1895 688 :width: 1895
689 :scale: 100 % 689 :scale: 100 %
690 :align: center 690 :align: center
691 691

mercurial