NetLogo / NetLogo/Python-Extension
Add ability to pass agents to python
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 31
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I think they should be represented as dict-like objects, where keys are agent variables.
For a first pass, they should be read-only.
One tricky thing is keeping them in sync with NetLogo. For instance:
py:set "t" turtle 0
ask turtle 0 [ set color red ]
print py:runresult "t['color']" ;; This will be out of date
I think just not caring is good enough for a first pass, as long as it's clear in the docs. Otherwise, we'd have to track and sync all agent-objects on every call, which sounds awful.
I think they should be represented as dict-like objects, where keys are agent variables.
For a first pass, they should be read-only.
One tricky thing is keeping them in sync with NetLogo. For instance:
py:set "t" turtle 0
ask turtle 0 [ set color red ]
print py:runresult "t['color']" ;; This will be out of date
I think just not caring is good enough for a first pass, as long as it's clear in the docs. Otherwise, we'd have to track and sync all agent-objects on every call, which sounds awful.
Copied from https://github.com/qiemem/PythonExtension/issues/2
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 files or tests are named. Start by tracing the existing py:set and py:runresult behavior, then define how agent variables become read-only dict-like Python objects. Done means agents can be passed to Python and the documentation clearly states that values may become stale after NetLogo changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, scala
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100