|
Size: 2820
Comment:
|
Size: 2766
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| On MacOS:<<BR>> |
|
| Line 20: | Line 22: |
| After some investigation it turned out that this happens only on MacOS. Unfortunately this effect isn't reproducible and hence not really debuggable and has to stay open for the moment. The calibrations don't seem to be corrupted and can be used anyway. To be more precise: This warning is emitted after having calculated the LCAL frame and during following reconstruction of the ARC_ON frame in order to create the reconstructed detector image, which in turn is used to collect some QC parameters. | Unfortunately this effect isn't reproducible and hence not really debugable and has to stay open for the moment. The calibrations don't seem to be corrupted and can be used anyway. To be more precise: This warning is emitted after having calculated the LCAL frame and during following reconstruction of the ARC_ON frame in order to create the reconstructed detector image, which in turn is used to collect some QC parameters. |
SPARK Known bugs
Check as well the Change Log to see which bugs have already been fixed, but not released yet.
Here we list some of the most unconvenient bugs. The technically more interested user can check the SPARK Bug Tracking (only from MPE) for more detailed information.
v1.2.5
On MacOS:<<BR>>
Some users reported following warning in kmo_wave_cal even when the resulting XCAL, YCAL, LCAL have the same number of rotator angles with matching values:
[WARNING] : **********************************************************************
[WARNING] : **********************************************************************
[WARNING] : *** For XCAL another angle has been picked than for LCAL ***
[WARNING] : *** (XCAL: 2.68156e+154, LCAL: 6.92925e-310) ***
[WARNING] : *** ***
[WARNING] : *** The recipe will be executed, but the ***
[WARNING] : *** results should be mistrusted !!! ***
[WARNING] : *** ***
[WARNING] : *** Please take care to take XCAL, YCAL and LCAL frame ***
[WARNING] : *** from the same calibration set !!! ***
[WARNING] : **********************************************************************
[WARNING] : **********************************************************************
One value is very large and the other very, very close to zero.
Unfortunately this effect isn't reproducible and hence not really debugable and has to stay open for the moment. The calibrations don't seem to be corrupted and can be used anyway. To be more precise: This warning is emitted after having calculated the LCAL frame and during following reconstruction of the ARC_ON frame in order to create the reconstructed detector image, which in turn is used to collect some QC parameters.
v1.2.4
SPARKplug with MacOS X
- Needs as prerequisite the port p5-tk to run, but it fails to compile. The bug has been reported but not fixed yet.
v1.1.0
SPARKplug
- some static calibration frames in the resulting sof-files are tagged wrong
SPARK / SPRED
MacOSX-Users with a working installation of the SPRED pipeline for SINFONI can experience difficulties using it after having installed SPARK. This happens only if they install packages needed for the SPARKplug tool which uses as well python. In this case separate working environemnts are recommended.