2008
DOI: 10.1016/j.ecoinf.2007.02.002
|View full text |Cite
|
Sign up to set email alerts
|

Towards a structured approach to building qualitative reasoning models and simulations

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2009
2009
2017
2017

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 31 publications
(8 citation statements)
references
References 5 publications
0
8
0
Order By: Relevance
“…naturnet.org) and related models (Nakova et al, , 2007, the river Mesta model about dissolved oxygen behaviour has been implemented in the Garp3 workbench , following the framework for qualitative modelling presented in Bredeweg et al (2008).…”
Section: Model Implementationmentioning
confidence: 99%
“…naturnet.org) and related models (Nakova et al, , 2007, the river Mesta model about dissolved oxygen behaviour has been implemented in the Garp3 workbench , following the framework for qualitative modelling presented in Bredeweg et al (2008).…”
Section: Model Implementationmentioning
confidence: 99%
“…Qualitative simulation is one of effective tools to simulate complex and dynamic systems [1] [2][3] [4]. To make a decision and determine a strategy like a city planning, causal graphbased simulation is one of promising field to analyze without qualitative differential equations [5] [6]. Causal graph model has nodes showing factors in a system and arcs that is connecting with related nodes [7].…”
Section: Introductionmentioning
confidence: 99%
“…During this process the assumptions and features that are essential to represent a domain model are derived from the overall requirements. Within this context we define a planning domain model as follows: This is in line with terminology from general Knowledge Engineering, specific work on domain "theories" of physical systems [4], and what is called the "domain file" in the most common planning domain encoding language, PDDL [26]. In particular, we expect the language in which the domain model is written to have a well-defined syntax and operational semantics: this means that, independent of planner and domain, there is a defined process for executing plans which correspond to sequences of actions in the application domain.…”
Section: The Domain Model In Automated Planningmentioning
confidence: 99%
“…Domain models are often formulated into a planner input language directly from a requirements specification using only basic editors (these are so-called hand-crafted domain models), such as PDDL-studio [29] or the online editor PDDL editor 4 . In some cases, the requirements are encoded firstly into a more applicationoriented language such as UML in itSIMPLE [40], or in AIS-DDL in the KEWI interface [41], and then mapped into the target planner's input language.…”
Section: Model Qualitymentioning
confidence: 99%
See 1 more Smart Citation