# HG changeset patch # User Iannis # Date 1422442090 -7200 # Node ID e3ff7af1d97e875ab8d34c79503f5c16d7226a39 # Parent 2c95a0843b6404ebfd60cc6b0c9ffdbf2c684627 Removed obsolete elda exit code FAQ diff -r 2c95a0843b64 -r e3ff7af1d97e docs/faq/faq.rst --- a/docs/faq/faq.rst Wed Jul 09 17:47:38 2014 +0300 +++ b/docs/faq/faq.rst Wed Jan 28 12:48:10 2015 +0200 @@ -190,20 +190,3 @@ 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.