35t Readout Software John Freeman Dune Collaboration Meeting September 3, 2015.

Slides:



Advertisements
Similar presentations
How to Use Stowe School District
Advertisements

Top-Down Network Design Chapter Nine Developing Network Management Strategies Copyright 2010 Cisco Press & Priscilla Oppenheimer.
Managing Cisco IOS Software. Overview The router boot sequence Locating IOS software The configuration register Recovering Passwords Backing Up the Cisco.
UPLOAD YOUR S2 SCANNER. To upload your Scanner means: Sending the data of the scans you made from your Scanner to the worldwide Nu Skin server. Benefits:
Customizing the MOSS 2007 Search Results November 2007 Rafael Perez.
IP Office Install in Basic Mode Initial Steps. ©2009. All rights reserved. Overview of Process 1. Read all documents sent from Avatel concerning install.
The Zebra Striped Network File System Presentation by Joseph Thompson.
MCTS GUIDE TO MICROSOFT WINDOWS 7 Chapter 10 Performance Tuning.
Distributed Databases John Ortiz. Lecture 24Distributed Databases2  Distributed Database (DDB) is a collection of interrelated databases interconnected.
1 Burn-in Viewer User’s Guide Version 2.0 February 17, 2005 LukasTomasek
Linda R. Coney – 24th September 2009 MOM Update End of Sept Run Linda R. Coney 05 October, 2009.
Chapter 11 - Monitoring Server Performance1 Ch. 11 – Monitoring Server Performance MIS 431 – created Spring 2006.
Version Control Systems Phil Pratt-Szeliga Fall 2010.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 8: Implementing and Managing Printers.
The Grades and Chat modules. This presentation covers two unrelated modules... … and Grades. Because these topics are short they are combined into one.
Using the Trigger Test Stand at CDF for Benchmarking CPU (and eventually GPU) Performance Wesley Ketchum (University of Chicago)
Computer Networks IGCSE ICT Section 4.
Postgraduate Essentials University of Edinburgh Postgraduate Essentials Online induction to the course.
Fundamentals of Networking Discovery 1, Chapter 9 Troubleshooting.
Control and monitoring of on-line trigger algorithms using a SCADA system Eric van Herwijnen Wednesday 15 th February 2006.
Windows Server 2008 Chapter 11 Last Update
PVSS Installation of a Project Need to run this by Xiaofeng to make sure the steps are right.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Windows & The Internet. Objectives: Identify and use computer hardware Open and close a desired program Switch back and forth between open windows Create.
These materials are licensed under the Creative Commons Attribution-Noncommercial 3.0 Unported license (
Two Questions Coaching Program [Your Name] [Your Address] [Date] [please name the file: your-name-2questions.pptx] —e.g. bill-marshall-2questions.pptx.
NETWORK CENTRIC COMPUTING (With included EMBEDDED SYSTEMS)
4 September 2015 RE Meyers, Ms.Ed., CCAI CCENT ICND1 Exam Topics Review Describe the Operation of Data Networks: Network Diagrams and Data Paths.
MyIPFWAdvisor Project Status Presentation, 2 April 2012.
MCTS Guide to Microsoft Windows 7
1 Guide to Novell NetWare 6.0 Network Administration Chapter 11.
Software Tools and Processes Training and Discussion October 16, :00-4:30 p.m. Jim Willenbring.
Genesys Meeting Center End-User Technical Troubleshooting Guide (v1
1. There are different assistant software tools and methods that help in managing the network in different things such as: 1. Special management programs.
Hunter Valley Amateur Beekeepers Forum User Guide Guide shows sample screenshots with most relevant actions. Website is at
Sonia Kalwaney My Wiki site s.com.
…using Git/Tortoise Git
Information Systems and Network Engineering Laboratory II DR. KEN COSH WEEK 1.
Installation and Upgrade Campus-Booster ID : **XXXXX Copyright © SUPINFO. All rights reserved Solaris 10 installation.
Loosely Coupled Parallelism: Clusters. Context We have studied older archictures for loosely coupled parallelism, such as mesh’s, hypercubes etc, which.
Erik Blaufuss University of Maryland Data Filtering and Software IceCube Collaboration Meeting Monday, March 21, 2005.
Maintaining and Updating Windows Server Monitoring Windows Server It is important to monitor your Server system to make sure it is running smoothly.
By: Anuj Sharma. Topics covered:  GIT Introduction  GIT Benefits over different tools  GIT workflow  GIT server creation  How to use GIT for first.
1 OGM Presentation for Your Hospital Today. 2 The Ongoing Maintenance Program The OGM Program Components.
LHC BLM Software revue June BLM Software components Handled by BI Software section –Expert GUIs  Not discussed today –Real-Time software  Topic.
L0 DAQ S.Brisbane. ECS DAQ Basics The ECS is the top level under which sits the DCS and DAQ DCS must be in READY state before trying to use the DAQ system.
DEPARTEMENT DE PHYSIQUE NUCLEAIRE ET CORPUSCULAIRE JRA1 Parallel - DAQ Status, Emlyn Corrin, 8 Oct 2007 EUDET Annual Meeting, Palaiseau, Paris DAQ Status.
Configuration Mapper Sonja Vrcic Socorro,
Integrate, check and share documents Module 3.3. Integrate, check and share documents Module 3.3.
TrainingRegister® Training Management Software Maintain Permanent Training Records for Each Individual Monitor and Track Required Training Know Who Needs.
7200 Samsung Confidential & Proprietary Information Copyright 2006, All Rights Reserved. 1/7 OfficeServ 7200 Enterprise IP Solutions Data Server S/W Upgrade.
Running Queries - LV This presentation describes how to run Miquest queries on the EMIS LV system. You should have already created them from the spreadsheet.
TELL1 command line tools Guido Haefeli EPFL, Lausanne Tutorial for TELL1 users : 25.February
IPS Infrastructure Technological Overview of Work Done.
FTS monitoring work WLCG service reliability workshop November 2007 Alexander Uzhinskiy Andrey Nechaevskiy.
October Test Beam DAQ. Framework sketch Only DAQs subprograms works during spills Each subprogram produces an output each spill Each dependant subprogram.
Activity 1 5 minutes to discuss and feedback on the following:
Information Systems and Network Engineering Laboratory I DR. KEN COSH WEEK 1.
This was written with the assumption that workbooks would be added. Even if these are not introduced until later, the same basic ideas apply Hopefully.
CACI Proprietary Information | Date 1 PD² SR13 Client Upgrade Name: Semarria Rosemond Title: Systems Analyst, Lead Date: December 8, 2011.
CACI Proprietary Information | Date 1 PD² v4.2 Increment 2 SR13 and FPDS Engine v3.5 Database Upgrade Name: Semarria Rosemond Title: Systems Analyst, Lead.
62cm 64cm. DAQ status and Plans DAQ –Timing tuning –Which tools to learn (SC, Event monitor, GPIO, MIDAS, DIP, laser, storage, analysis) Plan with beam.
Fermilab Scientific Computing Division Fermi National Accelerator Laboratory, Batavia, Illinois, USA. Off-the-Shelf Hardware and Software DAQ Performance.
Information Systems and Network Engineering Laboratory II
One vs. two production environments
MiniDAQ2 Workshop Control System.
Top-Down Network Design Chapter Nine Developing Network Management Strategies Copyright 2010 Cisco Press & Priscilla Oppenheimer.
ProtoDUNE SP DAQ assumptions, interfaces & constraints
The Troubleshooting theory
Top-Down Network Design Chapter Nine Developing Network Management Strategies Copyright 2010 Cisco Press & Priscilla Oppenheimer.
Presentation transcript:

35t Readout Software John Freeman Dune Collaboration Meeting September 3, 2015

RunControl, DAQInterface, Configuration Manager and TDUControl (not shown, sends sync pulse at run start) Every run consists of a configuration and a set of components For a given configuration, 1-1 correspondence between a component, an artdaq boardreader process, and a FHiCL document initializing the process

Top N things DAQ operators should know Running check_daq_application.sh will tell you which of the four applications are running, as well as the most recently written logfile If you plan on using these applications, make a note of it in the e- log The two most important sites on the internet are: E-log: Wiki describing how to run the DAQ: daq/wiki/Running_DAQ_Interface Months of work have gone in to making this wiki as comprehensive as possible, while still retaining readability…

More?

MsgViewer Hot off the press: a program called MsgViewer now pops up whenever DAQInterface is launched Any messages sent via the lbne-artdaq’s DAQLogger module will appear in the viewer E.g., DAQLogger::LogError() << “Message”; will: Appear as “Message” in red in the viewer Send an alert up to run control containing “Message” Throw an exception, also containing “Message” For more info, see artdaq/wiki/Info_on_Using_DAQLoggerhttps://cdcvs.fnal.gov/redmine/projects/lbne- artdaq/wiki/Info_on_Using_DAQLogger The lbne-artdaq codebase should begin using DAQLogger, rather than cout/cerr or various group-specific logging mechanisms.

More?

The following four slides were provided to me from Erik Blaufuss, concerning upcoming plans for RunControl…

Run control status and plans

Current status Current run control functionality Control DAQ: configure, start and stop runs Select desired configuration from list Select desired components (SSPs. RCEs) from list Select run type (Physics/Test/Commissioning) Save a run summary DB record for each run includes: Start, stop times (UTC) selected configuration name selected component list run type DB records are (will be?) mirrored to public servers Accepts monitoring value reports from anyone (JSON over 0MQ)

Planned work Slow control values from HV/Cryo systems Alan H reported CSV files to shared directory Parsed, displayed and reported to Conditions DB Basic Web display Basic rate plots, Cryo/HV values plotted for recent time period Current run status information Help with documentation Suggestions welcome, now or as we start up….

Current UI plans

Recent Networking Issues (I) Several weeks ago now, the dumb switch the SSPs had been connected to was swapped out for a Cisco switch The connection to the SSPs stopped working After plenty of troubleshooting, the connection started working again when the switch was “dumbed down” – i.e., stopped sending spanning tree and CDP (Cisco Discovery Protocol) packets

Recent Networking Issues (II) As an outgrowth of this work, we studied the rate at which data could flow through the SSPs Each SSP’s corresponding fragment generator sends 200 fragments per second, but the size of the fragment is linearly related to the hardware trigger frequency Assuming backpressure isn’t occurring, which is indicated by orange (and then red) FIFO lights On the next slides, assume that the rates achieved were done without FIFOs complaining

Network dataflow study Max dataflow trigger period 1.7 ms (~590 Hz): 86 MB/s into lbnedaq1 115 MB/s into lbnedaq2

Some interesting results Running no ssp fragment generators on lbnedaq1 and N ssp fragment generators on lbnedaq2, data rate into lbnedaq2 achieved was N = 1 -> 43 MB/s N = 2 -> 86 MB/s N = 3 -> 98 MB/s N = 4 -> 116 MB/s N = 5 -> 116 MB/s Of course, true rates remain to be seen when we have everything at PC4 and 16 RCEs + the penn trigger board running in parallel with the SSPs There are several other lbnedaq nodes, so it will be worth studying the optimal way to allot the fragment generators on these nodes as well as potentially useful hardware upgrades (10 gigabit cables, more NICs, etc.)

A few “best practices” If you’re adding to lbne-artdaq, before you commit your changes to its central develop branch, make sure that lbne-artdaq still compiles and runs when you merge in your changes Corollary: since versions of packages lbne-artdaq depends on can and do get bumped up, it’s worth periodically checking out a clean copy of lbne- artdaq via “quick-start.sh” See artdaq/wiki/Best_practices_for_code_development for morehttps://cdcvs.fnal.gov/redmine/projects/lbne- artdaq/wiki/Best_practices_for_code_development If you update the configuration directory, make sure you git commit the configuration, otherwise DAQInterface will refuse to run Before contacting experts concerning the DAQ, your question(s) may already be answered in the daq/wiki/Running_DAQ_Interface

Conclusions The DAQ applications admittedly have a 1980s feel to them, but have been under development for over a year and are quite robust and as simple to use as flexibility allows Though if you have any ideas for improvements, please contact me at They’re also well documented MsgViewer has been a useful start, and hopefully over the coming weeks and months determining what the DAQ is doing in real time will become easier than simply trolling the logfile via “tail –f” Thanks to everyone who’s helped out!