comparison: docs/faq/faq.rst
docs/faq/faq.rst
- changeset 54
- 613613bc8872
- parent 40
- fed9320bfbd2
- child 55
- d4ed2005724f
equal
deleted
inserted
replaced
| 53:e1cbe6415709 | 54:613613bc8872 |
|---|---|
| 117 Moreover in general, it makes no sense to calculate the elastic backscatter when you can calculate the Raman | 117 Moreover in general, it makes no sense to calculate the elastic backscatter when you can calculate the Raman |
| 118 one which usually is better. | 118 one which usually is better. |
| 119 | 119 |
| 120 Filename conventions | 120 Filename conventions |
| 121 ~~~~~~~~~~~~~~~~~~~~ | 121 ~~~~~~~~~~~~~~~~~~~~ |
| 122 A: What are the conventions for the filenames for the various files that need to be uploaded? | 122 Q: What are the conventions for the filenames for the various files that need to be uploaded? |
| 123 | 123 |
| 124 Q: The following definitions apply: | 124 A: The following definitions apply: |
| 125 | 125 |
| 126 SCC raw lidar data file | 126 SCC raw lidar data file |
| 127 ^^^^^^^^^^^^^^^^^^^^^^^ | 127 ^^^^^^^^^^^^^^^^^^^^^^^ |
| 128 | 128 |
| 129 This file should be named as measID.nc. For example if your measurement had a measurement ID of 20130101cc00 the corresponding NetCDF file should be named 20130101cc00.nc | 129 This file should be named as measID.nc. For example if your measurement had a measurement ID of 20130101cc00 the corresponding NetCDF file should be named 20130101cc00.nc |
| 185 Q: The preprocessing of one of my measurements failed (I get a status -127). However, when I check the Exit codes | 185 Q: The preprocessing of one of my measurements failed (I get a status -127). However, when I check the Exit codes |
| 186 to see the description of the problem, I get an empty value (-). What does this mean? | 186 to see the description of the problem, I get an empty value (-). What does this mean? |
| 187 | 187 |
| 188 A: This means that the preprocessor crushed unexpectedly! Sorry for that! Report the problem in the forum and it will be fixed | 188 A: This means that the preprocessor crushed unexpectedly! Sorry for that! Report the problem in the forum and it will be fixed |
| 189 soon. | 189 soon. |
| 190 | |
| 191 Optical processing (ELDA) failed but no Exit code is provided | |
| 192 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
| 193 Q: The optical processing of one of my measurements failed (I get a status -127). However, when I check the Exit codes | |
| 194 to see the description of the problem, there is none. What does this mean? | |
| 195 | |
| 196 A: The reason for which ELDA failed it's not currently easy to find because | |
| 197 this module does not implement yet the setting of a specific error code for a | |
| 198 specific error. Based of past experience, when something like that happens is | |
| 199 due to a poor S/N ratio of the pre-processed signals. What you could try to do | |
| 200 to debug the problem is: | |
| 201 | |
| 202 * try to increase the S/N ratio of the pre-processed signals, for example by increasing | |
| 203 the pre-processing vertical resolution or/and the pre-processing integration time. | |
| 204 | |
| 205 * look at the pre-processed signals produced for this measurement and see if | |
| 206 there is something wrong in them. |
