# HG changeset patch # User Iannis # Date 1395731779 -7200 # Node ID 613613bc8872ebc11881c12880fa02a86f89714c # Parent e1cbe641570997130ee50c3dd8235a8f0234a9fd New Q in FAQ. diff -r e1cbe6415709 -r 613613bc8872 docs/faq/faq.rst --- a/docs/faq/faq.rst Tue Mar 25 09:16:06 2014 +0200 +++ b/docs/faq/faq.rst Tue Mar 25 09:16:19 2014 +0200 @@ -119,9 +119,9 @@ Filename conventions ~~~~~~~~~~~~~~~~~~~~ -A: What are the conventions for the filenames for the various files that need to be uploaded? +Q: What are the conventions for the filenames for the various files that need to be uploaded? -Q: The following definitions apply: +A: The following definitions apply: SCC raw lidar data file ^^^^^^^^^^^^^^^^^^^^^^^ @@ -187,3 +187,20 @@ A: This means that the preprocessor crushed unexpectedly! Sorry for that! Report the problem in the forum and it will be fixed soon. + +Optical processing (ELDA) failed but no Exit code is provided +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Q: The optical processing of one of my measurements failed (I get a status -127). However, when I check the Exit codes +to see the description of the problem, there is none. What does this mean? + +A: The reason for which ELDA failed it's not currently easy to find because +this module does not implement yet the setting of a specific error code for a +specific error. Based of past experience, when something like that happens is +due to a poor S/N ratio of the pre-processed signals. What you could try to do +to debug the problem is: + +* try to increase the S/N ratio of the pre-processed signals, for example by increasing + the pre-processing vertical resolution or/and the pre-processing integration time. + +* look at the pre-processed signals produced for this measurement and see if + there is something wrong in them.