rest-for-physics / rest-for-physics/rawlib
Implementation of a common `TRestRawSignalEventProcess` for rawlib
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Perhaps it would be interesting to define a TRestRawSignalEventProcess where input/output TRestRawSignalEvent types are encapsulated (similar to TRestAxionEventProcess), and thus the implementation of a TRestRawSignalEventProcess gets simplified.
On top of that we could add common metadata members for all rawlib processes that inherit from TRestRawSignalEventProcess such as fSignalRange.
Just an idea to be considered.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the proposed TRestRawSignalEventProcess with TRestAxionEventProcess and the existing rawlib processes that use TRestRawSignalEvent. Identify the common input/output handling and metadata such as fSignalRange, then define the set of processes covered and the tests needed to show that their behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100