Skip to content

fix: identify sparse ROOT detector entries - #197

Open
zhaozhiwen wants to merge 1 commit into
gemc:mainfrom
zhaozhiwen:fix/189-root-event-keys
Open

zhaozhiwen wants to merge 1 commit into
gemc:mainfrom
zhaozhiwen:fix/189-root-event-keys

Conversation

@zhaozhiwen

Copy link
Copy Markdown
Collaborator

ROOT detector trees had no event join keys.

Write single-element vector g4localEventNumber and threadID metadata on event detector entries; reject reserved detector-variable names. Run-only schemas remain unchanged.

Validation: Real simulation joins against JSON plus deterministic sparse banks, late hits, rejected digitization, two worker IDs, collision rejection and run schema. Regression failed against the original implementation and passed with the focused fix. Combined source build/install and all 44 affected regressions passed. The 32-example sweep retained its 19/32 baseline with no new failing examples.

Closes #189.

Verification on 2026-11-15: all 44 selected affected regressions passed again on the combined nine-fix source. Each issue also has a separate failing-original/passing-fixed regression. These PR branches each contain only their own fix; shared-file conflicts may need resolving as other fixes merge. No clean full-project-suite claim: the broader source-example baseline remains 19/32, with no newly failing examples in the combined sweep.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ROOT detector trees lose event association when an event has no detector hit

1 participant