docs/faq/faq.rst

changeset 61
e3ff7af1d97e
parent 55
d4ed2005724f
child 79
99f25ea47505
child 81
26ba013a14a7
equal deleted inserted replaced
57:2c95a0843b64 61:e3ff7af1d97e
188 Q: The preprocessing of one of my measurements failed (I get a status -127). However, when I check the Exit codes 188 Q: The preprocessing of one of my measurements failed (I get a status -127). However, when I check the Exit codes
189 to see the description of the problem, I get an empty value (-). What does this mean? 189 to see the description of the problem, I get an empty value (-). What does this mean?
190 190
191 A: This means that the preprocessor crushed unexpectedly! Sorry for that! Report the problem in the forum and it will be fixed 191 A: This means that the preprocessor crushed unexpectedly! Sorry for that! Report the problem in the forum and it will be fixed
192 soon. 192 soon.
193
194 Optical processing (ELDA) failed but no Exit code is provided
195 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
196 Q: The optical processing of one of my measurements failed (I get a status -127). However, when I check the Exit codes
197 to see the description of the problem, there is none. What does this mean?
198
199 A: The reason for which ELDA failed it's not currently easy to find because
200 this module does not implement yet the setting of a specific error code for a
201 specific error. Based of past experience, when something like that happens is
202 due to a poor S/N ratio of the pre-processed signals. What you could try to do
203 to debug the problem is:
204
205 * try to increase the S/N ratio of the pre-processed signals, for example by increasing
206 the pre-processing vertical resolution or/and the pre-processing integration time.
207
208 * look at the pre-processed signals produced for this measurement and see if
209 there is something wrong in them.

mercurial