MASON-INTEREST-L Archives

October 2004

MASON-INTEREST-L@LISTSERV.GMU.EDU

Options: Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

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

Print Reply
Subject:
From:
Tony Bigbee <[log in to unmask]>
Reply To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Date:
Tue, 5 Oct 2004 11:13:18 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
Thanks Rob and Keith for the suggestions.  If the Stoppable.stop()
method actually does remove the agent from the schedule, that would
seem to be ideal.

Keith ---I don't know how computationally efficient dynamically adding
the living agents each step is, but it seems live a clever approach.  I
hadn't considered resurrection, but it's a good thought.  The float
value used in your sample might be an issue to due to floating point
accuracy/resolution issues, but I also note that there is no
scheduleOnce method signature that takes a float for the time.  There
is some discussion in the javadoc about real-valued time steps (as
doubles) via the toReals() and fromReals() methods, but caution is
recommended --"You have to be careful using a real-valued schedule."

Tony

On Oct 5, 2004, at 9:57 AM, Keith Sullivan wrote:

> Another potential solution is to use the scheduleOnce method.  In the
> step() method of your agents, you could test if they are alive on the
> current time step.  If so, then run
>         scheduleOnce(state.schedule.time()+1.0f, this)

ATOM RSS1 RSS2