Update workflow for timeseries and summary generation to regard user preferences within configuration file
- Dominant language
- Python
- Stars
- 3
- Forks
- 1
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
Current workflow currently takes all available data for timeseries and summary processing, regardless of if configuration file is marked to process for a given time period. Include checks when generating timeseries to heed to the "processing" entry in the configuration file.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the workflow that generates timeseries and summary data, then inspect how it reads the configuration file and its "processing" entry. Confirm the current behavior with available tests or a small configuration example; done means periods not marked for processing are excluded from both generation paths.
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
- 38/100