LHCb Front-end - DAQ - Controls workshop at CERN May 16 - 19 (Entire LHCb
collaboration)
From: Jorgen.Christiansen@cern.ch
Date: 4/6/00
Time: 5:43:15 PM
Remote Name: 137.138.142.33
Remote User:
Comments
Dear LHCb colleagues
After the successful front-end - DAQ - Controls workshop
in October last year it is felt that a new workshop of the same
type will be very useful for the front-end - DAQ - Controls
community. The most convenient time for such a workshop has been
found to be May 16 - 19. This is the week just before the coming
LHCb week which may in certain respects be considered a bit
unfortunate for some people who may then be requested to be at CERN
in two consecutive weeks (please comment). We intent to start Tuesday
May 16 at 14:00 to enable people to arrive Tuesday morning and to finish
friday at noon to enable people to return home friday afternoon.
The general Outline of the workshop is planned to be quite similar
to the previous workshop:
Tuesday, May 16, afternoon: Front-end
Wednesday, May 17: Front-end
Thursday, May 18: TFC - DAQ
Friday, May 19, morning: Controls
A first preliminary list of subjects to discuss during the
workshop is given below (please comment). Any volunteers to make
presentations in any of the given subjects is most welcome !.
Requests for specific contributions will be made shortly.
Front-end:
Front-end error conditions
Error sources: SEU, glitches, buffer overflows, etc.
Error propagation
Error recovery
Error rate estimation
Resets
Definition of reset types
Definition of reset scenarios
Physics loss related to resets
L1 buffer
Buffer size requirements
Synchronization:
Bunch collision synchronization
board to board synchronization
Radiation environment
Radiation level estimates
location of electronics
Qualification of electronics for radiation effects
Power supplies
Standardization possible ?
Location
Magnetic fields
Radiation levels
Interface to readout unit: Front-end multiplexing. link
technology link protocol
Interface to trigger systems: Data to read out from trigger
systems Requirements to front-end to monitor trigger systems
Testability/reliablilty requirements to front-end electronics
Redundancy required in critical parts ?. Grounding: Ground loop
prevention Signal shielding Isolation from beam pipe (special
vertex detector problem)
Access to electronics in cavern and detectors Access procedure
Access periods
DAQ: TFC (timing and fast control) status Requirements to readout supervisor
Partitioning and related distribution switch Throttling Who wants to throttle
who when ( DAQ, L1 , etc.)
Readout unit requirements: Data checking Error recovery Non zero
suppressed data Controls: Board level controls Credit card PC's
Firewire Local board control bus Chip level controls Control
system for CMS tracker Control requirements from sub-detectors (
bandwidth , etc.)
| 