NetLogo / NetLogo/NW-Extension
nw:weak-component-clusters not following seed?
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 66
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
When I run a netlogo code with nw:weak-component-clusters in it, it returns the components in a different random order each time, even when random-seed is specified. I've tried with netlogo 5.1.0, 6.1.0 and 6.2.2 and two different machines, but the problem persists.
extensions [nw]
to setup
clear-all
random-seed 5
create-turtles 1000
ask turtles [create-link-with one-of other turtles]
print (nw:weak-component-clusters)
end
, for example will sometimes print '[(agentset, 2 turtles) (agentset, 15 turtles) (agentset, 59 turtles) (agentset, 4 turtles) (agentset, 920 turtles)]', sometimes '[(agentset, 2 turtles) (agentset, 920 turtles) (agentset, 15 turtles) (agentset, 59 turtles) (agentset, 4 turtles)]', sometimes '[(agentset, 15 turtles) (agentset, 59 turtles) (agentset, 920 turtles) (agentset, 4 turtles) (agentset, 2 turtles)]' etc. Any idea what could be causing this?
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
Run the provided NetLogo example with nw:weak-component-clusters repeatedly using random-seed 5, then inspect the implementation of that primitive in the NW extension. Done means the component list has stable ordering across repeated runs with the same seed, with tests or updated behavior confirming the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100