MASON-INTEREST-L Archives

February 2014

MASON-INTEREST-L@LISTSERV.GMU.EDU
Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Date:
Thu, 27 Feb 2014 09:27:06 -0500
MIME-version:
1.0 (Mac OS X Mail 7.2 \(1874\))
Reply-To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Content-type:
text/plain; charset=iso-8859-1
Subject:
Re: How agents are chosen
From:
Sean Luke <[log in to unmask]>
In-Reply-To:
<[log in to unmask]>
Content-Transfer-Encoding:
8bit
Parts/Attachments:
text/plain (8 lines) 
On Feb 27, 2014, at 8:42 AM, Megan Olsen <[log in to unmask]> wrote:

> so if I want to use this functionality, it looks like I need to reinvent it each time in each language.

I understand the convenience factor: indeed I think that NetLogo has some mechanism built-in to help you in this way.  But it is NOT a good idea to have this built in: easy parallel synchronicity encourages very sloppy thinking on behalf of model-designers.  You get race-condition questions like: why is my object O gone from the field?  Not realizing that agent A put object O in position P and simultaneously agent B put object Q in the same position, overwriting it, because neither had a chance to see that the other was placing something in position P.  This is a _bad_ idea.

Sean

ATOM RSS1 RSS2