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

MASON-INTEREST-L June 2015

Subject:

Re: Anyone using Factory design pattern for agents?

From:

Christian Meyer <[log in to unmask]>

Reply-To:

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

Date:

Mon, 29 Jun 2015 13:22:13 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (92 lines)

Using an entity component system (ECS) might be suitable for you. It is 
similar to the strategy pattern but any combination of "strategies" is 
possible and also saving state along with them.

Each agent is an entity which is nothing more than a set of components 
(representing state). A factory class is used to create entities with 
the needed component sets. During each step systems (representing logic) 
will update the entity by changing its components. For example, a 
ReproductionSystem will look for a certain subset of components needed 
for reproduction and only update agents who have this subset. To give an 
agent the ability to reproduce, just add the needed components and you 
are done.

This is a simple ECS which I changed for MASON. Some work was needed to 
integrate it into the schedule.
https://github.com/adamgit/Entity-System-RDBMS-Beta--Java-

Best regards,
Christian

On 29.06.2015 03:23, Russell Thomas wrote:
> Is anyone using the “Factory” design pattern to construct agents at run
> time? I am about halfway down this path and I’d love to learn from
> anyone else who has experience with this approach. (See “Difficulties”
> below)
>
> Requirements
> ------------------
>
> The setting is modeling teams and organizations engaged in design (of
> artificial products), innovation (in how they do design), and
> qualitative learning (i.e. learning new skills, not just getting better
> at existing skills).  In other words, I’m modeling endogenous innovation
> involving genuine novelty.  My agents are (somewhat) cognitive and
> adaptive, particularly in their ability to acquire or develop novel
> capabilities during the course of a simulation run. Also I’d like to
> experiment with a wide variety of initial conditions regarding agent
> types and capabilities.  In essence, what I’m looking for is agents that
> are dynamic bundles of capabilities (i.e. resources, action rules, etc.)
> rather than fixed capabilities as is the norm in most ABMs.
>
> Approach
> -------------
> These requirements suggest the use of a “Factory” design pattern (see
> https://en.wikipedia.org/wiki/Factory_method_pattern for general
> description).
>
> During start( ), the /AgentFactory /is an object that takes as input
> specifications for the agents (i.e. list of capabilities) and also other
> key objects (i.e. environment objects such as /SimState/).  The
> /AgentFactory /class includes various pre-built templates and objects to
> produce an agent object of the specified type.  (I have a large library
> of capability and processing objects.)  Actions to be performed by agent
> at each time step is specified by a special-purpose language that
> describe sequences of tasks and their interdependencies. (Execution is
> by a simple O-O stack machine.)  Each task execution records its
> results, and these results can be concatenated and logged in a file.
>   Essentially, agents can “explain” what they did and why each step.
>   This is useful for both debugging and also as experimental results.
>
> Clearly, this approach does not result in fast execution and would not
> be suitable for a large population of agents and long simulation runs.
> My simulations will involve tens or at most a hundred agents, so it
> won’t be a problem for me.
>
> Difficulties
> --------------
> Where I’m running into difficulty is in *software design decisions*: 1)
> how general-purpose to make the code, and 2) how to avoid unnecessary
> complications.  The advantage of making it fully general-purpose is that
> it will (later) reduce the design and debug time for specific ABM
> designs.  The disadvantage is that it takes more time now for thinking,
> planning, coding, and testing (e.g. debug capabilities for the
> special-purpose stack machine).
>
> In pursuit of general functionality, I am probably making the software
> design too complicated.  It would be nice to see what other people have
> done and maybe learn from their experience.
>
> Also, I want to use built-in capabilities of Java and also available
> Java libraries.  For example, when I get to the point where agent
> specifications will come from a text file, I’ll probably use ANTLR to
> parse my special-purpose task language.  But I might be unknowingly
> “recreating the wheel” in many cases by creating my own classes for
> various low-level functions.
>
> Thanks,
>
> Russell Thomas
> Computational Social Science
> George Mason University

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

November 2021
May 2021
April 2021
March 2021
February 2021
August 2020
July 2020
June 2020
February 2020
August 2019
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