Add barrel reco configParams to AOD metadata. - #15645
Open
shahor02 wants to merge 3 commits into
Open
Conversation
shahor02
requested review from
a team,
bazinski,
davidrohr,
f3sch,
fprino,
mconcas,
mcoquet642,
sawenzel and
wille10
as code owners
July 28, 2026 17:10
Add all barrel tracking configurables to AOD metadata: write them as ConfigParam_<device>_<configname>.json files from every device (1st lane only in pipelined) Also, send them as META/<PROCNAME>/0 sporadic DPL output only once for the direct collection by the metadata writer (when it will be supported by the DPL).
shahor02
force-pushed
the
pr_conf2AODMDir
branch
from
July 28, 2026 19:22
48e1a14 to
c494919
Compare
With the option `--collect-config-files` provided, the AODProducer will collect the json dumps of ConfigParams made by the upstream processes and will add them as `<configName> : <configParam json>` TObjString pairs in the AOD metadata. Once the DPL supports collecting META/<PROCNAME>/0 sporadic inputs, the metadata will be created directly from these inputs, so this option will not be needed for the data processing. But in the case of MC, collecting json files via this option is the only way to add configs to the AOD metadata (as it is done in the sim_challenge.sh).
shahor02
force-pushed
the
pr_conf2AODMDir
branch
from
July 28, 2026 19:59
c494919 to
543e19d
Compare
Collaborator
|
Error while checking build/O2/fullCI_slc9 for 48e1a14 at 2026-07-29 05:18: Full log here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add all barrel tracking configurables to AOD metadata: write them as ConfigParam__.json files from every device (1st lane only in pipelined)
Also, send them as META//0 sporadic DPL output only once for the direct collection by the
metadata writer (when it will be supported by the DPL).
With the option
--collect-config-filesprovided, the AODProducer will collect the json dumps of ConfigParamsmade by the upstream processes and will add them as
<configName> : <configParam json>TObjString pairsin the AOD metadata.
Once the DPL supports collecting META//0 sporadic inputs, the metadata will be created directly
from these inputs, so this option will not be needed for the data processing.
But in the case of MC, collecting json files via this option is the only way to add configs to the AOD metadata.