# HG changeset patch
# User Iannis <ioannis@inoe.ro>
# Date 1422442400 -7200
# Node ID 7cf9dcc563fe73b0b4e0b9df7853eb75d6135ec6
# Parent  bf906688bb4143c9adf76598faa23090de0ee0c5# Parent  f5bf7a56ffd630b21bf9d9146b8be7217c9260bc
Merge from 62:f5bf7a56ffd6

diff -r f5bf7a56ffd6 -r 7cf9dcc563fe .hgtags
--- a/.hgtags	Fri Oct 10 15:16:30 2014 +0200
+++ b/.hgtags	Wed Jan 28 12:53:20 2015 +0200
@@ -2,3 +2,4 @@
 b747e9fcd2b17485ffa2016d82be44eec87d9fa0 1.0.0
 b747e9fcd2b17485ffa2016d82be44eec87d9fa0 1.0
 0000000000000000000000000000000000000000 1.0
+e3ff7af1d97e875ab8d34c79503f5c16d7226a39 v3.1
diff -r f5bf7a56ffd6 -r 7cf9dcc563fe docs/faq/faq.rst
--- a/docs/faq/faq.rst	Fri Oct 10 15:16:30 2014 +0200
+++ b/docs/faq/faq.rst	Wed Jan 28 12:53:20 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.