Closed dhixsingh closed 6 years ago
Further to this, it would be good if in the MATsim population file the attribute indicated which type of BDIagent the agent should be. Like BDIagent='Resident', BDIagent='Responder' etc. In this format, an agent that doesn't need a BDI correspondant could have attribute BDIagent='null'.
@osbornejr, yes likely we want more than one attribute and the ability to add more as we need them. Seems we could do something like this:
<person id="0">
<attributes>
<attribute name="BDIAgentType" class="java.lang.String" >io.github.agentsoz.ees.agents.Resident</attribute>
</attributes>
<plan selected="yes">
...
</plan>
</person>
Added a test AttributesInPopulationTest
which should explain this. Let me know if you have questions.
@kainagel, is AttributesInPopulationTest
not pushed maybe? I can't see it yet.
@kainagel thanks, AttributesInPopulationTest
is there now since 845fc54442933312649711ea0d887eb296421365. Yes that's all we need, I can take it from here.
Available since 71ae240. Example input is:
And further below:
Currently, the way BDI agents are specified for EES is a bit messy.
<bdiagents>..</bdiagents>
tag that gives a count of BDI agents also exists in the main scenario file (see Maldon600 example here), that seems to be used in a crude way.What we would like is this:
isBDIAgent=true
. @kainagel could you point us to info on how to set this up?One issue with doing this is that at the moment we do not have an explicit map from MATSim population IDs to Jill IDs so this will need to be setup first (raised #14 for this).