Transcript Considerations about the BMS links to other OPERA systems

Considerations about the BMS links to
other OPERA systems
D.Duchesneau
LAPP, Annecy
• Brick Manipulation Manager
• Links to other computing systems
• Needs to define the general framework
• Technical choices
OPERA collaboration meeting
May 21st, 2003
REMINDER: (my talk of yesterday)
Main functions of the computing system under development should be:
• To manage the life cycle of the bricks and CS and the
manipulation information
• To save the relevant information into a database
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…)
Links between the various computer systems involved in the brick
manipulation
<<subsystem>>
Brick Manipulation
Manager(BMM)
<<uses>>
Manipulator
Interface
Scanning
Interface
<<uses>>
BAM
Interface
<<uses>>
<<subsystem>>
Supervisor/
Manipulator
Manager
Interface
<<uses>>
<<subsystem>>
OPERA
Scanning System
<<subsystem>>
BAM
<<subsystem>>
(OGC)OPERA
Global Control
<<subsystem>>
OPERA
On Line System
What do we need:
• Wishes of external users concerning informations that should be available
from the manipulation DB (apart from what I already described)
• Define communication protocol and programming language (interfaces with
other systems): OPERA standards?
•Names of contact persons for the links to the following systems:
•Opera Global Control (or DAQ/OnLine)
•Brick information from the BAM
•CS scanning results
•…..
• To know how those external systems plan their own development?
• Study and development of the interfaces (in collaboration with our team)
•
Technical choices:
System analysis: follows the Unified System Development Process
(USDP) method using the Unified Modeling Language (UML)
(cf: yesterday’s talk)
Database : the choice goes to ORACLE. It seems to fit the needs
and follows preference which has been already suggested in
OPERA.
Operating system and platform for the BMM : the choice will
follow the standards choosen by the collaboration, all possibilities
should work (PC with Windows, Linux…..).
Programming language : C++ and/or Java for the users interface
Communication protocol: IP on Ethernet….
It is time now to start this work and
to join the effort!
•Names of contact persons
Opera Global Control (or DAQ/OnLine)
?
Brick information from the BAM
?
CS scanning results
?
• define OPERA standards and strategy