changeset
depolarization.rst : Replaced the underline and red fonts, with bold ones.
Tue, 25 Oct 2016 13:26:45 +0300
- author
- Michael Kottas <mike.kottas@gmail.com>
- date
- Tue, 25 Oct 2016 13:26:45 +0300
- changeset 75
- 5a6f17df5339
- parent 72
- 1294f75fb2be
- child 76
- 41c3dda6e81d
depolarization.rst : Replaced the underline and red fonts, with bold ones.
| docs/depolarization/depolarization.rst | file | annotate | diff | comparison | revisions |
--- a/docs/depolarization/depolarization.rst Tue Oct 25 12:57:18 2016 +0300 +++ b/docs/depolarization/depolarization.rst Tue Oct 25 13:26:45 2016 +0300 @@ -59,7 +59,7 @@ .. math:: \alpha_s P_s + \alpha_p P_p = P -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. +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. 1.3 SCC procedure to calculate the PLDRP ---------------------------------------- @@ -68,11 +68,11 @@ #. 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); -#. 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; +#. 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; -#. 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. +#. 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. -: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: +: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: *elPP→elPR* *elCP→elPT* @@ -190,8 +190,8 @@ The following minor changes have been applied to raw SCC data format: -#. The optional variable *ID\_Range* has been :underline:`REMOVED`; -#. The :underline:`OPTIONAL` variable :code:`int Signal\_Type(channels)` has been added. The possible values are the same available in the SCC\_DB: +#. The optional variable *ID\_Range* has been **REMOVED**; +#. The **OPTIONAL** variable :code:`int Signal\_Type(channels)` has been added. The possible values are the same available in the SCC\_DB: :code:`0` :math:`\rightarrow` :code:`elT` @@ -261,7 +261,7 @@ :code:`33` :math:`\rightarrow` :code:`-45elPRfr` - :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. + :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. 3. The variables: @@ -270,17 +270,17 @@ double Pol\_Calib\_Range\_Min(channels) double Pol\_Calib\_Range\_Max(channels) - 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; + 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; -4. The variable :code:`Depolarization_Factor` has been :underline:`REMOVED`. +4. The variable :code:`Depolarization_Factor` has been **REMOVED**. 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. - 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). + 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). - :WARNING: After this transition period :underline:`ONLY` automatic calibration will be allowed! + :WARNING: After this transition period **ONLY** automatic calibration will be allowed! -5. The new :underline:`OPTIONAL` variable: +5. The new **OPTIONAL** variable: :code:`string channel\_string\_ID(channels)` @@ -298,7 +298,7 @@ This section describes all the practical steps the users need to follow to switch from SCC v3.11 to new SCC v4.0. :IMPORTANT: - 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. + If your lidar system is not equipped with any polarization channels **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. The practical example reported below describes the modifications required to use the SCC v4.0 for lidar systems equipped with polarization channels. @@ -329,7 +329,7 @@ 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). -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 +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 modification. Let's focus on the modifications needed for the calculation of backscatter at 532nm. .. figure:: ../media/figure3.1.png @@ -352,9 +352,9 @@ +----------------+--------------+----------------+-------------+-----------+ | 387 | 2 | vrRN2 | x | | +----------------+--------------+----------------+-------------+-----------+ -| 532 cross | 3 | :red:`elPT` | x | x | +| 532 cross | 3 | **elPT** | x | x | +----------------+--------------+----------------+-------------+-----------+ -| 532 parallel | 4 | :red:`elPR` | x | x | +| 532 parallel | 4 | **elPR** | x | x | +----------------+--------------+----------------+-------------+-----------+ | 607 | 5 | vrRN2 | x | | +----------------+--------------+----------------+-------------+-----------+ @@ -374,7 +374,7 @@ 3.2 Definition of new calibration configuration and product ----------------------------------------------------------- -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. +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 **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. 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 3.1). @@ -408,7 +408,7 @@ As you can see it is possible to fill in only the K correction factor and not the calibration constant :math:`\eta^*`. -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. +Actually for a **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 **NOT** possible to provide calibration constant using this procedure and the parameter :math:`\eta^*` can be calculated **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. Moreover this raw input file has to contain the variables: :: @@ -658,7 +658,7 @@ | | | | | | | 387nm | | | | | +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ -| Raman backscatter | 10 | :red:`Raman backscatter and linear depolarization ratio` | x | | +| Raman backscatter | 10 | **Raman backscatter and linear depolarization ratio** | x | | | | | | | | | 532nm | | | | | +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ @@ -670,7 +670,7 @@ | | | | | | | 355nm | | | | | +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+ -| Elastic backscatter | 11 | :red:`Elastic backscatter and linear depolarization ratio`| | x | +| Elastic backscatter | 11 | **Elastic backscatter and linear depolarization ratio** | | x | | | | | | | | 532nm | | | | | +-----------------------+--------------+-----------------------------------------------------------+-------------+-----------+
