dataiku / dataiku/dss-plugin-osisoft
[feat] miss boundary_type when reading recorded data
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 1
- Avg merge
- 9h 33m
- Merged PRs (30d)
- 3
Description
When we want to read data in recorded mode from start_time to end_time, it is very useful to have the previous value of start_time and the next value of end_time to allow for interpolation. The Aveva Web API allows us to do this.
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
No file or test is named. Start by locating the recorded-mode data-reading entry point and review how the Aveva Web API exposes the previous value before start_time and the next value after end_time. Done means recorded reads include those boundary values for interpolation, with behavior covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100