Status of the Brick Manipulation database development Introduction: goal and principles System analysis –The brick life –Manipulation procedures Proposed design –Development phases –status Conclusions D.Duchesneau LAPP, Annecy OPERA collaboration meeting May 21st, 2003

Introduction: Goal Main functions of the computing system under development should be: To manage the life cycle of the bricks and the manipulation information To save the relevant information into a database The tracing and the control of the brick and CS manipulation: Start: first entrance on the manipulator Finish: when the brick is dismantled for development But the BMS will manipulate entities composed of a brick and a CS Multi localized activity: the system should take into account all the procedures occurring in different places!

Introduction: system main requirements During initial SM filling: To know the detector cell status: free or full To know the presence of a filling basket to proceed During OPERA data acquisition: Communicate to the BMS the list of bricks for daily extraction Keep track of the brick life from insertion to development At any time: To know status of any brick (position within the detector), actual manipulation…. To get complete history of a given brick To get complete history of a given detector cell Display the wall content To know the BMS status To get the detector geometry and cell localization ?

The Brick life Brick Assembly machine Loading basket Transport to the support Target walls BMS Load the replacement /new bricks Loading station Fill the walls Physical place results Physical movement action negative Cosmic bench positive CS Analysis Development laboratory Scanning laboratory Scan results Brick emulsion analysis Development laboratory Scanning laboratory Brick transport Analysis zone CS transport Bring the bricks to reinsert Unload the extracted brick Unload the bricks to analyse Extract brick for analysis; insert replacement brick CS separation Brick waiting Stock of bricks to reinsert Add a new CS from the stock Shielded area

Brick and CS Manipulations occur at many places by different actors (humans, computer systems…) which should be identified as function of their actions each time the brick status is changing or moved to an other place: need to collect, incorporate, update brick and CS information….in the system and save in database the information Important to: define the procedures involved in manipulation construct the use cases for each actor and the sequence of actions (sequence diagrams) Define now the information to be provided and saved by all external users!

Development : these CS are transported by the brick operator or a physicist for development CS to analyse new CS cart Towards cosmic bench before development. displacement controlled by the brick operator 1. BRICK UNLOADING and CS DETACHING Identify a brick to unload: read the bar code of a brick in the loading basket in the row 1 to 5 starting from 1 st position Take the brick Detach the CS Read the CS bar code 2. CONSULT THE CS RESULTS FOR DECISION Identify a brick to reinsert: read the bar code of a brick waiting for scanning. Move the brick to the CS gluing zone Identify a brick to analyze: read the bar code of a brick waiting for scanning. Put the brick in a stock to be sent to cosmics. 3. CS GLUING AND BASKET INSERTION Glue a new CS on a free brick in this zone according to the rules Read the CS and brick bar code In the available basket: insert the brick in row 6 to 9 starting from the first free slot. validate Example: shielded area (waiting zone) Information source: code bar readers (mandatory) Transport belt

Operator user interface

The core of the system is called « Brick Manipulation Manager » or BMM. Its tasks are: communicate to the supervisor all commands and actions from the outside world retrieve the data which will be used to update the database information. do the communication with the external systems (OGC, BAM, cosmic bench, CS analysis…)

> Supervisor/ Manipulator > BAM > (OGC)OPERA Global Control > OPERA On Line System > OPERA Scanning System > ManagerInterface ScanningInterface BAMInterface Brick Manipulation Manager(BMM) ManipulatorInterface Links between the various computer systems involved in the brick manipulation

Opera General User BrickOperatorLoading/UnloadingOperator CommonOperatorPhysicist Opera Global Control On-line Main actors of the BMM system: ? Function inheritance

Development phases Design of the brick management system (analysis) Use cases and user need studies Constraint studies (data availability, coherence, OS, inputs, outputs) Sketch the procedure schemes (as shown) Communication with the supservisor system Define the commands to exchange between supervisor and BMM Study and create the interface Define communication protocol and programming language (interfaces and BMM) Study and development of the users interface (as shown) Create the database structure with ORACLE Develop tools for DB exploitation API (« Application Programming Interface ») Information display Monitoring (ex: aver. time delay between extraction and CS decision)

The manipulator database project has started beginning of The team is composed of 2 software engineers (not full time) from LAPP and myself. 1 student from a Technical Institute (production management department) is working with us and proceeds in understanding the procedures and the system analysis (should finish end of june). For such a system: analysis following the Unified System Development Process (USDP) method using the Unified Modeling Language (UML): Advantages: Priority is given to the definition of the different actors of the system (with hierarchy, functions…) then to the definition of the use cases objects and object classes appear naturally Status:

Example: Some object classes which will appear in the database With their composition and association

Design of Graphical User Interfaces: To access the brick information stored in Database

Conclusions n Work has started! n The BMS database includes more than just the manipulator informations n It is crucial to understand now how the bricks will be treated during their lives n Procedures should be clearly defined asap n BMM concept seems adapted for the brick and CS manipulation management n BMM need interfaces with external systems (to be discussed tomorrow) as well as the OPERA standards (language …) for those kinds of developments