MASON-INTEREST-L Archives

March 2016

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
Mime-Version:
1.0
Content-Type:
text/plain; charset="UTF-8"
Date:
Tue, 22 Mar 2016 09:55:31 -0400
Reply-To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Subject:
Content-Transfer-Encoding:
8bit
Message-ID:
Sender:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
From:
Nick Malleson <[log in to unmask]>
Parts/Attachments:
text/plain (17 lines)
Hi all,

This might have an easy answer, apologies if I have missed something on the list.

I am using a GeomVectorField to store my agents. I need to be able to get back to the original Agent object, not just its associated MasonGeometry. I create agents and add them to the GeomVectorField a bit like this:

Agent a = new Agent();
agentGeomVectorField.addGeometry(a.getGeometry());
schedule.scheduleRepeating(a);

That basically works fine, but now I want to be able to get back to the underlying agent. I guess I could maintain a separate List of agents as well as the GeomVectorField, or I could add the agent to its MasonGeometry's userData field.

Any opinions on which would be best? How else have people stored their agents and their geometries using geomason?

Thanks in advance,
Nick

ATOM RSS1 RSS2