This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC0000661. Michigan State.

Slides:



Advertisements
Similar presentations
Paul Chu FRIB Controls Group Leader (Acting) Service-Oriented Architecture for High-level Applications.
Advertisements

Database System Concepts and Architecture
Copyright Hub Software Engineering Ltd 2010All rights reserved Hub Document Exchange Product Overview Secure Transmission for Transaction-based Documents.
This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC Michigan State.
Model Server for Physics Applications Paul Chu SLAC National Accelerator Laboratory October 15, 2010.
--What is a Database--1 What is a database What is a Database.
Paul Chu FRIB Controls Group Leader (Acting)
GLAST LAT ProjectOnline Peer Review – July 21, Integration and Test J. Panetta 1 Gamma-ray Large Area Space Telescope GLAST Large Area Telescope:
Integration case study Week 8 – Lecture 1. Enrolment request (Workstation) Application server Database server Database New University Student Record System.
SPEAR PV RDB Database EPICS Collaboration Meeting April 27, SPEAR PV RDB Database Clemens Wermelskirchen.
Chapter 9: Moving to Design
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Overview of Database Languages and Architectures.
The Client/Server Database Environment
Chapter 2 Database System Concepts and Architecture
8/21/2015J-PARC1 Data Management Machine / Application State Data.
“This presentation is for informational purposes only and may not be incorporated into a contract or agreement.”
Database System Concepts and Architecture Lecture # 3 22 June 2012 National University of Computer and Emerging Sciences.
GRID job tracking and monitoring Dmitry Rogozin Laboratory of Particle Physics, JINR 07/08/ /09/2006.
What is Sure BDCs? BDC stands for Batch Data Communication and is also known as Batch Input. It is a technique for mass input of data into SAP by simulating.
CSCI 6962: Server-side Design and Programming Introduction to Java Server Faces.
Eurotrace Hands-On The Eurotrace File System. 2 The Eurotrace file system Under MS ACCESS EUROTRACE generates several different files when you create.
ABC Insurance Co. Paul Barry Steve Randolph Jing Zhou CSC8490 Database Systems & File Management Dr. Goelman Villanova University August 2, 2004.
HPS Online Software Discussion Jeremy McCormick, SLAC Status and Plans.
Status of the Brick Manipulation database development Introduction: goal and principles System analysis –The brick life –Manipulation procedures Proposed.
Debby Quock November 13, 2012 IRMIS at CLS. IRMIS Currently at CLS PV Crawler –Perl modules that parse EPICS IOC st.cmd, db, and dbd files. Information.
BROOKHAVEN SCIENCE ASSOCIATES High level applications and EPICS control GUOBAO SHEN NSLS-II, Control Group May 4 th, 2009.
The Network Performance Advisor J. W. Ferguson NLANR/DAST & NCSA.
MASAR Service Guobao Shen Photon Sciences Department Brookhaven National Laboratory EPICS Collaboration Workshop Oct 05, 2013.
Elder Matias, Diony Medrano, Dong Liu (At Michigan State University - Nov 2011) IRMIS at CLS.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
The european ITM Task Force data structure F. Imbeaux.
4BP1 Electronic & Computer Engineering Paul Gildea th Year Interim Project Presentation.
ALICE, ATLAS, CMS & LHCb joint workshop on
K.Furukawa, Nov Database and Simulation Codes 1 Simple thoughts Around Information Repository and Around Simulation Codes K. Furukawa, KEK Nov.
This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC Michigan State.
17 th October 2005CCP4 Database Meeting (York) CCP4(i)/BIOXHIT Database Project: Scope, Aims, Plans, Status and all that jazz Peter Briggs, Wanjuan Yang.
Paul Chu Lattice Database.  Learning MySQL  Model DB prototyped Include part of the Lattice DB (Device Settings) Converted from SLAC/LCLS MACHINE_MODEL.
Paul Chu SLAC App. 10/14/ SLAC (LCLS) Application Plans P. Chu for SLAC High-Level Application Team.
Project Database Handler The Project Database Handler is a brokering application that mediates interactions between the project database and the external.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
Pan-STARRS PS1 Published Science Products Subsystem Presentation to the PS1 Science Council August 1, 2007.
1 P. Chu 1 Adapting XAL for LCLS EPICS Meeting, Vancouver Adapting XAL for LCLS Paul Chu - SLAC May 1, 2009.
LHCb File-Metadata: Bookkeeping Carmine Cioffi Department of Physics, Oxford University UK Metadata Workshop Oxford, 04 July 2006.
This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC Michigan State.
AHM04: Sep 2004 Nottingham CCLRC e-Science Centre eMinerals: Environment from the Molecular Level Managing simulation data Lisa Blanshard e- Science Data.
The DCS Databases Peter Chochula. 31/05/2005Peter Chochula 2 Outline PVSS basics (boring topic but useful if one wants to understand the DCS data flow)
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC Michigan State.
TRIUMF HLA Development High Level Applications Perform tasks of accelerator and beam control at control- room level, directly interfacing with operators.
UNICOS LHCLoggingDB Josef Hofer EN/ICE/SCD. Agenda The LHC Logging Database Purpose of the LHCLogging component Basic concepts Advanced concepts Logging.
2) Database System Concepts and Architecture. Slide 2- 2 Outline Data Models and Their Categories Schemas, Instances, and States Three-Schema Architecture.
Level 1-2 Trigger Data Base development Current status and overview Myron Campbell, Alexei Varganov, Stephen Miller University of Michigan August 17, 2000.
This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC Michigan State.
Simulation Production System Science Advisory Committee Meeting UW-Madison March 1 st -2 nd 2007 Juan Carlos Díaz Vélez.
Tutorial on Science Gateways, Roma, Catania Science Gateway Framework Motivations, architecture, features Riccardo Rotondo.
This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC , the State of Michigan.
This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC , the State of Michigan.
ISC321 Database Systems I Chapter 2: Overview of Database Languages and Architectures Fall 2015 Dr. Abdullah Almutairi.
16 Copyright © 2004, Oracle. All rights reserved. Testing the Migrated Oracle Database.
This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC , the State of Michigan.
LCLS Commissioning & Operations High Level Software
ODBC, OCCI and JDBC overview
Chapter 2 Database System Concepts and Architecture
The Client/Server Database Environment
New developments on the LHCb Bookkeeping
LCLS Commissioning & Operations High Level Software
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
DUCKS – Distributed User-mode Chirp-Knowledgeable Server
SLAC monitoring Web Services
Presentation transcript:

This material is based upon work supported by the U.S. Department of Energy Office of Science under Cooperative Agreement DE-SC Michigan State University designs and establishes FRIB as a DOE Office of Science National User Facility in support of the mission of the Office of Nuclear Physics. Paul Chu Lattice and Model

 Motivation  Model Server design  LCLS Model Database  Service layer  Prototype and path forward Outline P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 2

 Providing a universal model environment Different accelerators may use different modeling tools but some applications can be shared Universal API useful for future application development  Connection to control systems  Centralized model computation Reducing application complexity Model results shared  Client apps same for both online tuning and offline analysis  Simple, clean API for all model needs Motivation P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 3

Overview P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 4

 Using XAL data structure XAL accelerator hierarchy suitable for holding model data Set/get model data to/from XAL (data access API) Advantage: it is in Java, i.e. supporting Matlab, Jython  Using Java or scripting language to generate non-XAL model input files Prototyped for IMPACT (in Python)  Using scripting language to parse non-XAL model output files  Using scripting language for model run control Start/stop/abort a model run Scheduling on cluster Monitoring run status by checking a meta file Saving data to file system, then relational database  Data storage similar to LCLS MACHINE_MODEL schema Preliminary Design P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 5

 Initialization Establish CA and DB connection Construct Accelerator object  For live machine model, programmatically generate the input file  Schedule/run model, monitor progress  Collect model run result  Insert model run result into XAL data structure  Update model service data In-memory DB for quick access Store persistent data in RDB  Client apps access model data via API Model Run Control [1] P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 6

 Adapters between XAL and non-XAL models for both input and output  Arrange/schedule model runs  Monitoring run status for offline tracking  Hook to service provider Model Run Control [2] P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 7

 Model run on standalone app, on-demand based  3 databases – production, QA and production-for-external-use  Model data entered in Oracle DB with JDBC PL/SQL procedural calls for data validation, integrity check Failover protection  Model data indexed for better performance LCLS Machine_Model Schema [1] P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 8

LCLS Machine_Model Schema [2] P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 9  10 tables Table Name# of Cols# of IndexesSizeTablespace DEVICE_TYPES7364KMACHINE_MODEL ELEMENT_MODELS MMACHINE_MODEL GOLD72128KMACHINE_MODEL HARDWARE_SETTINGS6264KMACHINE_MODEL INITIAL_CONDITIONS6264KMACHINE_MODEL MODEL_DEVICES104304MMACHINE_MODEL MODEL_LINES6264KMACHINE_MODEL MODEL_MODES7364KMACHINE_MODEL RUNS145448KMACHINE_MODEL XML_DOCS131128KMACHINE_MODEL  29 views mainly for individual beamlines and grouped parameters Courtesy E. Grunhaus

 29 views mainly for individual beamlines 5 beamlines  ~2500 elements for the LCLS “FULL MACHINE” line  Total data after 3 years ~2 GB, ~10 runs per day while operating  Support DESIGN and EXTANT models LCLS Machine_Model Size Estimate P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 10

 DEVICE_TYPES: link to the component tables  ELEMENT_MODELS: actual model data  GOLD: keep track of GOLD model history  HARDWARE_SETTINGS: link to SCORE (data correlation)  INITIAL_CONDITIONS: can be used for different initial beam conditions. Not in use for now.  MODEL_DEVICES: machine settings for model run input  MODEL_LINES: beamlines  MODEL_MODES: can distinguish, say, different MPS or running modes  RUNS: different model runs, e.g. date, design/extant, comments etc.  XML_DOCS: can save model data as XML files LCLS Machine_Model Schema details P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 11

 Communication protocol – TBD XML-RPC, JSON-RPC for simple data types PVAccess?  How to package and transport model data Mainly simple data such as getBetaX(), getEmitX(), getEnergy() Maybe getAllBetaFor(a_beamline_section), getAllBetaFor(all_magnets)  Broadcasting/on-demand pulling/Subscription to a service Service Layer P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 12

 XAL data structure and access API is basically ready Maybe need convenient wrapper API  XML-RPC based service prototyped for data communication Is PVAccess/PVData ready for complex data structure?  Lattice DB schema can base on LCLS MACHINE_MODEL  Need IRMIS data access API for Lattice Prototype and Path Forward P. Chu, Controls Database Collaboration, 17 Nov 2011, Slide 13