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

shower_distribution not propagated by HDF5EventSource #2632

Open
kosack opened this issue Oct 30, 2024 · 1 comment · May be fixed by #2633
Open

shower_distribution not propagated by HDF5EventSource #2632

kosack opened this issue Oct 30, 2024 · 1 comment · May be fixed by #2633
Assignees
Labels

Comments

@kosack
Copy link
Contributor

kosack commented Oct 30, 2024

Describe the bug

The /simulation/service/shower_distribution histograms are written if you read a simtel file with the SimTelEventSource, but further processing of the HDF5 file by the HDF5EventSource drops this information. This is not critical, as one can use the configuration/simulation/run to compute the spectrum of simulated events, however that may be insufficient in the future if more complex spectra are used.

To Reproduce
Steps to reproduce the behavior:

  1. process an existing ctapipe output file with ctapipe-process to a higher level

Expected behavior

Simulated shower distributions end up in output files.

Supporting information

This is not a problem for the HDF5Merger, which does propagate this information, so merging and applying models works fine. it is only an issue if DL1 files are further processed into DL2 by ctapipe-process.

We need a unit test that does:

  • simulated-R0 → DL1 → file
  • file → DL2
  • checks the data model against the output (note this last step probably is more general: we need a ctapipe-verify command )
@kosack kosack added the bug label Oct 30, 2024
@maxnoe
Copy link
Member

maxnoe commented Oct 30, 2024

Confirmed. We have no general API on the EventSource and the DataWriter explicitly checks for SimTelEventSource. So no other event source can even try to provide the histograms.

Reading the comments in the DataWriter method, this is a known issue... but we have no corresponding issue here.

Will fix, this is definitely a bug and directly impacts our processing of prod5/prod6 on the GRID, since we recently switched to a setup where we first run ctapipe-process to extract only images for all telescopes and then again ctapipe-process to perform parametrization and stereo-reco for a selected subarray. So we loose the histograms here in the second step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants