ts-get-interp causes runtime error when input time is at/near start of time series

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
scala
Domain
documentation

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.

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.

Dominant language
Scala
Stars
8
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NetLogo/Time-Extension

All issues in NetLogo/Time-Extension

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.