NetLogo / NetLogo/Time-Extension
ts-get-interp causes runtime error when input time is at/near start of time series
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Using ts-get-interp with a time equal to, or soon after, the first time in the time series object raises a runtime error in to-report __col-of-row [columns row col-name]; the error is "ITEM expected input to be a string or list but got NOBODY instead."
Tracing this back through __interp, I am guessing the problem has to do with ts-get-before-and-after sometimes returning NOBODY...
The documentation for ts-get-interp needs to say what happens when you try to interpolate using a time not between the beginning and end of the time-series.
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
Reproduce the boundary cases for ts-get-interp, then trace __interp and ts-get-before-and-after to confirm how NOBODY reaches __col-of-row. Review the extension documentation for interpolation behavior outside the time-series range; done means the runtime behavior is understood and the documented boundary behavior matches it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100