1 / 15

Satisfying Requirements

Satisfying Requirements. BPF for DRA shall address: DAQ Environment (Eclipse RCP): Gumtree ISEE workbench integration; Design Composing and Configurability, Event Auditing: Audit trails for process network, Modifiable signal transfer mechanism; Anticipated outcomes:

elvis
Download Presentation

Satisfying Requirements

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. Satisfying Requirements • BPF for DRA shall address: • DAQ Environment (Eclipse RCP): • Gumtree ISEE workbench integration; • Design Composing and Configurability, • Event Auditing: Audit trails for process network, • Modifiable signal transfer mechanism; • Anticipated outcomes: • Design Composing with the UML 2.0 • probably using the ratified SysML 1.0;

  2. Satisfying Requirements • Other capabilities: • Heterogenous Component Libraries, using: • Processor “Wrapper” Components, • Composite Reduction Components, and • Java’s JNI; • Desirable: File Format import/export: • IO components for NeXus support; • Propagation of: • Type: Ports… • carry type and dimension properties, and • transfer only compatible Signals types; • Statistical Error: an algorithm property;

  3. Scientific Workflow • A method for automated problem solving; • Present at: • Scientific computing institutions and, • Corporations investing in process improvement; • Traditionally achieved through • “toolkits”, and • “environments”; • Kepler Project: for Scientific Workflows; Reference: “Scientific Workflows: Scientific Computing Meets Transactional Workflows”

  4. Computation Models • Ptolemy II realises: • Process design, • Concurrent simulation, and • Computation models; • Ptolemy II: Directors realise computation models;

  5. Kepler Project • Aim: An open-source system to address scientific workflow simulation; • Incorporates numerous scientific resources, • Collaborative, and • Large Component ontology: • Organised by scientific disciplines;

  6. Kepler Project Development • Contributors: • Ptolemy II framework project, • SEEK, • GEON, • EOL, • Resurgence, • ROADNet, …and many others; • Current release: Version 1.0(Beta); • Uses: Sun Java (revision 1.4) platform;

  7. Ptolemy II Framework • Aims: • Computation Model generation, and, • Concurrent simulation; • UC Berkeley developed: • Emerged out of Ptolemy research project; • Comprehensive, categorised collection components, • Aggregates other projects, • Extendable( e.g. Kepler extension ), and • Currently release: version 6.0 (Beta); Reference: Project Website FAQ(1. General);

  8. Ptolemy II Operation • Domain Interoperability, • Clustered Graph Models, • Composite and Atomic Entities and Ports: • Ports: • Typed enforceable, and • Token-passing; • Hierarchical Entities Executed using: • Container attribute: Director;

  9. Domains • Computation model simulation, or • Simulating Programmatic paradigms; • Ptolemy II “Directors” realise several: • Beta (Version 6.0): 20+ methods available: • traditional and experimental; • Kepler restricts to subset of 4: • Continuous, Discrete Time domains, • Processing Networks, and • Synchronous Data Flow; • Bragg Process Framework adopts: • Synchronous Data transfer: • Ports communicate a single signal;

  10. Historical Ptolemy • Developed at Faculty of Electrical Engineering and Computer Science, UC Berkeley (www.eecs.berkeley.edu); • Research: • Functional assembly of heterogenous computation models;

  11. Ptolemy II Facilities • Subprojects: • “Vergil”: • Graphical User Interface (GUI) framework, • Provides model manipulation and simulation control; • For SVG rendering: “Grid” (project) component; • “Plot”: a graphical plotting package; • “Copernicus”: • ‘Deep’ source generation: Java and ANSI C languages; • Recent additions: • Semantic system;

  12. DRA Requirements • Kepler addresses: • Algorithm Libraries: Actor Libraries *, • Configurability and portability: • Composable, Composite workflows, and • Model Persistence (MoML); • Execution control through Director “layers”: • Formulates “port firing schedule” per actor, and • SDF Domain Director suits Data Reduction;

  13. DRA Requirements • Is Kepler suitable? • NeXus Support: requires… • Actor development: adapt to NeXus File IO libraries, and • Usage of SRB Actors for structure retrieval; • Propagation of: • Type: • Directors evaluate IO Port token type criteria; • Errors: perhaps… • Algorithms export to “sink” actors for: storage and/or display; • Operational Errors: • Responsibility of Type Hierarchy and Directors;

  14. Ptolemy II Features (1/2) • External Process execution: • Applications and scripted languages; • Workflow integration of: • Heterogenous programming languages, and • Remote services: • Distributed processing: • Web Services (inc. service aggregation), • Grid computing architectures, • Distributed Storage: • Database connectivity; • Copernicus: C and Java (inc. Applets) Generation;

  15. Ptolemy II Features (2/2) • Under development: • KGrid (P2P): Previously designed to use : • Processing with distributed instances, and • Current platform: JINI;

More Related