Mercurial > public > sccdocs / changeset

--- a/docs/depolarization/depolarization.rst	Tue Apr 05 12:16:26 2022 +0200
+++ b/docs/depolarization/depolarization.rst	Tue Jul 26 11:36:46 2022 +0200
@@ -587,27 +587,27 @@
 
 :code:`Raw_Lidar_Data[0][0][points]` :math:`\rightarrow` 1\ :sup:`st` measured transmitted signal at +45 degrees
 
-:code:`Raw_Lidar_Data[0][1][points]` :math:`\rightarrow` 1\ :sup:`st` measured transmitted signal at +45 degrees
+:code:`Raw_Lidar_Data[0][1][points]` :math:`\rightarrow` 1\ :sup:`st` measured reflected signal at +45 degrees
 
 :code:`Raw_Lidar_Data[0][2][points]` :math:`\rightarrow` 1\ :sup:`st` measured transmitted signal at -45 degrees
 
-:code:`Raw_Lidar_Data[0][3][points]` :math:`\rightarrow` 1\ :sup:`st` measured transmitted signal at -45 degrees
+:code:`Raw_Lidar_Data[0][3][points]` :math:`\rightarrow` 1\ :sup:`st` measured reflected signal at -45 degrees
 
 :code:`Raw_Lidar_Data[1][0][points]` :math:`\rightarrow` 2\ :sup:`nd` measured transmitted signal at +45 degrees
 
-:code:`Raw_Lidar_Data[1][1][points]` :math:`\rightarrow` 2\ :sup:`nd` measured transmitted signal at +45 degrees
+:code:`Raw_Lidar_Data[1][1][points]` :math:`\rightarrow` 2\ :sup:`nd` measured reflected signal at +45 degrees
 
 :code:`Raw_Lidar_Data[1][2][points]` :math:`\rightarrow` 2\ :sup:`nd` measured transmitted signal at -45 degrees
 
-:code:`Raw_Lidar_Data[1][3][points]` :math:`\rightarrow` 2\ :sup:`nd` measured transmitted signal at -45 degrees
+:code:`Raw_Lidar_Data[1][3][points]` :math:`\rightarrow` 2\ :sup:`nd` measured reflected signal at -45 degrees
 
 :code:`Raw_Lidar_Data[2][0][points]` :math:`\rightarrow` 3\ :sup:`rd` measured transmitted signal at +45 degrees
 
-:code:`Raw_Lidar_Data[2][1][points]` :math:`\rightarrow` 3\ :sup:`rd` measured transmitted signal at +45 degrees
+:code:`Raw_Lidar_Data[2][1][points]` :math:`\rightarrow` 3\ :sup:`rd` measured reflected signal at +45 degrees
 
 :code:`Raw_Lidar_Data[2][2][points]` :math:`\rightarrow` 3\ :sup:`rd` measured transmitted signal at -45 degrees
 
-:code:`Raw_Lidar_Data[2][3][points]` :math:`\rightarrow` 3\ :sup:`rd` measured transmitted signal at -45 degrees
+:code:`Raw_Lidar_Data[2][3][points]` :math:`\rightarrow` 3\ :sup:`rd` measured reflected signal at -45 degrees
 
 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 backscatter products (see section 3.3).
 

--- a/docs/file_formats/netcdf_file.rst	Tue Apr 05 12:16:26 2022 +0200
+++ b/docs/file_formats/netcdf_file.rst	Tue Jul 26 11:36:46 2022 +0200
@@ -3,7 +3,7 @@
 The SCC input netCDF file format
 ================================
 
-A more detailed version of this document can be found in this :download:`pdf file <../files/NetCDF_input_file_v3_5.pdf>`.
+A more detailed version of this document can be found in this :download:`pdf file <../files/NetCDF_input_file_v3_6.pdf>`.
 
 .. note::
 
@@ -119,7 +119,7 @@
 +----------------------+-------------------------------------------+
 | Station Name         | Dummy station                             |
 +----------------------+-------------------------------------------+
-| Earlinet call-sign   | cc                                        |
+| Earlinet call-sign   | ccc                                       |
 +----------------------+-------------------------------------------+
 | Pointing angle       | 5 degrees with respect to the zenith      |
 +----------------------+-------------------------------------------+
@@ -813,17 +813,29 @@
 ~~~~~~~~~~~~~~~~~
 
 -  | ``Measurement_ID``
-   | This mandatory global attribute defines the measurement ID
-     corresponding to the actual lidar measurement. It is a string
-     composed by 12 characters. The first 8 characters give the start
-     date of measurement in the format YYYYMMDD. The next 2 characters
-     give the Earlinet call-sign of the station. The last 2 characters
-     are used to distinguish between different time-series within the
-     same date. In our example we have to set:
+   | The submission of a raw data file to the SCC is possible only if it contains
+     this global attribute which, in general, can be set to any alphanumeric string 
+     composed by 12 or 15 characters. The raw data file can be registered into the SCC database only
+     if the corresponding measurement ID string is not already used by any other raw data file 
+     (of any station). To ensure the unicity of the measurement ID string the following format is highly recommened::
+
+     <start\_date><station\_code><start\_time> 
+
+     where: 
+
+     +-----------------------+------------------------------------------------------------------+
+     | *<start\_date>*       | 8 digits measurement start date: YYYYMMDD (for example 20220620) | 
+     +-----------------------+------------------------------------------------------------------+
+     | *<station\_code>*     | 3 digits code (for example pot)                                  |
+     +-----------------------+------------------------------------------------------------------+
+     | *<star\_time>*        | 4 digits measurement start time (UTC): HHMM (for example 2226)   |
+     +-----------------------+------------------------------------------------------------------+
+ 
+     In our example we have to set:
 
    ::
 
-        Measurement_ID= "20090130cc00" ;
+        Measurement_ID= "20090130ccc0000" ;
 
 -  | ``RawData_Start_Date``
    | This mandatory global attribute defines the start date of lidar
@@ -920,7 +932,7 @@
             double DAQ_Range(channels) ;
 
     // global attributes:
-                    :Measurement_ID = "20090130cc00" ;
+                    :Measurement_ID = "20090130ccc0000" ;
                     :RawData_Start_Date = "20090130" ;
                     :RawData_Start_Time_UT = "000001" ;
                     :RawData_Stop_Time_UT = "000501" ;
@@ -1049,7 +1061,7 @@
 
     Measurement_ID.nc
 
-| so in the example the filename should be 20090130cc00.nc.
+| so in the example the filename should be 20090130ccc0000.nc.
   
 Please keep in mind that in case you submit a file like the previous
 one all the parameters present in it will be used by the SCC even if
@@ -1088,7 +1100,7 @@
             double DAQ_Range(channels) ;
 
     // global attributes:
-                    :Measurement_ID = "20090130cc00" ;
+                    :Measurement_ID = "20090130ccc0000" ;
                     :RawData_Start_Date = "20090130" ;  
                     :RawData_Start_Time_UT = "000001" ;
                     :RawData_Stop_Time_UT = "000501" ;
@@ -1210,17 +1222,17 @@
 
 In this case we have to generate the following NetCDF additional files:
 
--  | ``rs_20090130cc00.nc``
+-  | ``rs_20090130ccc0000.nc``
    | The name of *Sounding Data* file has to be computed as follows:
    | ``"rs_"``\ +\ ``Measurement_ID``
    | The structure of this file is summarized in table 2 of the pdf.
 
--  | ``ov_20090130cc00.nc``
+-  | ``ov_20090130ccc0000.nc``
    | The name of *Overlap* file has to be computed as follows:
    | ``"ov_"``\ +\ ``Measurement_ID``
    | The structure of this file is summarized in table 3 of the pdf.
 
--  | ``lr_20090130cc00.nc``
+-  | ``lr_20090130ccc0000.nc``
    | The name of *Lidar Ratio* file has to be computed as follows:
    | ``"lr_"``\ +\ ``Measurement_ID``
    | The structure of this file is summarized in table 4 of the pdf.
@@ -1247,17 +1259,17 @@
 
    ::
 
-       Sounding_File_Name = "rs_20090130cc00.nc" ;
+       Sounding_File_Name = "rs_20090130ccc0000.nc" ;
 
 #. Add the global attribute ``LR_File_Name``
 
    ::
 
-       LR_File_Name = "lr_20090130cc00.nc" ;
+       LR_File_Name = "lr_20090130ccc0000.nc" ;
 
 #. Add the global attribute ``Overlap_File_Name``
 
    ::
 
-       Overlap_File_Name = "ov_20090130cc00.nc" ;
+       Overlap_File_Name = "ov_20090130ccc0000.nc" ;
 

Binary file docs/files/NetCDF_input_file_v3_6.pdf has changed