Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What is the relationship between Kepler and Ptolemy?

Kepler ptolemy relationship
0
Posted

What is the relationship between Kepler and Ptolemy?

0

Kepler builds upon the mature Ptolemy II framework, developed at the University of California, Berkeley. Ptolemy II is a Java-based component assembly framework with a graphical user interface called Vergil. The Ptolemy project focuses on modeling, designing, and simulating concurrent, real-time, embedded systems. For more information about Ptolemy, please see http://ptolemy.eecs.berkeley.edu/ptolemyII/ptIIfaq.htm. Kepler inherits modeling and design capabilities from Ptolemy, including the Vergil GUI and workflow scheduling and execution capabilities. Kepler also inherits from Ptolemy the actor-oriented modeling paradigm that separates workflow components (“actors”) from the overall workflow orchestration (conducted by “directors”), making components more easily reusable. Through the actor-oriented and hierarchical modeling features built into Ptolemy, Kepler scientific workflows can operate at very different levels of granularity, from low-level “plumbing workflows” (that explicitly

0

Kepler inherits modeling and design capabilities from Ptolemy, including the Vergil GUI and workflow scheduling and execution capabilities. Kepler also inherits from Ptolemy the actor-oriented modeling paradigm that separates workflow components (“actors”) from the overall workflow orchestration (conducted by “directors”), making components more easily reusable. Through the actor-oriented and hierarchical modeling features built into Ptolemy, Kepler scientific workflows can operate at very different levels of granularity, from low-level “plumbing workflows” (that explicitly move data around, start and monitor remote jobs, for example) to high-level “conceptual workflows” that interlink complex, domain-specific data analysis steps. Kepler extensions to Ptolemy include an ever increasing number of components aimed particularly at scientific applications, e.g., for remote data and metadata access, data transformations, data analysis, interfacing with legacy applications, Web service invoc

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.