2009
DOI: 10.1002/int.20391
|View full text |Cite
|
Sign up to set email alerts
|

The design and application of structured types in Ptolemy II

Abstract: Ptolemy II is a component-based design and modeling environment. It has a polymorphic type system that supports both base types and structured types, such as arrays, records, and unions. This paper presents the extensions to the base type system that support structured types. In the base type system, all the types are organized into a type lattice, and type constraints in the form of inequalities can be solved efÞciently over the lattice. We take a hierarchical and granular approach to add structured types to … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2011
2011
2018
2018

Publication Types

Select...
2
2

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 15 publications
0
4
0
Order By: Relevance
“…We would like to mention in particular stochastic hybrid automata (SHA) [35] or at a lower semantic level Tag machines [10]. Another line of interesting work is on heterogeneous composition, in particular Metropolis [8], Ptolemy [43] or BIP [9]. There is also some work with a similar motivation as ours, where unifying models explicitly address viewpoint integration.…”
Section: Viewpoint Compositionmentioning
confidence: 98%
“…We would like to mention in particular stochastic hybrid automata (SHA) [35] or at a lower semantic level Tag machines [10]. Another line of interesting work is on heterogeneous composition, in particular Metropolis [8], Ptolemy [43] or BIP [9]. There is also some work with a similar motivation as ours, where unifying models explicitly address viewpoint integration.…”
Section: Viewpoint Compositionmentioning
confidence: 98%
“…design rules, which are defined and checked by the component based design framework. While this tailoring may support complex type systems, as e. g. the polymorphic and structured types [12] in Ptolemy II , it lacks flexibility w. r. t. defining viewpoint-specific compatibility and refinement rules, meaning constraints on how these types can bottom-up be constructed resp. top-down refined, checking value-, causality-and time-aware construction rules.…”
Section: Related Workmentioning
confidence: 99%
“…Naturally, we can model default values in ArcGIS Geoprocessing tools as PortParameters and associate them with ParameterPorts. Another useful feature in Ptolemy II is its type checking system that allows determining structural compatibility among ports [39]. For example, if the output of port has a string type while its connecting regular input port requires an array of strings then an error can be reported to identify potential problems in workflow design.…”
Section: Ptolemy II For Workflow Applications: An Overviewmentioning
confidence: 99%