openclimatefix / openclimatefix/pvnet
Use start and end intervals, rather than history and future
Open
Nobody has claimed this yet.
ocf-internal
- Dominant language
- Python
- Stars
- 60
- Forks
- 50
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 2
Description
Detailed Description
Use start and end intervals, rather than history and future
Context
- currently using history and future minutes
- will help to clarify about if it includes t0 or not - see openclimatefix/ocf-data-sampler#326
Possible Implementation
- change in ocf-data-sampler
- change in pvnet + migration script for HF
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 the interval handling in ocf-data-sampler and the corresponding pvnet code, then inspect the migration script for HF. Confirm how history and future minutes are represented and identify every affected interface; done means the sampler, pvnet, and migration path consistently use start and end intervals with clarified t0 behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100