LISTSERV mailing list manager LISTSERV 16.0

Help for MASON-INTEREST-L Archives


MASON-INTEREST-L Archives

MASON-INTEREST-L Archives


MASON-INTEREST-L@LISTSERV.GMU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MASON-INTEREST-L Home

MASON-INTEREST-L Home

MASON-INTEREST-L  August 2007

MASON-INTEREST-L August 2007

Subject:

Re: Access to schedule from ParallelSeqence

From:

"Maciej M. Latek" <[log in to unmask]>

Reply-To:

MASON Multiagent Simulation Toolkit <[log in to unmask]>

Date:

Thu, 9 Aug 2007 23:18:29 -0400

Content-Type:

multipart/mixed

Parts/Attachments:

Parts/Attachments

text/plain (110 lines) , Schedule.java (110 lines)

First of all, thanks to Professor Luke for help.

1) A modified by Professor Luke version of Schedule is attached, If I
recall correctly, the major changes happend in the step method, with
minor revision of a number of ScheduleOnce(*) and ScheduleRepeating(*)
variants.
2) This version allows for calling schedule.time() (and
schedule.getSteps()) method from Steppables called from inside the
ParallelSequence.

Summarizing other possible workarounds of this problem:

3) To have the time available from the ParallelSequence using
unmodified MASON engine, one may extend the Steppables to have a time
field and use wrapper to set it before ParallelSequence get's called:

Xagent implements Steppable ..... {
double time;
}

and in the SimState start() method have something along following lines:

final Steppable parallelWrapper = new Steppable() {
public ParallelSequence agentSequence;
public void step(SimState state) {
for (int i=0; i < agentSequence.steps.length; i++) {
	((Xagent) agentSequence.steps[i]).timer = state.schedule.time();
}
agentSequence.step(state);
}
};
schedule.scheduleRepeating(parallelWrapper);

assuming proper initialization of agentSequence, the time field will
have the same value as the one received should calls to
schedule.time() be allowed (same hold for getSteps()).

4) If scheduling events from inside the ParallelSequence is necessary,
one may find helpful similar wrapper that buffers things to add and
adds them en masse after internal ParallelSequence has finished.

Regards

Maciek




On 8/9/07, Sean Luke <[log in to unmask]> wrote:
> I have given Maciej a revised version of Schedule which allows any
> arbitrary thread to query the current time() and getSteps() [read-
> only methods] but not write to the Schedule.  This satisfies Maciej
> for the moment, but it's slightly less efficient (up to two extra
> synchronizations per schedule step) which makes me Unhappy.
>
> I could go three ways here: (1) keep the Schedule as-is, (2) include
> the revised methods, which are helpful for parallel people but less
> efficient, or (3) push forward and make it possible to schedule stuff
> on the Schedule even if you don't have a lock on it.  That'd be a bit
> less efficient still, but it might be worth it in terms of
> helpfulness to parallel folks.
>
> Sean
>
> On Aug 9, 2007, at 6:42 PM, Sean Luke wrote:
>
> > The reason for this is fairly simple: the parallel sequence's step
> > call (in which you're trying to make these calls) is made from an
> > outer call to Schedule.step().  This outer call is synchronized on
> > the schedule.  However, also state.schedule.time() and
> > state.getSteps() are also synchronized on the schedule, and your
> > inner parallel sequence threads thus don't have access to it until
> > the main thread  exits from Schedule.step().
> >
> > This is clearly a stupid error in MASON's schedule: let me Ponder
> > Deeply upon it.
> >
> > Sean
> >
> > On Aug 9, 2007, at 6:27 PM, Maciej M. Latek wrote:
> >
> >> Dear MASON team,
> >>
> >> I have a number of agents being stepped by ParallelSeqence facility.
> >> For most of the time it runs smoothly. Nevertheless,  I got into a
> >> minor problem when trying to query the schedule for time: any
> >> reference to state.schedule.time() or getSteps() causes a deadlock. I
> >> have tried putting it as a synchronized call with locking on schedule
> >> and simulation, I tried adding a synchronized function to SimState
> >> that would return me that information, always with the same result.
> >>
> >> Is it possible to access schedule when agent is stepped of the
> >> ParallelSequence at all without causing deadlocks? Or is
> >> ParallelSequence locking the schedule?
> >>
> >> Above mentioned issue is more of theoretical significance for me:
> >> as I
> >> need just coarse approximation of the number of steps from
> >> schedule, I
> >> update agents with this information just before the ParallelSequence
> >> is stepped.and avoid querying the schedule. I would love to know the
> >> answer for potential future developments though.
> >>
> >> Regards
> >>
> >> Maciek
> >
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
October 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
September 2017
June 2017
May 2017
March 2017
February 2017
January 2017
December 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
February 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
July 2004
May 2004
April 2004
March 2004

ATOM RSS1 RSS2



LISTSERV.GMU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager