60 likes | 73 Views
Learn about the collaborative effort between SNS and APS in developing the IRMIS approach for control system engineering. Explore the minimalist, scalable, and extensible relational database schema with a site-neutral and user-friendly interface. Witness the recent progress, including PV crawler development and schema enhancements, aiming to provide reusable frameworks for modeling accelerators.
E N D
IRMIS IRMIS-APS, outline, boundary conditions, issues D. Dohan, Mar 9, 2005
Group leaders - general requirements and perspective • Potential coverage of the IRMIS approach • Recent Collaboration progress • User interface – XAL/CFW • Configuration management • RDB experts - ideas on how to extend the core
IRMIS - Introduction • Integrated Relational Model of Installed Systems • ‘system’ approach to modeling the accelerator and its control system • integrated coverage of software, hardware and cabling • Collaborative approach • Goal is to provide re-useable relational database and application frameworks . • Inter-laboratory approach strengthens the underlying database and application structures • The ‘EPICS’ model is used throughout – sophisticated high level tools are developed, but the user always maintains the ability to look ‘under the hood’ • Minimalist approach, locally extensible.
The IRMIS Collaboration • Initial collaborative effort between SNS and APS • initiated after Santa Fe EPICS meeting • series of visits to SNS • initial crawler tests at SNS • XAL demonstration/developments • JERI demonstration and developments • PV crawler and schema under test at SNS and DESY • Recent developments: this meeting
Boundary Conditions • the underlying RDB schema should be easy to understand • ‘a control system engineers relational database’ • promotes RDB evolution and exploitation if understood by the control system engineer/end user. • site neutral • no site-specific constructs • no accelerator specific assumptions • OS neutral • RDBMS neutral • extensible • although schema changes are expensive (-> domain modeling) we accept them as a fact of life. Development effort based on major release phases (EPICS model)
IRMIS PV ERD • ERDs are cause for (potentially) plenty of debate • “we have different schemae because we abstract or conceptualize the problem differently” • IRMIS has no formal domain analysis – use prototype approach • S. Lewis, NIF, private communication • APS crawler and Oracle PV database running for ~4 years • use this prototype experience in lieu of domain analysis? • New PV crawler and schema now ready for release • C. Saunders talk