1 / 7

Lattice Model and XAL

Lattice Model and XAL. Paul Chu. Background. High-level software architecture Application layer Operator interfaces (OPI) High-level applications Libraries Service layer Access to data Programming Interface Data layer Managed data No direct access RDB, Files, No-SQL etc. Status.

mason
Download Presentation

Lattice Model and XAL

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. Lattice Model and XAL Paul Chu

  2. Background High-level software architecture • Application layer • Operator interfaces (OPI) • High-level applications • Libraries • Service layer • Access to data • Programming Interface • Data layer • Managed data • No direct access • RDB, Files, No-SQL etc. Lattice DB and XAL, P. Chu, 26 Jan 2010

  3. Status • Prototype Model database schema • Based on LCLS MACHINE_MODEL • Support DESIGN and EXTANT models • Support GOLD (default) and GOLD history • Currently standalone, can link to Component/Device, Configuration DB • Converted from Oracle to MySQL (almost done) • Test data in for both FRIB and ReA3 • Prototype client GUI • Based on LCLS Model Manager Java app • Can compare between any 2 saved models or the current running one • No service layer yet • Direct JDBC between client GUI and DB server Lattice DB and XAL, P. Chu, 26 Jan 2010

  4. DB Schema • DB is the place to hold model data • Will be used for any model, not only XAL • Converted from Oracle to MySQL with some fancy functions left out • 10 tables and 1 view as self contained, standalone DB • Oracle version is in LCLS production environment – mature enough Lattice DB and XAL, P. Chu, 26 Jan 2010

  5. GUI Client App • Prototype from LCLS Model Manager app • Served as a quick viewing tool for model data • Not meant for heavy production release FRIB SG1 TO STRIPPER Lattice DB and XAL, P. Chu, 26 Jan 2010

  6. Near-term To Do List • Set up Lattice schema • Link to IRMIS for Device table • Correct parameters in XAL XDXF files (for both FRIB and ReA3) • Populate device info in IRMIS • XAL XDXF file can then generated from IRMIS directly • Currently, XAL XDXF file is generated from Excel • Populate official lattice data • Design and construct Model service layer • Once the service and its API is ready, non-XAL model can take advantage of it – need script/glue code to link non-XAL model and the Model Service • Client GUI modification or start over • User input is needed for GUI design Lattice DB and XAL, P. Chu, 26 Jan 2010

  7. Summary • Model DB prototyped • Client GUI prototyped • Ready for data population • Ready for user test • What’s next? Save/restore DB schema + app? Lattice DB and XAL, P. Chu, 26 Jan 2010

More Related