NatLabRockies / NatLabRockies/H2Integrate
Resources: ability to handle different simulation time-steps (perhaps may require downsampling or upsampling)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 16
Description
Ability to handle different simulation time-steps (perhaps may require downsampling or upsampling)
Resources are generally handled on a per-hour basis.
Sometimes we may need more the ability to handle more fine or coarse resource data.
The river resource module has some examples of how we could handle this as it already re-samples data: https://github.com/NatLabRockies/H2Integrate/blob/main/h2integrate/resource/river.py#L112
Proposed solution
Alternatives considered
Additional context
Contributor guide
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 with h2integrate/resource/river.py around line 112, where resource data is already re-sampled. Trace how resource time-series inputs are represented and consumed, then determine the expected behavior for finer and coarser simulation time-steps. Done should mean resource data can be handled at non-hourly resolutions through appropriate re-sampling, with the behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100