JEventProcessorPODIO: remove EcalBarrelScFi*Pulses* from the default output - #2836
Merged
Conversation
wdconinc
reviewed
Aug 6, 2026
14 tasks
wdconinc
approved these changes
Aug 7, 2026
Contributor
Capybara summary for PR 2836
Last updated 2026-08-11T10:37-04:00 325ab76 |
mhkim-anl
approved these changes
Aug 11, 2026
wdconinc
force-pushed
the
pr/no_bic_pulse
branch
from
August 11, 2026 02:51
8511ba2 to
81e459a
Compare
wdconinc
enabled auto-merge
August 11, 2026 02:51
wdconinc
force-pushed
the
pr/no_bic_pulse
branch
from
August 11, 2026 13:00
81e459a to
325ab76
Compare
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
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.
Briefly, what does this PR introduce? Please link to any relevant presentations or discussions.
We enable most collections by default to exercise the underlying algorithms, and happy to provide those that are used by the analyzers. Unfortunately, these are quite large and not as useful. With #2732 and #2770 and other next changes coming up to provide the full functionality, we will soon have necessary components reengaged anyway, or so I hope.
What is the urgency of this PR?
What kind of change does this PR introduce?
Please check if any of the following apply