Mercurial > public > sccdocs / changeset

--- a/docs/conf.py	Thu Nov 03 16:27:26 2016 +0200
+++ b/docs/conf.py	Thu Nov 03 16:27:54 2016 +0200
@@ -41,16 +41,16 @@
 
 # General information about the project.
 project = u'Single Calculus Chain'
-copyright = u'2014, Ioannis Binietoglou'
+copyright = u'2016, Ioannis Binietoglou'
 
 # The version info for the project you're documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 #
 # The short X.Y version.
-version = '2.0'
+version = '4.0'
 # The full version, including alpha/beta/rc tags.
-release = '2.0'
+release = '4.0.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

--- a/docs/faq/faq.rst	Thu Nov 03 16:27:26 2016 +0200
+++ b/docs/faq/faq.rst	Thu Nov 03 16:27:54 2016 +0200
@@ -5,7 +5,7 @@
 Using an ancillary file
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-Q: I use the “Quick upload” to submit a measurement file together with an ancillary 
+Q: I use the "Quick upload" to submit a measurement file together with an ancillary
 file. Will this ancillary file be used in the processing of my measurement. 
 
 A: No. Which ancillary file is used when processing a measurement is defined in the 
@@ -47,6 +47,23 @@
 module will be implemented at the end of ACTRIS project. 
 
 
+Minimum number of analog files to submit
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Q: Is it possible to submit a single analog profile for processing?
+
+
+A: It depepends on the type of product you ar trying to calculate.
+
+* If the product is a linear polarization calibration,  it is possible to submit a timeseries containing 
+  one single analog profile. This is allowed because some stations are performing depolarization calibration measurements using 
+  single profiles. If the errors are present they will be taken into account for the calculation of the error on calibration constant. 
+  If they are not the error on calibration constant is calculate as the standard deviation withing the calibration range.
+
+* If the product to calculate is NOT a linear polarization calibration, if the raw analog error have not been provided we need at
+  least 3 raw profile in order to compute the statistical error
+
+
 High/low range channels
 ~~~~~~~~~~~~~~~~~~~~~~~
 Q: What is the definition of low range, ultra near range and high range channels? 
@@ -57,15 +74,6 @@
 as low range and which one as far range. If no gluing is applied by the SCC the range 
 id flags are not taken into account.
 
-Variable depolarization factor
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Q: Due to changes in the settings of our lidar system, the depolarization factor can 
-change during the measurement. Is it necessary to provide one SCC-file for each settings 
-or is it possible to set the Depolarization_Factor variable time dependent? 
-   
-A: Unfortunately it is not possible to have time dependence on Depolarization_Factor variable. 
-So if this parameter changes you should provide different SCC files for each setting.
 
 Extra netcdf parameters
 ~~~~~~~~~~~~~~~~~~~~~~~
@@ -83,6 +91,7 @@
 A: The NetCDF libraries 4.1.3 are used in all the SCC modules. So all the NetCDF formats you 
 have indicated should be compatible with the SCC (we have tested NetCDF3 and NetCDF4).
 
+
 Lidar ratio
 ~~~~~~~~~~~
 Q: What are the values for the lidar ratio used in the SCC_DB? 
@@ -117,6 +126,7 @@
 Moreover in general, it makes no sense to calculate the elastic backscatter when you can calculate the Raman 
 one which usually is better.
 
+
 Filename conventions
 ~~~~~~~~~~~~~~~~~~~~
 Q: What are the conventions for the filenames for the various files that need to be uploaded?