Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bug in simulation main loop when constantTopology=False or runNetworkUpdate=True #2

Closed
ahrenberg opened this issue Nov 16, 2011 · 0 comments
Closed

Bug in simulation main loop when constantTopology=False or runNetworkUpdate=True #2

ahrenberg opened this issue Nov 16, 2011 · 0 comments
Assignees
@ahrenberg

Comments

@ahrenberg
Copy link
Contributor

There seems to be an error with copying graph information between iterations in the main loop if the network update is carried out, basically resulting in incorrect mean field values. This could also impact the constant topology or runNetworkUpdate=False in some cases.
@ghost ghost assigned ahrenberg Nov 16, 2011
ahrenberg added a commit that referenced this issue Nov 17, 2011
@ahrenberg
Fix of Issue #2 on github. Should now work also for non-constant topo…
2934581 
…logy processes.

   - Rewrote part of Simulation.execute so that the coping of graph attribute dictionary now is performed for all processes and cleaned up the read/write graph juggling.

   - Updated ExplicitStateProcess.deduce[Node/Edge]State so that it looks up the state dictionary using the get method instead of the [] operator. This yields None on a miss instead of an exception.

   - Also updated the docstring on constantTopology to more accurately describe the flag.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ahrenberg ahrenberg

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ahrenberg