Post on 31-Dec-2015
J.Harvey : Status report to LHCC referees21/10/98 Slide 2
Focus of Talk
Organisation and strategy for building new software Update on developments in DAQ and Controls
First results from Myrinet evaluation Progress in the CERN Joint COntrols Project (JCOP)
A Process for Developing Software ManagePlan, initiate, track, coordinateSet priorities and schedules, resolve conflicts
SupportSupport development processesManage and maintain componentsCertify, classify, distributeDocument, give feedback
AssembleDesign applicationFind and specialise componentsDevelop missing componentsIntegrate components
RequirementsExisting software
systems
BuildDevelop models, Evaluate toolkitsArchitect components and systems Choose integration standardEngineer reusable components
ProjectOrganisation
Support
FacilitiesCPU farmsDesktopStorageNetworkSystem Man.
VendorsIT-IPT..
VendorsIT-PDP
VendorsIT-ASD
Support
SoftwareSDEProcessQualityLibrarianTrainingWebmaster
M
Data ManagementEvent, Geometry
M
M
Build
ArchitectureComponentsFrameworks
A
ToolkitsGUI, visual,…...
M
Reconstruction
M
Simulation
M
Analysis
M
Controls
M
Control Room
M
Assemble
DAQ
M
ManageSteering Group
M M C
Technical ReviewE M A
LHCb Computing...
Arch. ReviewM A E ... ...
M
A
C
E
Coordinator
Architect
Project Manager
Project Engineer
J.Harvey : Status report to LHCC referees21/10/98 Slide 5
LHCb Offline Software Road Map
200420022000
Working Prototype, ‘retire’ SICB
Detailed Implementation
Integration and Commissioning Exploitation
Rele
ase
Num
ber
2006
J.Harvey : Status report to LHCC referees21/10/98 Slide 6
Milestone 1- Working Prototype
By mid 2000, produce a new working prototype of LHCb software incorporating: model of the LHCb detector geometry database containing ~ 1,000,000 simulated events (~100 GB) framework for processing events detector response simulation toolkit pattern recognition algorithms for tracking, RICH, calorimetry,.. toolkit of analysis algorithms interactive framework for data analysis
When in production, stop development of SICB
J.Harvey : Status report to LHCC referees21/10/98 Slide 7
Strategy
We are convinced of the importance of the architecture Identify components, define their interfaces, relationships among them Build components
first look around and see what components we can use (Objectivity, OpenInventor, ROOT, WIRED,….)
Build frameworks from these components “framework artefact that guarantees the architecture is respected”
Common approach in different domains apply good principles system-wide and reuse ideas
Incremental approach to development new release every two months gradually add functionality rapid feedback
J.Harvey : Status report to LHCC referees21/10/98 Slide 8
Design Team
Architect and Project Leader experienced designer
Domain specialists data management visualisation algorithms
Team of seven people all located at CERN (optimal) Daily design sessions (4 - 7 p.m.) Consult with experts from other experiments
2 day meeting at Orsay/LAL with ATLAS domain architects external reviewers
J.Harvey : Status report to LHCC referees21/10/98 Slide 9
Current Architecture
TObjTObj
Obj2
AppManager
PersistencySvc
Algorithm1Algorithm1
Algorithm1
JobOptionsSvc
TObj
TObjContainerTObjContainer
ObjContainer
Obj3
MessageSvc
TObj1Obj1
DetDataSrv
TDetElem1TDetElem1
TDetElem1
PObjectPObjectPDetElem
EventDataSvc
AlgFactory
AnotherPercySvc
Transient Event Store
PObjPObj
PObj
PObjPObj
PObj
DetPerstySvc
Alg Properties
T Detector Store
T Histogram Store
HistogramSvc
Hist1Hist1
Hist1
HistPerstySvc PHistPHist
ConverterConverter
Converter ConverterConverter
Converter
EventSelector
Converter
TObjObj1
uses
creates
navigability
J.Harvey : Status report to LHCC referees21/10/98 Slide 10
Use Cases (scenarios) : AppManager : AlgorithmFactory : EventDataSvcB : AlgorithmA : Algorithm
1: CreateAlgorithm ( )
2: New
3: Initialize ( )4: CreateAlgorithm ( )
5: New
6: Initialize ( )
7: NextEvent ( )
8: DoEvent ( )9: DoEvent ( )
10: Find (char*)
12: Register ( )
11: Process
J.Harvey : Status report to LHCC referees21/10/98 Slide 11
LHCb Detector Description
Transient Detector Store
Detector DataService
PersistencyServiceDetElementDetElement
DetElement
DetElementDetElementDetElement
PersistencyDetector
Store
ConverterConverterConverter
Converter
ToGeant4Service
ConverterConverterConverter
Converter
Geant4Detector
description• Detector Elements need to be “identified”
• Strong hierarchical structure• Versioning
J.Harvey : Status report to LHCC referees21/10/98 Slide 12
Visualisation
Transient Event/Detector Store
Rep.Service
RepresentationsStore
(graphical, textual)
ConverterConverterConverter
Converter
Selector
Mark objects in Store
GraphStore
UserInterface
J.Harvey : Status report to LHCC referees21/10/98 Slide 13
Architecture Review Benefits
Force preparation for the review - Documentation! Early detection of problems with the existing architecture Validation of the requirements Improvement in Architectures in all experiments
Planned for last week in November Review team
Experience with software architectures Domain experts From other LHC experiments
J.Harvey : Status report to LHCC referees21/10/98 Slide 14
Development Environment
Development platform: NT Design tool: Rational Rose Coding/debugging: Visual C++ Code Management: Visual
SourceSafe Code repository: \\alnts1\Packages\
LHCb\ Web authoring: Front Page 98 Participate in SPIDER project
J.Harvey : Status report to LHCC referees21/10/98 Slide 15
LHCb OO Programming Course
Five day course to be held at CERN Dec 7-11 Covers OO Analysis and Design, and hands-on programming Establish use of common methods and notation 16 people registered to attend Second course already fixed for Jan 18-22, 1999
J.Harvey : Status report to LHCC referees21/10/98 Slide 16
Releases
Release 1.0 planned for end ‘98 allows user to : Access simulated event data produced by SICB (ZEBRA format) Output results in the form of HBOOK histograms and/or ntuples Typical “client”: Sub-detector expert developing a pattern recognition algorithm.
Future releases will evolve according to user needs, for example to add : transient model of the detector geometry persistent event data store using Objectivity visualisation component to permit event display ...
J.Harvey : Status report to LHCC referees21/10/98 Slide 18
Project Tracking
Progress can be followed from Web page http://lhcb.cern.ch/computing/offline/html/TNS_Scrapboard.htm
1 week delay for the moment
ID Task Name1 User Requirements
2 Architecture Design
3 SDE preparation
4 Review Preparation
5 Architecture Review
6 Module Development
7 Module Design
8 Coding
9 Module testing
10 System Testing
11 Documentation
12 Release 1.0
25/11
18/12
24/8 31/8 7/9 14/9 21/9 28/9 5/10 12/10 19/10 26/10 2/11 9/11 16/11 23/11 30/11 7/12 14/12 21/12 28/12 4/1September October November December January
J.Harvey : Status report to LHCC referees21/10/98 Slide 20
Event Builder Project
PCI
MyrinetInterface
CPU
Mem
PCI-PCI ..To Farm CPUs
Link Interface
MemoryCPU
DMA
Myrinet Link
DMAPCI
Myrinet Link
Network Interfacese.g. Fast Ethernet
PCI
Myrinet Equipment received and installed. First program for interface processor written First measurements of raw speed done
J.Harvey : Status report to LHCC referees21/10/98 Slide 21
Myrinet interface-interface bandwidthMyrinet Interface to Interface Bandwidth
60
70
80
90
100
110
120
130
140
0 5000 10000 15000 20000 25000 30000 35000
Packet size [Bytes]
Ban
dw
idth
[M
Byt
es/S
ec]
Maximum obtainable speed: 132 MBytes/sec given by PCI speed
J.Harvey : Status report to LHCC referees21/10/98 Slide 22
JCOP : OPC Evaluation
ROC IOS
PLC PLC
IOS IOS IOS
LHC Exp. Sub-Detectors &Experimental equipment
I/O Servers distributed in the experimental area ( PC, VME,…)
PLC PLCAnalog/Digital channels, PLCs,Field buses, RS232, etc.
. . .
LAN
WAN
StorageO
the
r sy
ste
ms
(LH
C,
Sa
fety
, ..
.)
Servers & Workstations(Fault tolerant)
Configuration DB, Archives,Logfiles, etc.
Remote Workstations
ROC
Re
ad
ou
t sy
ste
m
OPC (OLE Process Control)
OPC interface
Industrial standard Customise interfaces Check interoperabilityWrite OPC server for CAEN I/f
J.Harvey : Status report to LHCC referees21/10/98 Slide 23
Controls Task Architecture
Operconsole
Otherconsoles
Susuisor
. . .
Operconsole
AlarmHandler
Subsystemsupervisor
IOS
DCSDatabase
DBEditor
Gen.UtilityProg.
Visuali-zation
Devserver
Devserver
Devserver
Devserver
Log+Dataarchive
DataArchiver
Servers
WS
ReportGenerator
Otherconsoles
Statusdisplays
ExternalSubSys
Othersystems
parameters
devices
Sub-systems
Expertsystem
J.Harvey : Status report to LHCC referees21/10/98 Slide 24
Controls Software Architecture
Hardware: I/O cards, FieldBus I/F, RS232, ...
DCS Services(Alarm Hand., Archiver, etc.)
InputOutput (interface drivers)
DeviceLib (device drivers)
Distributed I/O Servers
DCS DB
GUI Client Applications(Consoles, DataViewer, etc.)
Sub-System supervisors
DBMS
Generic
Specific
Object Network
parameters
devices Storage
Device API
subsystems
distributeddevices
Config.&
Utilitytools