Cache is still used even when `wind-up` configuration inputs change
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 29
- Forks
- 11
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 11
Description
Example
A user has run a wind-up analysis. As part of this analysis, a preprocess.pickle will be created and saved to local cache. The user amends some wind-up configuration inputs (eg amends exclusion_periods_utc on the WindUpConfig) and re-runs the analysis. Currently, the preprocess.pickle cache will be used even though the user inputs have changed, therefore not updating the analysis with the user's new inputs.
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
Trace how WindUpConfig inputs, including exclusion_periods_utc, are used when preprocess.pickle is written to and read from the local cache. Re-run the analysis with changed configuration values and verify that stale preprocessing data is not reused and the analysis reflects the new inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100