rest-for-physics / rest-for-physics/rawlib
TRestRawSignalChannelActivityProcess dependencies with detector library necessary?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
This process depends on detectorlib through the TRestDetectorReadout. There is already a TRestDetectorChannelActivityProcess that might be replicating what is is being done at TRestRawSignalChannelActivityProcess. So, a question is if TRestDetectorReadout related routines at this process could be removed, and/or translated/migrated to TRestDetectorChannelActivityProcess.
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
Compare TRestRawSignalChannelActivityProcess with TRestDetectorChannelActivityProcess, starting with their TRestDetectorReadout-related routines and the detectorlib dependency. Trace where those routines are used and document whether they overlap; the work is done when the dependency and any migration or removal scope are agreed and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100