1 August 2000ATLAS SCT and Pixel Off-Detector PDR 1 SCT ROD Crate DAQ Status and Schedule John Hill University of Cambridge.

Slides:



Advertisements
Similar presentations
Systems Analysis, Prototyping and Iteration Systems Analysis.
Advertisements

[Insert Project Name] Detailed Design Review (DDR) [Insert Date of DDR] Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC)
Supervision of Production Computers in ALICE Peter Chochula for the ALICE DCS team.
The LAr ROD Project and Online Activities Arno Straessner and Alain, Daniel, Annie, Manuel, Imma, Eric, Jean-Pierre,... Journée de réflexion du DPNC Centre.
CMS Week Sept 2002 HCAL Data Concentrator Status Report for RUWG and Calibration WG Eric Hazen, Jim Rohlf, Shouxiang Wu Boston University.
Rational Unified Process
Uli Schäfer Discussions with H.B. after last meeting… All ATLAS standard racks and crates will be monitored. Helfrieds group will equip them with ELMBs.
18 June 2001SCT/Pixel ROD Software Workshop1 SCTDAQ- a brief summary John Hill University of Cambridge.
Stephen Milton Undulator System 20 April, 2006 LCLS Undulator System Update S. Milton, ANL FAC, April 20 th, 2006.
Runtime alignment system SOFTWARE DESIGN IDEAS Wed 4 th May 2005 P Coe.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Package design and the Iterative process model. What is a package? Classes are not sufficient to group code –Some classes collaborate, implying dependencies.
Introduction to Computer Technology
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
CIS 321—IS Analysis & Design
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
RUP Fundamentals - Instructor Notes
Chapter 2 The process Process, Methods, and Tools
These slides are designed to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Peter W. PhillipsSCT/Pixel RODDAQ workshop, UCL, July 2002 SCT Needs for Full User Evaluation Peter W Phillips Rutherford Appleton Laboratory.
JCOP Workshop September 8th 1999 H.J.Burckhart 1 ATLAS DCS Organization of Detector and Controls Architecture Connection to DAQ Front-end System Practical.
Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang.
Update on Database Issues Peter Chochula DCS Workshop, June 21, 2004 Colmar.
André Augustinus 10 September 2001 DCS Architecture Issues Food for thoughts and discussion.
I Power Higher Computing Software Development The Software Development Process.
Control in ATLAS TDAQ Dietrich Liko on behalf of the ATLAS TDAQ Group.
Software Status Sonja Vrcic Socorro,
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 other methodologies 1 Method/Process = step-by-step description of the steps involved.
T. Meyer ROD Software Workshop July 2002 Opening Comments Tom Meyer Iowa State University
Mobile DAQ Testbench ‘Mobi DAQ’ Paulo Vitor da Silva, Gerolf Schlager.
Multistep Runs with ROD Crate DAQ Murrough Landon, QMUL Outline: Overview Implementation Comparison with existing setup Readout Status ModuleServices API.
Overview of DAQ at CERN experiments E.Radicioni, INFN MICE Daq and Controls Workshop.
Upgrade to the Read-Out Driver for ATLAS Silicon Detectors Atlas Wisconsin/LBNL Group John Joseph March 21 st 2007 ATLAS Pixel B-Layer Upgrade Workshop.
6th Feb 2003SCT DAQ analysis development 1 SCT analysis framework Work by:Alan Barr, Matt Palmer, Dave Robinson Almost all slides originally produced by.
IDE DCS development overview Ewa Stanecka, ID Week, CERN
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
28 June 2004ATLAS Pixel/SCT TIM FDR/PRR1 TIM tests with ROD Crate John Hill.
Tom Meyer, Iowa State SCT/Pixel Online Workshop June, 2001 UML and OOAD Unified Modeling Language Object Oriented Analysis and.
Click to add text Systems Analysis, Prototyping and Iteration.
ATLAS SCT/Pixel TIM FDR/PRR28 July 2004 Resonant Triggers - Matt Warren1 Physics & Astronomy HEP Electronics Matthew Warren John Lane, Martin Postranecky.
MINERvA Status Report Deborah Harris, Gabe Perdue, Kevin McFarland, Jorge Morfin October 15, 2009.
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Peter W. PhillipsATLAS SCT Week, CERN, September/October 2002 Electrical Tests of SCT modules using RODs Peter W Phillips Rutherford Appleton Laboratory.
GAN: remote operation of accelerator diagnosis systems Matthias Werner, DESY MDI.
TDAQ Experience in the BNL Liquid Argon Calorimeter Test Facility Denis Oliveira Damazio (BNL), George Redlinger (BNL).
The ATLAS DAQ System Online Configurations Database Service Challenge J. Almeida, M. Dobson, A. Kazarov, G. Lehmann-Miotto, J.E. Sloper, I. Soloviev and.
Correlator GUI Sonja Vrcic Socorro, April 3, 2006.
DAQ Status & Plans GlueX Collaboration Meeting – Feb 21-23, 2013 Jefferson Lab Bryan Moffit/David Abbott.
October Test Beam DAQ. Framework sketch Only DAQs subprograms works during spills Each subprogram produces an output each spill Each dependant subprogram.
AFP Trigger DAQ and DCS Krzysztof Korcyl Institute of Nuclear Physics - Cracow on behalf of TDAQ and DCS subsystems.
1 Tracker Software Status M. Ellis MICE Collaboration Meeting 27 th June 2005.
1 G4UIRoot Isidro González ALICE ROOT /10/2002.
Database Issues Peter Chochula 7 th DCS Workshop, June 16, 2003.
1 4 July 2006 Alan Barr - SCT DAQ Experience and plans from running the (SCT) DAQ at SR1 HEP Cosmics setup Running modes Problems Future.
ATLAS SCT/Pixel Off Detector Workshop, UCL, 15 June ROD Test Stand Lukas Tomasek LBL
Basic Characteristics of Object-Oriented Systems
Rutherford Appleton Laboratory September 1999Fifth Workshop on Electronics for LHC Presented by S. Quinton.
August 24, 2011IDAP Kick-off meeting - TileCal ATLAS TileCal Upgrade LHC and ATLAS current status LHC designed for cm -2 s 7+7 TeV Limited to.
Software Design and Development Development Methodoligies Computing Science.
Summary of IAPP scientific activities into 4 years P. Giannetti INFN of Pisa.
L1Calo DBs: Status and Plans ● Overview of L1Calo databases ● Present status ● Plans Murrough Landon 20 November 2006.
Advanced Higher Computing Science
Gu Minhao, DAQ group Experimental Center of IHEP February 2011
DAQ for ATLAS SCT macro-assembly
INO TRIDAS presentations
Online Software Status
AICT5 – eProject Project Planning for ICT
Presentation transcript:

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 1 SCT ROD Crate DAQ Status and Schedule John Hill University of Cambridge

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 2 Summary of talk Short description of ROD Crate Controller (RCC) in context of ROD crate. Main requirements of RCC. Quick summary of interfaces. Status of DAQ software in RCC. Schedule.

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 3 SCT/Pixel ROD Crate - latest layout Mixed 6U/9U crate (RCC will be 6U). VME64x. Maximum 16 RODs/crate (not fully occupied in current planning). 8 ROD crates each for SCT and pixels.

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 4 ROD Crate Controller Hardware not yet defined - wait as long as possible –to avoid specifying a processor that will be obsolete long before LHC starts running! –to see what recommendations may come from T/DAQ group Prototype RCC using PC+NI-VXI interface –hardware already in use in a large number of SCT labs (and most importantly in the systemtest lab and the test beam) –a lot of software support and experience already available (eg. LabWindows, SCTDAQ for existing readout hardware) Final RCC could be similar (Linux support for NI-VXI is now available), or a single board computer.

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 5 ROD Crate Controller - context See the diagram (courtesy Tom Meyer) for a possible context for the RCC. This is just a working proposal - the details of how the ROD Crate DAQ might appear are still being developed. –for single-crate setups (eg. assembly sites, test beam), might have RCC at top level of ROD Crate DAQ –for multi-crate setups (eg. final assembly, ATLAS), maybe a “master” RCC approach could be used However, it gives a good idea of how the RCC is likely to fit into the overall scheme.

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 6

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 7 ROD Crate Controller - requirements Not an exhaustive list - just describes the main requirements of the RCC: –operate both in global ATLAS and local mode –communicate via the VME interface to the other modules in the crate BOC communication is indirect via the ROD ROD communication will be via the “primitive” mechanism TIM communication will be by direct access to the VME registers –communicate over the “LAN” with central ATLAS services examples are Run Control, databases, Status Display –initialise the modules in the ROD crate for data-taking might be as instructed by the ATLAS DAQ or local DAQ database information will be used to define the configuration

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 8 ROD Crate Controller - requirements –RCC will be able to read events and/or histograms from RODs in ATLAS running event reading will be in spy mode (maximum rate 1kHz), with programmable selection criteria in local running this is the mechanism to get events from RODs histograms may be stored in a database for each run –RCC must be able to reset, reconfigure or disable/enable a ROD to deal with a faulty ROD this may have to be dynamic if problems with ~1% of readout is not considered sufficient to pause ATLAS running during normal running, the RCC will continually monitor the RODs

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 9 ROD Crate Controller - interfaces Overlaps information presented elsewhere, so will skip over it quickly –interface to ROD and TIM via VME initialisation, configuration, reading events, reading histograms, monitoring behaviour –BOC interface is indirect via the ROD and the setup bus. synchronisation of the front end timing –DCS, ATLAS DAQ interface via LAN will use whatever LAN technology is selected for ATLAS

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 10 ROD Crate DAQ - Status Existing readout of SCT modules uses SCTDAQ - see Developed by Gareth Moorhead, Peter Phillips and John Hill. Main purpose is for understanding of SCT front end modules. Current version uses MuSTARD, CLOAC, SLOG, SCTLV and BiLED for readout (see diagram and photo). Implementation is modular via a set of hardware libraries, and so including ROD/BOC/TIM should not be difficult.

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 11

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 12

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 13 ROD Crate DAQ - Status Above the individual libraries, st provides the glue that makes them work together root is used for display and control (see picture). SCTDAQ has been used in the systemtest lab (B186 at CERN) and the 2000 SCT test beam, as well as in a large number of institute labs. Since the ROD User Evaluation has to “mesh in” with work on front end modules (which are much scarcer than had been hoped, and hence not available for dedicated ROD evaluation), it is natural to consider the use of SCTDAQ as the framework for initial ROD evaluation “in the field”.

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 14

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 15 ROD Crate DAQ - status However - clearly SCTDAQ is not suitable for the ROD crate DAQ to be used in ATLAS, so we need to start to develop this final DAQ in parallel with the evaluation of the prototype RODs. This will be an iterative and incremental process (see Tom’s slide) “Use Cases” are the primary mechanism in defining what we need. –work on this has already begun –not critical to get all the Use Cases enumerated initially –implementation issues are not addressed (so we avoid technical nitty-gritty until it is necessary)

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 16 Methodology Analysis (Define the problem) Design (Elaborate the problem) Implementation (Design the solution) Testing (Test the solution) Release (Let users beat up the solution) The key point: Iteration

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 17 ROD Crate DAQ - status Basic tool for the design phase will be UML (Unified Modeling Language) - seems to be fairly universally accepted Important to get the design right - don’t rush into implementation –this was graphically demonstrated by the successful way the ROD DSP software was developed (we seemed to spend a long time in the design phase, but the implementation went quickly and painlessly)

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 18 ROD Crate DAQ - status Can we use existing software? We should certainly avoid “reinventing the wheel” if possible. The ATLAS DAQ-1 Backend software (see URL provides many of the services we need: –Run Control –Database tools –Message Reporting –Process Management –etc. Also it would allow us to integrate in a natural way with the ATLAS DAQ (ie. we would minimise incompatibility issues).

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 19 ROD Crate DAQ - status Can we use existing software? We should certainly avoid “reinventing the wheel” if possible. The ATLAS DAQ-1 Backend software (see URL ) provides many of the services we need: –Run Control –Database tools –Message Reporting –Process Management –etc. Also it would allow us to integrate in a natural way with the ATLAS DAQ (ie. we would minimise incompatibility issues).

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 20 ROD Crate DAQ - status The Backend software is available as a bi-monthly release (including sources) on CD - we can take the package away and evaluate it. The ATLAS T/DAQ group view DAQ-1 as the most appropriate starting place for DAQ in ROD crates (and in Spring 2000 it was used by the TileCal group in their test beam) - hopefully this means some assistance because... Though we are starting the evaluation process, progress is constrained by limited manpower.

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 21 ROD Crate DAQ - Schedule Taking software from the test stand and integrating in the existing SCTDAQ is envisaged by end-September Up to March 2001 is the “User Evaluation” period - main non-expert location will be the SCT systemtest. Software will be developed during this period in the light of experience. In parallel with the above two activities, continue the specification and design of the final RODDAQ. Spring/Summer the ROD may be used in the ATLAS SCT test beam, either with SCTDAQ or with a first version of the final DAQ.

1 August 2000ATLAS SCT and Pixel Off-Detector PDR 22 ROD Crate DAQ - Schedule In any case, a version of the final DAQ will be needed soon after summer 2001, as construction of the first SCT barrel is scheduled to start at that time, which needs ~1 full crate of RODs to be completely read out.