docs/faq/faq.rst

changeset 81
26ba013a14a7
parent 61
e3ff7af1d97e
child 82
aaeb64dc946b
--- a/docs/faq/faq.rst	Thu Mar 17 12:07:31 2016 +0200
+++ b/docs/faq/faq.rst	Thu Nov 03 13:13:01 2016 +0200
@@ -57,15 +57,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 +74,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 +109,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?

mercurial