Skip to content

Tkuma timeframe splitting #1916

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

Open
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

11kumaoka
Copy link

Briefly, what does this PR introduce?

What kind of change does this PR introduce?

  • [O] Bug fix (issue #__)
  • [O] New feature (issue #__)
  • Documentation update
  • Other: __

Please check if this PR fulfills the following:

  • [O] Tests for the changes have been added
  • Documentation has been added / updated
  • Changes have been communicated to collaborators

Does this PR introduce breaking changes? What changes might users need to make to their code?

Does this PR change default behavior?

nathanwbrei and others added 14 commits June 12, 2025 10:59
JANA2 is moving away from the JEventSource(std::string resource_name, JApplication*) constructor because it doesn't play nicely with injected JApplications. Instead, we use the newer, simplified JEventSource constructor, and move the JEventSourcePODIO parameter registration out of the constructor and into the Init() callback where it anyhow belongs.
This is so that we can use CI to test that reconstruction isn't changed in the case when timeframe=physicsevent.
### Briefly, what does this PR introduce?
1. Implement simple time split algorithm in the timesplitter.
2. Create a new factory to align hit time.

### What kind of change does this PR introduce?
- [ ] Bug fix (issue #__)
- [O] New feature (issue #__)
- [ ] Documentation update
- [ ] Other: __

### Please check if this PR fulfills the following:
- [O] Tests for the changes have been added
- [ ] Documentation has been added / updated
- [O] Changes have been communicated to collaborators

### Does this PR introduce breaking changes? What changes might users
need to make to their code?

### Does this PR change default behavior?

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants