Geant4Output2EDM4hep: get run from worker context - #1663
Conversation
Test Results 9 files 9 suites 11h 44m 19s ⏱️ For more details on these failures, see this check. Results for commit 1eb7ad4. ♻️ This comment has been updated with latest results. |
I'm assuming a "trivial" solution employing |
86c6456 to
2c073a2
Compare
tmadlener
left a comment
There was a problem hiding this comment.
This looks deceptively simple in the end, but I think following your comments / explanations it should be correct.
Somewhat related: Can we handle multiple runs in flight in a multi-threaded context correctly in DD4hep/ddsim? I think at least from the podio side things should keep working, as long as all runs are added to a worker context at some point.
Unless I already forgot again: run information is read when the file is opened. There is no sequential processing of files. Only one run per file, so no treatment of multiple runs in parallel. |
| // only one of the worker contexts (or the master context) has run parameters, since only one reader is created | ||
| // which registers the run parameters | ||
| parameters->extractParameters(runHeader); | ||
| m_file->writeFrame(runHeader, podio::Category::Run); |
There was a problem hiding this comment.
I have to check. Are there always runParameters, or are there cases where we don't have runParameters, but we still want to write the runheader.
only write run frame when we have run parameters
Indeed |
use same printout identifier as during createWorker
|
EventReader test fails only in 107a (podio 1.2.0) 109: this warning is not present (podio 1.7.0) Still weird why it started failing so, need to investigate. |
Because we just turned on EDM4hep for the CI |
|
What is the file version with which the input file has been written? ( |
106podio-dump crashes 107a109a |
|
I am going to disable the edm4hep filereader test for podio < 1.6 |
8b461b0 to
bc2c601
Compare
…mutex Thanks to D. Konstantinov and his codex
Avoids having the mutex present where it is not needed
… register another callback
…ur file is too new
…ound the action here
…and put them into the file in the end
Thank you gemini ❤️
…in multithreaded mode
This will need some more work,
the current status writes one run per thread.BEGINRELEASENOTES
ENDRELEASENOTES
TODO