Update BDI agent attributes about ees HOT 4 CLOSED

Unfortunately there is no way to do that last one. A MATSim activity tag like this one <activity type="beach" x="794920.60169" y="5772690.71159" end_time="16:02:00" /> cannot have a description assigned to the type. The only way to say that beach is Anglesea Beach for intance, is via some attribute tag like beachDescription but that would not be a good idea as it would be easy to mess this up if one tag is updated and not the other.

from ees.

Parameters getProbHomeAfterDependents() and getProbHomeBeforeLeaving() are now exposed as of f8222a4. See below:
https://github.com/agentsoz/bdi-abm-integration/blob/f8222a474ce91025a2c29880bd8d33ec2555fd35/examples/bushfire/scenarios/surf-coast-shire/population-subgroups-sample/scenario_matsim_plans.xml#L43-L44

@osbornejr you can now adjust these as needed for the hand-crafted test SurfCoastShirePopulationSubgroupsSampleTest.

from ees.

From @osbornejr on August 23, 2018 5:39

Thanks. I am thinking with getProbHomeAfterDependents() and getProbHomeBeforeLeaving() that they should not be a probability for each agent, but a true/false condition which is determined during attribute assignment based on some overall probability for their subgroup type.

They could even be collapsed into one attribute WillGoHome, because the first one only applies to those with dependents, who do not have the later option of going home before leaving. Ultimately all agents will only use this variable once in their decision tree.

It would be good to avoid having any non-determined variables within the <attributes> field for an agent, and instead leave the probabilistic aspects to the global/subgroup level. Otherwise you have a random assignment of the variable to the agent, and another random choice when the agent has to apply that variable (a kind of double decision). It will make testing/validation more difficult down the track.

The only time it would be good is in cases where for a given agent, consistency is explicitly not desired. Is this the case the decision is only used once, so it should only be used once.

This is achievable now by just setting these variables to 1.0 or 0, but down the track I think it could be consolidated to one, deterministic attribute?

from ees.

Yes that is a much better scheme @osbornejr. Have now implemented what you suggested in agentsoz/bdi-abm-integration@db4cd19. Now looks like this.

from ees.