Understand full stack of XRayPhysics
Open
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
What sort of rounding and conversion error is unavoidable (if any) at different levels of the XRayPhysics Python and C++ interfaces? Can we reproduce with a different backend?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by tracing the Python and C++ interfaces and their backend boundaries, then compare results across backends to identify rounding or conversion differences; done means documenting unavoidable error at each interface level and reproducing any backend-dependent discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100