NetLogo / NetLogo/Time-Extension
Bug: Nothing named TIME:TS-LOAD has been defined
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I have been trying to run a NetLogo simulation model but the time extension doesn't seem to work as intended. I am using the NetLogo 6.4 version on my mac OS Monterey.
The problem is that the commands time:ts-load gives the error "Nothing named TIME:TS-LOAD has been defined".
I have followed the instructions under Time Series Utilities from https://ccl.northwestern.edu/netlogo/docs/time.html. However, the link to the Time-Extension/time-series.nls shows 404 - page not found. Due to this I searched for the time-series.nls and found it under Time-Extension/src/time-series.nls instead. I downloaded it and added it to my directory where the .nlogo is located. I also added __includes [ "time.series.nls" ] in the top of the code. I also have the extensions [time table Csv rngs]. Unfortunately this did not remove the error.
I did not know where to reach out for help - so I though I could post it as an Issue here.
Pictures to show the issue:
All help is very much appreciated!
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 with Time-Extension/src/time-series.nls and the Time Series Utilities documentation linked in the report. Reproduce the error in NetLogo 6.4 using the linked supermarket model and its time:ts-load call, then check whether the documented include path and filename match the repository file. The issue is resolved when the command is recognized without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100