NetLogo / NetLogo/NW-Extension
Dealing with custom contexts is awkward
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 66
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
As long as you stick to breed-set based contexts, the nw primitives mix nicely with the netlogo ones. However, when you switch to static agent-set based contexts, thinks get more difficult. For instance, to the degree of a node, you first have to have a reference to the link-set of the context and then do count my-links with [ member? self nw-links ]. This is pretty awkward. One solution would be to provide primitives that mirror the built-in primitives, but relative to the context. For instance:
nw:nodes- turtle-set of the nodes in the networknw:links- link-set of the links in the networknw:my-links(and variations thereof) - links connected to caller
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 by reviewing the existing network-extension primitives for breed-set and static agent-set contexts, then compare them with the corresponding NetLogo primitives. Done means defining and implementing an agreed set of context-relative primitives, including node, link, and caller-connected-link operations, with behavior clarified for the listed variations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100