lincc-frameworks / lincc-frameworks/ponder
Ability to control how/when Ponder handles changed orbits
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Instead of a machine-precision hash, we should let the user specify what warrants a re-run.
Contributor guide
No contributing guide indexed for this repository
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 tracing how Ponder currently detects changed orbits and where the machine-precision hash triggers a rerun. Define the user-facing control for deciding what warrants a rerun, including how and when it is applied. Done means the behavior is configurable rather than fixed to the machine-precision hash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100