Concurrency can introduce additional randomness to a model's execution due to the non-determinacy of the arrival order of messages. As Frank points out this can be a problem (but not for all models). With effort one can have the system know which computation orders are a problem and which ones are not. There is a nice discussion of this in A Distributed Platform for Global-Scale Agent-Based Models of Disease Transmission <http://dl.acm.org/citation.cfm?id=2043637> by Parker and Epstein.
-ken On 5 February 2015 at 11:39, Frank Duncan <[email protected]> wrote: > To be honest, we haven't done a lot of thought on concurrent > functioning, mainly because reproducibility is useful in both > experiements and debugging. Between that and the fact that the legacy > code would take a lot of work to upgrade to a different architecture > means we probably wouldn't attack this problem any time soon. > > Thanks for the suggestion! > > Frank > > > On Sat, Jan 24, 2015 at 08:51:34AM -0800, [email protected] wrote: > > Have you considered using Akka for concurrent functioning of agents in > NetLogo? > > > > If yes, what are the pitfalls of this approach to concurrency? > > > > -- > > You received this message because you are subscribed to the Google > Groups "netlogo-devel" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "netlogo-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "netlogo-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
