Differences

This shows you the differences between two versions of the page.

--- lydaq_install [2018/03/28 05:43]
acqilc [Structure]
+++ lydaq_install [2021/07/10 23:21] (current)
@@ Line 1: / Line 1: @@
 ====== LYDAQ installation ======
+Documentation {{ :daq_doc.pdf?600 |}}
 ===== Linux version =====
@@ Line 19: / Line 21: @@
   * During the installation a passphrase is required, use the usual acqilc one.
+===== Debian package (binaries only) installation =====
+It works only on debian jessie amd64 architecture:
+   * Download the package [[https://cms-wiki.ipnl.in2p3.fr/software/lydaq_1.0_amd64.deb|lydaq]]
+   * Run ''sudo dpkg -i lydaq_1.0_amd64.deb''
+The binaries of the software is install in ''/data/daq'' and in ''/data/root''
+==== New version ====
+  * [[https://cms-wiki.ipnl.in2p3.fr/software/lydaq_1.01_amd64.deb|lydaq 1.01 amd64 (pc 64 bit Debian jessie)]]
+  * [[https://cms-wiki.ipnl.in2p3.fr/software/lydaq_1.01_armv7l.deb|lydaq 1.01 armv7l (raspberry raspbian wheezie/jessie)]]
+==== Complete raspberry jessie image (ready to use) ====
+  * [[ftp://lyoftp.in2p3.fr/mirabito/raspbian_jessie_lydaq.img| copy it and change hostname ]]
 ====== LYDAQ Configuration ======
@@ Line 77: / Line 96: @@
   * "publish": "tcp:\/\/*:5555", publish port to DIFSERVER
   * "state": "TestChamberLPC", the DB state
+=== Monitoring applications ===
+Each slow control application has 3 mandatory parameters:
+   * "TCPPort": 5600, the publication port
+   * "location": "DOME_STACK", The location of the monitor hardware
+   * "period": 30, the period of monitoring in second
 ==== Example ====
@@ Line 266: / Line 295: @@
 }
 </code>
+===== Managment of JSON file=====
+In order to store data in the Oracle DB you need a login and password. Please contact Guillaume to get one if you don't know it.
+==== Storage of a file ====
+Access the [[http://daqcontrol.ipnl.in2p3.fr/login.html|DAQ control]] page.
+Go to ''Manage Configuration'' page,end of page and create ''New configuration''
+Choose your file and create. Then you must click once on your configuration to have it surrounded by a red line, i.e, it is available
+==== List  files and access it ====
+With the same account goto [[https://ilcconfdb.ipnl.in2p3.fr/config|ilcconfdb]] , you will have a list of all registered configuration
+To access one go to [[https://ilcconfdb.ipnl.in2p3.fr/config-content/chamber_stack_lpc_2|one example]] where the last name is the name of the config.
+====== LYDAQ Usage ======
+===== DAQ control interface =====
+The [[http://daqcontrol.ipnl.in2p3.fr/login.html|DAQ control interface]] is accessible from anywhere but the browser should be able to send http commands to the DAQ computers. It should be either in the same network or accessible via SOCKS proxy using a dynamic ssh tunnel.
+Once logged in, you can choose the configuration used and control the DAQ whatever the current status is.
+The list of command and the sequence of acquisition is the same as the one described in the command line interface bellow (one name differs PREPARE instead of daq-service).
+===== Command line interface =====
+==== The .daqrc file  ====
+This file defines 2 aliases and for each of them the login to be used and the configuration file. It then launch the //fdaq// script
+<code>
+alias slccontrol="export DAQLOGIN=cmsLyon:RPCxxxxx;export DAQURL=https://ilcconfdb.ipnl.in2p3.fr/config-content/stageM2_daq_2;/opt/lydaq/apps/bin/fdaq.py"
+alias daqcontrol="export DAQLOGIN=cmsLyon:RPCxxxxx;export DAQURL=https://ilcconfdb.ipnl.in2p3.fr/config-content/Testchamber2_23022019;/opt/lydaq/apps/bin/fdaq.py"
+</code>
+** this file should be sourced in the .bashrc **
+=== Job control ===
+  * **create** , //daqcontrol --jc-create //, initialise job control
+  * **start** , //daqcontrol --jc-start //, start all processes
+  * **kill** , //daqcontrol --jc-kill //, kills all processes
+  * **destroy** , //daqcontrol --jc-destroy //, allow new initialisiation with a different file for job control
+  * **status** , //daqcontrol --jc-status //, Lists status of all processses
+=== Data acquisition ===
+  * **create**, //daqcontrol --daq-create //, initialise the FDAQ process
+  * **discover**, //daqcontrol --daq-discover //, Ask FDAQ to initialise all processess described inthe configuration file
+  * **service**, //daqcontrol --daq-service //, configure services like Event Builder, DB server, Trigger control
+  * **initialise**, //daqcontrol --daq-initialise //, initialise DIF server access
+  * **configure**, //daqcontrol --daq-configure//, Configure DIFs and ASICs
+  * **start**,//daqcontrol --daq-start//, start a new run
+  * **stop**,//daqcontrol --daq-stop//, stop the run
+  * **destroy**,//daqcontrol --daq-destroy//, go back before the **initialise **
+== Status ==
+  * **state**,//daqcontrol --daq-state//, Current state of the Daq
+  * **status**, //daqcontrol --daq-status//, List the status of all DIFs
+  * **Event builder**, //daqcontrol --daq-evbstatus//, run and event writen
+Normal sequence from scratch:
+  - daqcontrol --jc-create
+  - daqcontrol --jc-start
+  - daqcontrol --jc-status
+  - daqcontrol --daq-create
+  - daqcontrol --daq-discover
+  - daqcontrol --daq-service
+  - daqcontrol --daq-initialise
+  - daqcontrol --daq-status
+At this stage the DIFs should all be initialised
+  - daqcontrol --daq-configure
+  - daqcontrol --daq-status
+At this stage all the DIFs should be CONFIGURED all OK
+Then one can start and stop runs
+  - daqcontrol --daq-start
+  - daqcontrol --trig-resume
+  - sleep 7200 (wait 2 hrs)
+  - daqcontrol --daq-stop

IP2I CMS Wiki

User Tools

Site Tools

Differences

Page Tools