Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log warning messages from analysis steps not written to general stderr file #226

Open
morcuended opened this issue May 12, 2023 · 0 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@morcuended
Copy link
Member

Stderr/std log of batch jobs, which pipe all the LST-1 analysis steps, does not capture the warning messages from the lstchain scripts themselves. However, capturing all log messages from all the modules (above a given level of severity) is expected.

This was seen for example with subrun 02978.0091 from 20201120. This is the last subrun of the run and contains events with event_id=0 which gives a warning message if the r0 to dl1 lstchain script is run interactively. These warnings should be propagated to the stderr/out of the batch jobs.

Check how the stderr/out is captured in the subprocesses that run the lstchain scripts inside datasequence.py

@morcuended morcuended added the bug Something isn't working label May 12, 2023
@morcuended morcuended added the help wanted Extra attention is needed label Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant