rest-for-physics / rest-for-physics/rawlib
Migrating TRestRawReadoutAnalysisProcess to detector library
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
This process is actually placed at the connectors library.
I believe it makes sense to migrate this process to the detector library. There would be a reason to prevent us from migrating this process to the domain of TRestDetector>?
If we are in the hypothetical scenario that we do not compile the raw library but we compile the detector library, this process will not be available. But if we are in the other scenario, raw library active, but detector library disabled, it will not be considered either.
But probably, we would be willing to have this process even if raw library was not compiled.
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 locating TRestRawReadoutAnalysisProcess in the connectors library and checking how the raw and detector libraries expose it. Review the detector library's TRestDetector domain and the build conditions for both libraries. Done means the process is placed in the appropriate detector-library location and remains available under the intended library configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100