SCC Documentation: comparison docs/depolarization/depolarization.rst

-:41c3dda6e81d
+:41bcdbc4191b
-.. role:: underline
-:class: underline
-.. role:: red
 1. Particle Linear Depolarization Ratio Implementation
 ======================================================
 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.
 #. 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 **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 **ALL** channels of **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*
 *elPPnr→elPRnr*
 :code:`32` :math:`\rightarrow` :code:`-45elPRnr`
 :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 **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:
 ::
 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 **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 **ONLY** automatic calibration will be allowed!
+.. warning:: After this transition period **ONLY** automatic calibration will be allowed!
 5. The new **OPTIONAL** variable:
 :code:`string channel\_string\_ID(channels)`
 Starting from SCC v4.0 the lidar channel can be identified not only by using integers (as it happened until SCC v3.11) but also by using strings.
 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).
-: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!
+.. 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!
 3. Real Example
 ===============
 This section describes all the practical steps the users need to follow to switch from SCC v3.11 to new SCC v4.0.
 :scale: 100 %
 :align: center
 **Figure 3.4:** How to link a product to calibrate with a calibration product.
-: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.
+.. 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.

Mercurial > public > sccdocs / file comparison

comparison: docs/depolarization/depolarization.rst

docs/depolarization/depolarization.rst