|
From: Nick C. <nic...@ve...> - 2002-01-09 13:34:10
|
I don't think Tom's post made it to the list. Nick -----Forwarded Message----- > From: Thomas Howe <th...@sr...> > To: nic...@ve... > Subject: Re:[Repast-developer] aspectj and movement > Date: 08 Jan 2002 10:05:35 -0600 > > Hi all, > I seem to be still having problems getting emails from my machine to actually post to the list. > > In anycase, Nick, I've been working on the problem of eliminating the spatial reference from the agent. As I have written it, the only reference is in the constructor, and it is as an Object. I handle all the casting in the aspect. Basically, I introduce a method on the class called setWorld(Object world). Beyond that, the code is completely free of any reference to the space. I now have a method move(Point old, Point new) that handles the movement. > > this is the interface for MoveableAgent: > > move(Point old, Point new) > > Vector getNeighbors(Point loc, int xExtent, int yExtent); > > Object getObjectAt(Point loc); > > setWorld(Object world); > > > There are more methods, mostly overloaded ones, that handle other things, and a few private methods, but this should give an idea of what I mean by space independence. One concern is specialty spaces like heatspace. This space has methods like diffuse that we cannot account for in the aspect(of course, I can for heatspace, but generally I cannot). This would still require either a reference to the space or to be handled in the model. I think. If anyone has any thoughts, that would be cool. > > -Tom |