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  September 2011

MASON-INTEREST-L September 2011

Subject:

Re: Lingering Steppable on Schedule after stopping Steppable

From:

Sean Luke <[log in to unmask]>

Reply-To:

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

Date:

Wed, 21 Sep 2011 17:29:41 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (53 lines)

You've got too many variables here for me to give a good answer.  So some hints and guesses:

schedule.scheduleOnce(schedule.getTime(), new Steppable() {
    public void step(SimState state) {
         // Stopping steppables in here
    }
}

Let's say that schedule.getTime() = t.  Then this code will stop any steppables scheduled for time t + epsilon and beyond.  However if a steppable is scheduled for time t it will still be stepped.

It's not clear what you mean by "stopping" the steppable in this context.  I presume it's scheduled repeating, so you're calling stop() on the Stoppable that was returned when you originally scheduled it.  Alternatively I suppose you could refer to having the Steppable wrapped in a TentativeStep and you're calling stop() on that.  Either way, just because you call stop() on the Steppable doesn't mean it's entirely deleted from the Schedule.  The object is dropped from the Schedule and can be garbage collected, but its outer wrapper (a TentativeStep or a Schedule.Repeat object) remains on the Schedule awaiting its final step() method, which will do nothing at all.

Since you mentioned Display2D I should remind you that visualization and GUI events should NOT be scheduled on the schedule but rather added to the "minischedule", part of the GUIState.  Make sure you're doing that.  Otherwise you won't be able to serialize models properly.  There's some discussion in the manual about this.

Last I'm wondering about when you're clicking on the objects -- I wonder if there's a fencepost error.  I suspect here's what might be happening.  When the GUISTate's step() method is called, it does the following:

	- call step() on all objects on the "before" minischedule  
	- advance the Schedule and step it
	- call step() on all objects on the "after" minischedule

The Display2D's step() method is scheduled on the "after" minischedule, and in the step() method it calls repaint(), which queues up a repaint event on the Swing event queue, along with your mouse clicks.  Thus at the time that your mouse clicks have any effect, the schedule has ALREADY stepped all Steppables which were scheduled for the current schedule time.  You should still be able to schedule for that time plus epsilon though. But instead of doing that, why not just call stop() from your mouse click?  You'd do it like this:

	synchronized(gui.state.schedule)  // so we're not modifying at the same time as the model
		{
		stop() all the objects of interest
		}

Anyway, that's all I can think of for now.

Sean

On Sep 21, 2011, at 4:01 PM, Sam Brett wrote:

> I am having a problem removing Steppables from the schedule dynamically. I
> am stopping them in an extension of the Display2D class which I called
> InteractiveDisplay2D where I can remove agents by clicking on the grid. But
> I find even when stopping these Steppables that they will linger on the
> schedule. For example, I am stopping them by means of:
> 
> schedule.scheduleOnce(schedule.getTime(), new Steppable() {
>     public void step(SimState state) {
>          // Stopping steppables in here
>     }
> }
> 
> I read that if you do a schedule once on the current time that the steppable
> will be put on the schedule at the current time plus epsilon. So I thought
> this should work as I will have always stopped the Steppables after they
> have executed and on the same thread. In that way, there should be no thread
> interference. But still I am having this problem. This must have something
> to do with the Display2D being on the event dispatch thread separate from
> the thread the schedule is operating on. I cannot understand why though,
> since I put the removal on the schedule itself.

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

June 2019
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