1 / 6

Model Design Alternatives for Supporting Object Conversion in Complex Type Hierarchies

Explore alternatives for supporting object conversion in complex type hierarchies and the consequences of converting objects in different systems. Discover possible problems and challenges, such as asymmetric conversions and preserving object type history. Compare alternative designs based on ease of use, extensibility, support for data-intensive modeling, real-time models, and other factors. Includes examples in Java (Repast), C# (Terrarium), and NetLogo.

dmontes
Télécharger la présentation

Model Design Alternatives for Supporting Object Conversion in Complex Type Hierarchies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Model Design Alternatives for Supporting Object Conversion in Complex Type Hierarchies Brian Lawler Santa Fe Institute Complex Systems Summer School June 2007

  2. Why Study Object Conversion? In an economic system, we do expect there to be Employee objects that will convert from Part-time Worker to Full-Time Worker. In a biological system, we do not expect a Human to convert to a Fish.

  3. What are the consequences? • Typical model conversion process: • Create a Part-Time object • Copy data from Full-time object to the Part-Time object • Name • Date of Birth • etc. • Destroy the Full-Time object • Use the Part-Time object • Possible Problems: • During the conversion process, there are both a Full-Time and Part-Time which is not an accurate count of the participants in the system. • This conversion process is slow in most modeling environments and may not proceed appropriately relative to other events in the model – e.g. killing off the agent object as part of an epidemic model.

  4. What are some possible alternatives?

  5. Person Taxpayer Person MarriedFiling Separately Single Filer MarriedFiling Jointly Prisoner Susceptible Infected Felon Recovered What are some other challenges? Asymmetric Conversions Preserving Object Type History Hierarchies Supporting State Models

  6. Basis for Design Alternative Comparisons • Ease of use and intuitive understandability by the subject matter experts • Extensibility for subsequent model enhancements • Ability to support data-intensive modeling and collection activities • Suitability for “real-time” models and system behaviors • Ability to support behaviors allocated at multiple scales of the system • Risks of introducing errant behaviors • Tools and language examples – Java (Repast), C# (Terrarium), NetLogo, etc.

More Related