ALICE trigger control technologies run2 vs run3 layout IPbus introduction 1 Anton Jusko 27/01/20166CTP/LTU review.

Slides:



Advertisements
Similar presentations
Review of Topology and Access Techniques / Switching Concepts BSAD 141 Dave Novak Sources: Network+ Guide to Networks, Dean 2013.
Advertisements

Status of the CTP O.Villalobos Baillie University of Birmingham April 23rd 2009.
1 iTOP Electronics Effort LYNN WOOD PACIFIC NORTHWEST NATIONAL LABORATORY JULY 17, 2013.
09/06/11 CMS Trigger and Readout Upgrades: The IPbus Protocol & The IPbus Suite TIPP 2011 Robert Frazier Greg Iles, Dave Newbold, Andrew Rose Robert Frazier.
Copyright© 2000 OPNET Technologies, Inc. R.W. Dobinson, S. Haas, K. Korcyl, M.J. LeVine, J. Lokier, B. Martin, C. Meirosu, F. Saka, K. Vella Testing and.
28 August 2002Paul Dauncey1 Readout electronics for the CALICE ECAL and tile HCAL Paul Dauncey Imperial College, University of London, UK For the CALICE-UK.
1 CTP DCS luminosity monitoring A. Jusko, R. Lietava, J. Urban.
UNIVERSITY OF BERGEN DEPARTMENT OF PHYSICS 1 UiB DR 2003 High Level API for the TPC-FEE control and configuration.
Field Programmable Gate Array (FPGA) Layout An FPGA consists of a large array of Configurable Logic Blocks (CLBs) - typically 1,000 to 8,000 CLBs per chip.
Chapter 15 Networks. Chapter Goals Types of networks Topologies Open Systems Home Internet connections 15-2.
Hall D Trigger and Data Rates Elliott Wolin Hall D Electronics Review Jefferson Lab 23-Jul-2003.
1 Introduction to Networking Dr. Mahdi Nasereddin PPU.
ACM 511 Chapter 2. Communication Communicating the Messages The best approach is to divide the data into smaller, more manageable pieces to send over.
Engineering & Instrumentation Department, ESDG, Rob Halsall, 24th February 2005CFI/Confidential CFI - Opto DAQ - Status 24th February 2005.
Remote Firmware Down Load. Xilinx V4LX25 Altera Stratix Control Altera Stratix Control Xilinx V4FX20 EPROM XCF08 EPROM XCF08 EPROM EPC16 EPROM EPC16 EPROM.
Boosting Event Building Performance Using Infiniband FDR for CMS Upgrade Andrew Forrest – CERN (PH/CMD) Technology and Instrumentation in Particle Physics.
Cluster Computers. Introduction Cluster computing –Standard PCs or workstations connected by a fast network –Good price/performance ratio –Exploit existing.
“ PC  PC Latency measurements” G.Lamanna, R.Fantechi & J.Kroon (CERN) TDAQ WG –
15-1 Networking Computer network A collection of computing devices that are connected in various ways in order to communicate and share resources.
LECC2003 AmsterdamMatthias Müller A RobIn Prototype for a PCI-Bus based Atlas Readout-System B. Gorini, M. Joos, J. Petersen (CERN, Geneva) A. Kugel, R.
SBS meeting VETROC application for Cerenkov triggering Alexandre Camsonne March 18 th 2015.
SBS meeting VETROC application for Cerenkov triggering Alexandre Camsonne March 18 th 2015.
Design and Performance of a PCI Interface with four 2 Gbit/s Serial Optical Links Stefan Haas, Markus Joos CERN Wieslaw Iwanski Henryk Niewodnicznski Institute.
The ALICE DAQ: Current Status and Future Challenges P. VANDE VYVRE CERN-EP/AID.
1 Lecture 7 LAN Wiring, Physical Topology, and Interface Hardware Computer Networks CS 4316.
David Abbott - JLAB DAQ group Embedded-Linux Readout Controllers (Hardware Evaluation)
Increasing Web Server Throughput with Network Interface Data Caching October 9, 2002 Hyong-youb Kim, Vijay S. Pai, and Scott Rixner Rice Computer Architecture.
Introduction to Sockets “A socket is one endpoint of a two-way communication link between two programs running on the network. A socket is bound to a port.
Client Target control req control res control req.
Performance measurement with ZeroMQ and FairMQ
1 Network Performance Optimisation and Load Balancing Wulf Thannhaeuser.
Features of the new Alibava firmware: 1. Universal for laboratory use (readout of stand-alone detector via USB interface) and for the telescope readout.
Xiangming Sun1PXL Sensor and RDO review – 06/23/2010 STAR XIANGMING SUN LAWRENCE BERKELEY NATIONAL LAB Firmware and Software Architecture for PIXEL L.
Serial Data Link on Advanced TCA Back Plane M. Nomachi and S. Ajimura Osaka University, Japan CAMAC – FASTBUS – VME / Compact PCI What ’ s next?
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Connecting to the Network Introduction to Networking Concepts.
Socket Programming Introduction. Socket Definition A network socket is one endpoint in a two-way communication flow between two programs running over.
IPHC - DRS Gilles CLAUS 04/04/20061/20 EUDET JRA1 Meeting, April 2006 MAPS Test & DAQ Strasbourg OUTLINE Summary of MimoStar 2 Workshop CCMOS DAQ Status.
Sep. 17, 2002BESIII Review Meeting BESIII DAQ System BESIII Review Meeting IHEP · Beijing · China Sep , 2002.
June 17th, 2002Gustaaf Brooijmans - All Experimenter's Meeting 1 DØ DAQ Status June 17th, 2002 S. Snyder (BNL), D. Chapin, M. Clements, D. Cutts, S. Mattingly.
SoLiD/PVDIS DAQ Alexandre Camsonne. DAQ limitations Electronics Data transfer.
PCI B ASED R EAD-OUT R ECEIVER C ARD IN THE ALICE DAQ S YSTEM W.Carena 1, P.Csato 2, E.Denes 2, R.Divia 1, K.Schossmaier 1, C. Soos 1, J.Sulyan 2, A.Vascotto.
IPbus A method to communicate with cards over Ethernet 1.
SRB data transmission Vito Palladino CERN 2 June 2014.
16th May 2007 MICE tracker phone meeting 1 Setup test bench/ Installation DATE Hideyuki Sakamoto 16 th May 2007 MICE phone meeting.
Control for CTP and LTU boards in Run
Cluster Computers. Introduction Cluster computing –Standard PCs or workstations connected by a fast network –Good price/performance ratio –Exploit existing.
L1/HLT trigger farm Bologna setup 0 By Gianluca Peco INFN Bologna Genève,
Introduction to DAQ Architecture Niko Neufeld CERN / IPHE Lausanne.
ROM. ROM functionalities. ROM boards has to provide data format conversion. – Event fragments, from the FE electronics, enter the ROM as serial data stream;
1 Network Communications A Brief Introduction. 2 Network Communications.
UHAL API Status and Plans , CMS Electronics Week Marc Magrans de Abril Dave Newbold Rob Frazier Andrew Rose Jeremiah Mans Paolo Rumerio Christoph.
DAQ 1000 Tonko Ljubicic, Mike LeVine, Bob Scheetz, John Hammond, Danny Padrazo, Fred Bieser, Jeff Landgraf.
Real-time control using embedded micro-controllers Flavio Fontanelli, Giuseppe Mini, Mario Sannino, INFN Genoa Zbigniew Guzik, Institute for Nuclear Research.
The Evaluation Tool for the LHCb Event Builder Network Upgrade Guoming Liu, Niko Neufeld CERN, Switzerland 18 th Real-Time Conference June 13, 2012.
András László KFKI Research Institute for Particle and Nuclear Physics New Read-out System of the NA61 Experiment at CERN SPS Zimányi Winter School ‑ 25.
The ALICE Data-Acquisition Read-out Receiver Card C. Soós et al. (for the ALICE collaboration) LECC September 2004, Boston.
Eric Hazen1 Ethernet Readout With: E. Kearns, J. Raaf, S.X. Wu, others... Eric Hazen Boston University.
Hub v.s. Switch Qualnet Exercise 1.
The STAR Heavy Flavor Tracker PXL detector readout electronics
Wireless-N Comparative Results -3rd party testing preliminary results
Electronics Trigger and DAQ CERN meeting summary.
TELL1 A common data acquisition board for LHCb
ALICE Trigger Upgrade CTP and LTU PRR
L0 processor for NA62 Marian Krivda 1) , Cristina Lazzeroni 1) , Roman Lietava 1)2) 1) University of Birmingham, UK 2) Comenius University, Bratislava,
J.M. Landgraf, M.J. LeVine, A. Ljubicic, Jr., M.W. Schulz
D.Cobas, G. Daniluk, M. Suminski
PCI BASED READ-OUT RECEIVER CARD IN THE ALICE DAQ SYSTEM
Example of DAQ Trigger issues for the SoLID experiment
Hall D Trigger and Data Rates
TELL1 A common data acquisition board for LHCb
Presentation transcript:

ALICE trigger control technologies run2 vs run3 layout IPbus introduction 1 Anton Jusko 27/01/20166CTP/LTU review

Connections RUN1: VME RUN2: VME, USB RUN3: VME (TTCmi crate), USB (PM/SPI), IPbus USB: PM/SPI bus on new board s Lab: connected to Wxx PC with USB cable P2: Anywhere USB-Ethernet-USB adapter allowing longer distance VME, replaced by IPbus in run3: Board’s FPGA programming (not clear yet, if IPbus can be used) Boards control Counters reading SSM reading possibly CTP readout using IPbus in run3 2

Run2 layout NFS/BOOTP server serving VME CPUs NFS/BOOTP server serving VME CPUs Application server (SMAQ, IR processing) Application server (SMAQ, IR processing) Diskless VME CPU CTPCTP CTPCTP LTULTU LTULTU RF2TTCRF2TTC RF2TTCRF2TTC LTULTU LTULTU 9 VME CPUs controlling 9 VME crates VME bus 3 Alice experimental network cavern

Run3 layout NFS/BOOTP server serving VME CPU IPbus Controlhub NFS/BOOTP server serving VME CPU IPbus Controlhub Application server Diskless VME CPU CTPCTP CTPCTP LTULTU LTULTU RF2TTCRF2TTC RF2TTCRF2TTC LTULTU LTULTU Alice experimental network 1 VME CPU VME bus 4 1Gb switch 1Gb private Ethernet, for IPbus cavern

IPbus Based on UDP protocol over 1Gb Ethernet Reliable TCP connection when used with Control hub –part of IPbus software Data word: 32bits Typical latency: 250 – 450 usecs Typical throughput: 50 – 500 Mb/s, depends on the length of data block Software API: Available for C++ and python Allows single atomic operations: Read, Write Read+Modify bits: (X= (X&A) | B Read+Modify sum: X= X+A Block R/W operations Future plans: Streaming DAQ port (aka DDL in run2) 10Gb ethernet (2014 TWEPP paper) 5

IPbus example address_table.xml: describing firmware connection_file.xml: specifies particular IPbus endpoint <connection id="board.1" uri="chtcp-2.0://localhost:10203?Control hub target= :50001" IPbus endpoint address_table="file://address_table.xml "/> 6

C++ #include "uhal/uhal.hpp" #include "uhal/tests/tools.hpp" //open connection ConnectionManager manager ( "file://../connection_file.xml" ); HwInterface hw=manager.getDevice ( "board.1" ); // Request for block and simple register read ValWord reg; ValVector ram(1000); ram= hw.getNode( "ram" ).readBlock(1000); reg= hw.getNode( "reg" ).read(); // data transfer starts/finishes with following line hw.dispatch(); cout << "reg:" << reg.value() << " ram[0]:" << ram.at(0) << std::endl; 7

Summary Latency: VME (~1us) much faster, but is not an issue for CTP/LTU control Throughput SSM (=4MB) read: VME using word access 28Mb/s, IPBUS: ~ 500Mb/s is meaningful IPbus used for CTP readout: possible, with rates given in an example below, using 4kB data blocks (50Mb/s IPbus data rate ) IRs stream: 64bits/interaction, as used in run2/DDL2, IR rate 500kHz corresponds to 32Mb/s IPbus data rate Trigger messages: 144 bits/message, 100 kHz event rate corresponds to 14.4 Mb/s in IPbus data rate 8