You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
References to LCLS1
Ford, Christopher
Mon 11/12/2018, 4:30 PM
Hi Mikhail,
Currently there is no documentation for the JSON messages, only prototype code.
Thanks,
-caf
See create_msg() and its context in collection.py:
https://github.com/slac-lcls/lcls2/blob/master/psdaq/psdaq/control/collection.py
The create_msg() function is also imported and used by a command line client, cmd.py:
https://github.com/slac-lcls/lcls2/blob/master/psdaq/psdaq/control/cmd.py
Control-level gui thoughts
O'Grady, Paul Christopher <cpo@slac.stanford.edu>
Thu 1/24, 10:40 AMDubrovin, Mikhail;Ford, Christopher
code is in psdaq/psdaq/control
interface is in collection.py
can run one (or more) dtiproxy in a standalone mode for gui development (caf will send an example)
requirements:
- asynchronous processes to watch for the completion of the transitions
- error display
- copy the lcls1 daq gui as closely as we can
- receive messages directly from many drp nodes using a zmq many-to-one pattern
- longer term, if we follow lcls1 model, this gui would also be used to managing detector configurations
preview: 'daqstate' CLI for DAQ
Ford, Christopher <caf@slac.stanford.edu>
Thu 1/24, 12:06 PMO'Grady, Paul Christopher;Weninger, Clemens;Dubrovin, Mikhail
The brief demo below shows
three LCLS-II DAQ transitions (plat/alloc/connect) being automated by
the new 'daqstate' CLI. Two instances of dti_proxy were running at the
time, as shown by 'showPlatform.'
I intend to commit 'daqstate' to git this afternoon. Then, I will add an updated demo to Confluence.
Thanks,
-caf
(ps-0.1.2) -bash-4.2$ daqstate -p1
reset
(ps-0.1.2) -bash-4.2$ showPlatform -p1
Platform | Partition | Node
| id/name | level/pid/host
---------+----------------+------------------------------------
1 1/(None)
(ps-0.1.2) -bash-4.2$ daqstate -p1 --state connected
connected
(ps-0.1.2) -bash-4.2$ showPlatform -p1
Platform | Partition | Node
| id/name | level/pid/host
---------+----------------+------------------------------------
1 1/(None) drp-no-teb/19944/psbuild-rhel7-01
drp-no-teb/19916/psbuild-rhel7-01
(ps-0.1.2) -bash-4.2$ daqstate -p1
connected
(ps-0.1.2) -bash-4.2$
Weaver, Matt <weaver@slac.stanford.edu>
Thu 1/24, 12:22 PMO'Grady, Paul Christopher;Dubrovin, Mikhail;Ford, Christopher
You can execute the DAQ on drp-tst-dev011 by running
cd /reg/g/pcds/dist/pds/tst/scripts
../../tools/procmgr/procmgr start testgui.cnf
../../tools/procmgr/procmgr stop testgui.cnf (when you're done)
The IP address of
drp-tst-dev011 appears in testgui.cnf. You can replace it with some
other node. Don't try to run fast, because the event data is getting
broadcasted on the cds-tst network (since we don't have
a FEZ or multicast filtering).
-Matt