You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now there is no way of knowing whether jobs launched by autocloser finished OK or not, unless manually checked.
This can lead to unnoticed problems in the merging of files, as happened for 2023-12-11 (see cta-observatory/cta-lstchain#1193). The DL1 merging job failed for one run, but the file was halfway produced.
The update_source_catalog script reads these DL1 merged files but does not check if the merging script finished properly.
The text was updated successfully, but these errors were encountered:
morcuended
changed the title
Check status of jobs scheduled by autocloser
Check state and exit code of jobs scheduled by autocloser
Dec 12, 2023
Also even if there is a dependency on the long-term dl1 check script after all run-wise dl1 data check files are produced, I think sometimes, it is still executed regardless of the exit code of some of the previous jobs. Make sure that this does not happen, for example, launching these lstchain scripts using a bash script with set -e to capture the failing exit at any point.
Right now there is no way of knowing whether jobs launched by autocloser finished OK or not, unless manually checked.
This can lead to unnoticed problems in the merging of files, as happened for 2023-12-11 (see cta-observatory/cta-lstchain#1193). The DL1 merging job failed for one run, but the file was halfway produced.
The
update_source_catalog
script reads these DL1 merged files but does not check if the merging script finished properly.The text was updated successfully, but these errors were encountered: