Status of KM3NeT Detector Manager

1. Status of KM3NeT Detector Manager Cristiano Bozza University of Salerno / INFN Oct 31st 2014 Manythanksto T. Chiarusi, R. Bruijn, V. vanBeveren, A. Albert, C. Pellegrino, PieterJansweijer, K. Graf, M. Circella, T. Gal forsupport, discussion and advice!

2. Status of KM3NeT Detector Manager • What CU-DM does • Control one or more CLB’susing a flexibleconfiguration (no hardcodedparameters) • Remember the last status even in case of processkill • Write Datalogfiles to keeptrack of allevents and data • Write human-readable log files • Expose data for realtimemonitoring • Depend on centralizedauthentication for service startup • Provide a GUI interface • Allowmanual control • Allow multiple GUI interfaces for diverse purposes Cristiano Bozza – University of Salerno/INFN – Oct 2014

3. Status of KM3NeT Detector Manager • What CU-DM doesnot(yet) • Authenticateusers to the centralizedauthentication provider • Transmitmonitoring data toROyWebtomakeplots • Take data from DB • Runsetup and Detector files are static • Runsetup/Detector file format in DB-compliant format • Some work isneededtoshrinkthem down: with 104-105 PMT’s individualsettingsmightreallymake the fileshuge Cristiano Bozza – Universityof Salerno/INFN – Oct 2014

4. Status of KM3NeT Detector Manager • What CU-DM does and shouldnot do • Allowsettingrunnumber • Allowsetting detector • Allowsettingrunsetup • Allowsetting the target • Thesetasksshould be left to the CU Manager for centralizedoperation • For the purpose of development and debugging, theyhavebeenprovidedbutwill be removed in the finalversion Cristiano Bozza – Universityof Salerno/INFN – Oct 2014

5. Status of KM3NeT Detector Manager • Interfaces • Console mode (Command line) • Configure DM • Startup/shutdown DM • Archive logfiles • Define the current target • Define the currentrunsetup • Define the currentrunnumber • Define the current detector • GUI (Web-based) • Query runtimeparameters • Monitor a CLB • Design user-defined control panels • Define the current target • SAWI (Web-based) • Notify target change • Notify detector change • Notifyrunnumberchange • Notifyrunsetupchange Cristiano Bozza – Universityof Salerno/INFN – Oct 2014

6. Status of KM3NeT Detector Manager • Developingyourown GUI • Custom GUI’s can be used to automatetests • Standard GUI worksthrough HTTP, no «backdoors» • Get a security token (login) • Read data usingvirtual directory for MON parameters • SendcommandsusingURL’s • Instructions on Wiki Cristiano Bozza – Universityof Salerno/INFN – Oct 2014

7. Status of KM3NeT Detector Manager • Version 0.9 deprecated • Version 0.91 functional, stillbugged • Current SVN «bin» versionrunning: • DM testedat NIKHEF, 1 CLB • DM testedat Bologna test bench, 4 CLB’s • DM tested in Catania, 2 CLB’s • Release planned in the nextdays • Exe upgrade possiblethrough SVN • no recompilationneeded Cristiano Bozza – Universityof Salerno/INFN – Oct 2014

8. Status of KM3NeT Detector Manager • Interactive parametersetting • Requiresswitch from «auto» to «manual» mode • Authorization by LocalAuthenticationProviderisrequired • Parameter set with 4 possiblescopes: • 0: by UPI (for PMT’s and array parameters) • 1: by DOM • 2: by DU • 3: by Detector • Scopes 2 and 3 requirethateachindividual DOM be switched to «manual» Cristiano Bozza – Universityof Salerno/INFN – Oct 2014

9. CU activities • Currentactivity on DM • Working with Vincent to reduce threadspawningwhenCLB’s are unreachable • Working with Vincent to removeprogramhangatshutdown • Vincent has made a new SVN check-in yesterday– testsongoing • «QA» on program: individualsupport to users to track and fixbugs • Currentactivity on TriDAS Manager • CHOO (ControlHost) porting to C# Cristiano Bozza – Universityof Salerno/INFN – Oct 2014