[amp-dev] Antwort: Better SD / AMF integration

[Urs Frei <urs.frei@xxxxxxx>]

Why the extra baggage?
For our very first steps with SD in
AMP we've used Agents, Attributes and Rules to model SD. No extensions
to AMP, to changes. Just pure AMP without SD plugins. It works. But it's
seens to us like workaround.

Our modelers are SD modelers. They don't
know Agent Based modeling. They need an easy workflow with the metaabm
model. The need model components like Stocks, Flows, etc. So adding an
Agent with Attributes and Rules just to represent a Stock or a Flow doesn't
seem like the way to go.

We wanted SD to be an extension to AMP
because Agent Based modelers probably don't want to bother with any SD
fragments. Only a modeler that has installed SD plugins is supposed to
see SD components in the metaabm editor.

When creating the extension point on
the metaabm model, we didn't want to create an extension __only__ for SD.
Who knows, one day someone might want to add a Discrete Event extension.
Or anything else. That's why the extension was created in a very generic
way. The extension (realized with a list of IAgentChild) is __not__ SD
specific. That's why we didn't want to call it "Dynamic Variables".
It's just a child of an Agent.

PS: As you know, Jonas and I are only
able to work frequently on AMP. Right now we're switching back to other
software development projects. So don't take it personally if we won't
respond as quickly as right now.




Von:      
 Miles Parker <milesparker@xxxxxxxxx>
An:      
 AMP developer mailing
list <amp-dev@xxxxxxxxxxx>
Datum:      
 05.07.2011 19:41
Betreff:    
   [amp-dev] Better
SD / AMF integration
Gesendet von:    
   amp-dev-bounces@xxxxxxxxxxx

---

I really need feedback on these. I'm pretty sure I
can make the SEIR model work just fine without all of the extra modeling
baggage, but there may be something I'm still missing here, because it
just doesn't seem that complicated to me:

1. Agents have state as quantities.
2. Those quantitates can change dynamically over time based on rates and
between quantities (sources and sinks).

I can't see why this doesn't fit in with the basic hierarchical AMF Action
design with some modifications. I know that I don't see anything semantically
in the example model that can't be represented in the existing AMF model
with some new Action additions. Check out ADiffuse for an example of how
that can work.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=350999
https://bugs.eclipse.org/bugs/show_bug.cgi?id=351000
_______________________________________________
amp-dev mailing list
amp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/amp-dev




________________________________________________________________

Urs Frei, Ingenieur FH
Wissenschaftlicher Mitarbeiter

Fon +41 71 226 12 22
Fax +41 71 226 12 13
Web http://www.fhsg.ch

FHS St.Gallen, Hochschule für Angewandte Wissenschaften
IMS-FHS |  Poststrasse 28 | Postfach 1664 | 9001 St.Gallen | Switzerland

FHO Fachhochschule Ostschweiz