90 likes | 98 Views
Background. Mission performance requirements for critical products and the need to keep operations costs low drive the need for automation. Historically, missions have, with low inheritance, developed unique capabilities to manage production of critical instrument products.
E N D
Background • Mission performance requirements for critical products and the need to keep operations costs low drive the need for automation. Historically, missions have, with low inheritance, developed unique capabilities to manage production of critical instrument products. • Development on a project specific system for Cassini (CDRS) was approximately 2.5 FTEs. • MER developed a similar system for 1.0 FTE.
What is MATIS? • MATIS – Multi-mission Automated Task Invocation Subsystem • A distributed data processing frameworkfor automated program execution. It is a workflow manager: • Execute programs in a specific order and under specific conditions • Synchronized program execution • Leveraging off lessons learned and skill sets from Cassini and MER, MATIS development over FY06-FY07 was approximately 2.0 FTEs. Adaptation effort varies from project to project, but it’s on the order of a couple months.
Radiometrically Correct Geometrically Correct Stereo Disparity 3-D XYZ Range MATIS - Phoenix Surface Normal Reachability Surface Rough Slope Maps Automated Generation of RDRs "Courtesy of D. Alexander"
The Operational Product Generation Subsystem (OPGS), part of the Ground Data System (GDS), is responsible for the generation of: - Experiment Data Records (EDR) for 6 instruments, including all cameras - Reduced Data Records (RDR) The higher level products, or the Reduced Data Records (RDR), are used for daily planning which has to be completed within very tight timing requirement. Timing requirements: - Produce and deliver the lowest level products, EDRs within 60 seconds - Produce higher imaging products, RDRs, within 30 minutes. Included in the RDRs, are some CPU intensive products which may take up to 5 minutes each. Phoenix Requirements
Phoenix Adaptation • Met all timing requirements • Phoenix pipeline - 40 parallel streams (including EDRs, RDRs, mosaic and terrain meshes) distributed among 4 machines (need not be distributed evenly) • Demonstration
MATIS Overview • Workflow Manager Framework • Provides common functionalities in the Core part, allowing the Adaptation effort to be small. • Core • Logging • Fail-safe capability • Automated parallel processing • Distributed processing • Load balancing • Execution of the programs • Interface definitions for the project specific modules • Scalable • Configurable • Adaptation • What to run • When to run • Where to run • How to run
MATIS Architecture Where? When? What? Database Scheduler Load Balancer Pipeline Design Process Definition (PD) RunTask RunTask RunTask Host c Host d Host e Process Definition (PD) Service Factory Service Factory Service Factory How? Host a Host b MATIS Persistent Store Controller Objects outlined in red are project-specific.
When is it Useful to use MATIS? • Processing high data volumes • Supporting rapid product turnaround • Distributing programs across multiple hosts • Keeping operational costs low • Automating steps that need to be repeated • Performing different tasks based on different conditions