comparison: docs/faq/faq.rst
docs/faq/faq.rst
- changeset 81
- 26ba013a14a7
- parent 61
- e3ff7af1d97e
- child 82
- aaeb64dc946b
equal
deleted
inserted
replaced
| 65:a6e69feda10d | 81:26ba013a14a7 |
|---|---|
| 55 A: There are no threshold values defined for the different range types. This information | 55 A: There are no threshold values defined for the different range types. This information |
| 56 is used only in the gluing procedures just to identify which channel should be taken | 56 is used only in the gluing procedures just to identify which channel should be taken |
| 57 as low range and which one as far range. If no gluing is applied by the SCC the range | 57 as low range and which one as far range. If no gluing is applied by the SCC the range |
| 58 id flags are not taken into account. | 58 id flags are not taken into account. |
| 59 | 59 |
| 60 Variable depolarization factor | |
| 61 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
| 62 | |
| 63 Q: Due to changes in the settings of our lidar system, the depolarization factor can | |
| 64 change during the measurement. Is it necessary to provide one SCC-file for each settings | |
| 65 or is it possible to set the Depolarization_Factor variable time dependent? | |
| 66 | |
| 67 A: Unfortunately it is not possible to have time dependence on Depolarization_Factor variable. | |
| 68 So if this parameter changes you should provide different SCC files for each setting. | |
| 69 | 60 |
| 70 Extra netcdf parameters | 61 Extra netcdf parameters |
| 71 ~~~~~~~~~~~~~~~~~~~~~~~ | 62 ~~~~~~~~~~~~~~~~~~~~~~~ |
| 72 Q: Is it possible for documentation purposes to put own parameters in the SCC-NetCDF file? | 63 Q: Is it possible for documentation purposes to put own parameters in the SCC-NetCDF file? |
| 73 For example who created the file.... Are there any reasons against this? | 64 For example who created the file.... Are there any reasons against this? |
| 80 ~~~~~~~~~~~~~~ | 71 ~~~~~~~~~~~~~~ |
| 81 Q: Which NetCDF version is to use? NetCDF3, NetCDF3 Classic, NetCDF4, NetCDF4 Classic? | 72 Q: Which NetCDF version is to use? NetCDF3, NetCDF3 Classic, NetCDF4, NetCDF4 Classic? |
| 82 | 73 |
| 83 A: The NetCDF libraries 4.1.3 are used in all the SCC modules. So all the NetCDF formats you | 74 A: The NetCDF libraries 4.1.3 are used in all the SCC modules. So all the NetCDF formats you |
| 84 have indicated should be compatible with the SCC (we have tested NetCDF3 and NetCDF4). | 75 have indicated should be compatible with the SCC (we have tested NetCDF3 and NetCDF4). |
| 76 | |
| 85 | 77 |
| 86 Lidar ratio | 78 Lidar ratio |
| 87 ~~~~~~~~~~~ | 79 ~~~~~~~~~~~ |
| 88 Q: What are the values for the lidar ratio used in the SCC_DB? | 80 Q: What are the values for the lidar ratio used in the SCC_DB? |
| 89 | 81 |
| 114 | 106 |
| 115 Note: you cannot calculate a b532 file containing the Raman and elastic backscatters at the same time. | 107 Note: you cannot calculate a b532 file containing the Raman and elastic backscatters at the same time. |
| 116 The reason is that the 2 products will produce an output file with the same name (according to the EARLINET rules). | 108 The reason is that the 2 products will produce an output file with the same name (according to the EARLINET rules). |
| 117 Moreover in general, it makes no sense to calculate the elastic backscatter when you can calculate the Raman | 109 Moreover in general, it makes no sense to calculate the elastic backscatter when you can calculate the Raman |
| 118 one which usually is better. | 110 one which usually is better. |
| 111 | |
| 119 | 112 |
| 120 Filename conventions | 113 Filename conventions |
| 121 ~~~~~~~~~~~~~~~~~~~~ | 114 ~~~~~~~~~~~~~~~~~~~~ |
| 122 Q: What are the conventions for the filenames for the various files that need to be uploaded? | 115 Q: What are the conventions for the filenames for the various files that need to be uploaded? |
| 123 | 116 |
