Implement robust provenance and reproducibility
- Dominant language
- Python
- Stars
- 5
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
A config file fully specifies a simulation at the time it is used, but simulation parameters are typically changed on the fly (e.g., airmass, exposure time, source spectrum) so the input config file is not sufficient for specifying exactly how a simulation was run.
This issue is to develop a plan for providing more robust log of exactly how a simulation was performed with, ideally, the ability to reproduce a simulation after the fact.
This is not urgent, but something to start thinking about.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the config file and on-the-fly parameters such as airmass, exposure time, and source spectrum enter a simulation. Define what runtime state must be logged and how that record could support reproducing a past simulation; done means a concrete implementation plan exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100