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.DuchesneauLAPP, 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 requirementsDuring 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 laboratoryScan results

Brick emulsion analysis

Development laboratory

Scanning laboratory

Brick transport

Analysis zone

CS transport

Bring the bricks to reinsertUnload 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 1st 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

WORK PLAN

OPERATIONS LIST

Close

Basket unloading + brick/CS ungluing(7) (priority : 1.78)

Move brick to cosmic benchMove brick to reinsertion

(12) (priority : 1.31)

Brick/CS gluing + basket insertion(4) (priority : 2)

WORK PLAN

Brick/CS gluing + basket insertion

Brick/CS gluing + basket insertion 12/06/03 15:12

Brick/CS gluing + basket insertion

Brick/CS gluing + basket insertion

Brick/CS gluing + basket insertion

12/06/03 16:36

12/06/03 17:07

2

3

2

1

PriorityDate/HourTask

12/06/03 16:22

Sort by priority

Sort by date

Taskinfo.

Close

Task selection

Task in progress

Validate the insertion

TASK DESCRIPTION (activate)

Brick/CS gluing + basket insertion

Brick/CS identification

Close

Brick Id : h2154 CS Id : h2154/kj412

Click to valid

Glue CS on a waitingbrick

Read the CS andbrick code bars

In an availab le basket, insert the brick on row 6 to 9 starting from firstfree position

Validate

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…)

<<subsystem>>Supervisor/Manipulator

<<subsystem>>BAM

<<subsystem>>(OGC)OPERA Global Control

<<subsystem>>OPERA

On Line System

<<subsystem>>OPERA

Scanning System

<<uses>>

ManagerManagerInterfaceInterface

ScanningScanningInterfaceInterface

<<uses>> <<uses>>

BAMBAMInterfaceInterface

<<uses>>

<<subsystem>>Brick Manipulation

Manager(BMM)

ManipulatorManipulatorInterfaceInterface

Links between the various computer systems involved in the brick manipulation

OperaOperaGeneral UserGeneral User

BrickBrickOperatorOperator

Loading/UnloadingLoading/UnloadingOperatorOperator

CommonCommonOperatorOperator

PhysicistPhysicist

OperaOperaGlobal ControlGlobal Control

On-lineOn-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 2003.• 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:

detector

Work plan

Half super module

+4

+1

row

wall

+31

+1

+64

+1

Brick manager

Position manager

operations

brickcell

+26

+1

+0,1+0,1 basket+0,n +0,1

CS

components Bar code reader

Example: Some object classes which will appear in the database

With their composition and association

Detector view

OPERADETECTOR VIEW

Sm1, WALL02Sm1, WALL 02 95

Cell :Row :

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

6 46 36 26 16 05 95 85 75 65 55 45 35 25 15 04 94 84 74 64 54 44 34 24 14 03 93 83 73 63 53 43 33 23 13 02 92 82 72 62 52 42 32 22 12 01 91 81 71 61 51 41 31 21 11 0987654321

Brick history

Cell history

Cell history

Sm1, right, wall02, line34, cell18

Cell history

Empty 01/01/03 08h00brick contained 29/01/03 14h22 b2145line in manipulation 04/05/04 20h20brick contained 04/05/04 20h33 y8741line in manipulation 27/08/04 21h15brick contained 27/08/04 21h29 g9762

close

Brick history

Sm1, right, wall02, line34, cell18

Brick id : g9762CS id : g9762/fc786

Brick history

insertion 10/06/03 21h45 sm2, right, 07, 23, 07extraction 23/08/04 18h35 sm2, right, 07, 23, 07insertion 27/08/04 21h29 sm1, right, 02, 34, 18

close

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

Conclusions

Work has started!

The BMS database includes more than just the manipulator informations

It is crucial to understand now how the bricks will be treated during their lives

Procedures should be clearly defined asap

BMM concept seems adapted for the brick and CS manipulation management

BMM need interfaces with external systems (to be discussed tomorrow) as well as the OPERA standards (language …) for those kinds of developments