You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of having their own .addAgent methods, Networks and Terrains, when constructed with an Environment, should just point their .agents array at the Environment's. Then when the Environment adds or removes Agents, they will automatically be synced to the helper in question.
In addition to updating the constructors, Environment's .addAgent and .removeAgent methods will need to be updated to do any cleanup/updates in the helpers (for example, if removing an Agent that has connections in the Network, remove those connections).
Since this will involve API changes, probably should go under a new major release 0.6.0.
The text was updated successfully, but these errors were encountered:
^ Pretty self-explanatory...
Instead of having their own
.addAgent
methods,Network
s andTerrain
s, when constructed with anEnvironment
, should just point their.agents
array at theEnvironment
's. Then when theEnvironment
adds or removesAgent
s, they will automatically be synced to the helper in question.In addition to updating the constructors,
Environment
's.addAgent
and.removeAgent
methods will need to be updated to do any cleanup/updates in the helpers (for example, if removing anAgent
that has connections in theNetwork
, remove those connections).Since this will involve API changes, probably should go under a new major release 0.6.0.
The text was updated successfully, but these errors were encountered: