Project

General

Profile

Artdaq "wish list" responses » History » Version 1

John Freeman, 01/12/2017 01:25 PM

1 1 John Freeman
h1. Artdaq "wish list" responses
2 1 John Freeman
3 1 John Freeman
# a computer running CentOS7 that has artdaq, lbne-artdaq, nodeJS, MongoDB, artdaq-database, etc. already installed.  This computer would be connected to a SLAC RCE with a 10 Gb link, could be connected to the CERN public network (or at least has a well-defined path in and out), and has a moderately large disk that can be used for writing data.  [this may be out of our control, but I've included it to set the stage]
4 1 John Freeman
# an instance of artdaq-database running in MongoDB that has pre-populated entries for 
5 1 John Freeman
## the list of available components:  e.g. 1 or more RCEs, 1 or more SSPs, 1 or more FELIX cards
6 1 John Freeman
## the locations where various BoardReaders should run
7 1 John Freeman
##	the possible locations of EventBuilders
8 1 John Freeman
##	possible location(s) of Aggregators
9 1 John Freeman
##	any other dataflow configuration parameters that are needed
10 1 John Freeman
##	a sample RCE BoardReader and electronics configuration - this can be a shell of what will be needed
11 1 John Freeman
#	the ability for an expert user to add another RCE to the list of components or modify the value of a dataflow parameter (mentioned in 2.5)
12 1 John Freeman
#	the ability for an expert user to add parameters to one or more RCE boards in the RCE BR/electronics configuration and the ability to add more boards to the configuration (mentioned in 2.6)  [ideally, this would be more sophisticated than "export the FHiCL file, edit it, and import it"]
13 1 John Freeman
#	a user interface that can present the list of available components to a user, when requested (this user interface and the ones mentioned below do *not* need to be graphical)
14 1 John Freeman
# a user interface that allows a user to pick a set of components to use for a given DAQ session
15 1 John Freeman
#	a user interface that allows the startup all of the artdaq processes
16 1 John Freeman
#	a user interface that shows the list of available Run configurations (also known as Detector/Electronic configurations) to the user and allows him/her to select one
17 1 John Freeman
#	a process that is smart enough to build the FHiCL files that need to be sent to the artdaq processes, given the selected Run configuration and readout components
18 1 John Freeman
#	a user interface that allows the configuration all of the artdaq processes
19 1 John Freeman
#	a (possibly simple) mechanism for automatically assigning unique run numbers
20 1 John Freeman
#	a user interface that allows a user to begin a run (without having to explicitly provide a run number)
21 1 John Freeman
#	archiving of the configuration that is used in each run
22 1 John Freeman
#	archiving of some amount of run history information, such as begin-run time, end-run time, and number of events in the run
23 1 John Freeman
#	a user interface that allows end run; and later, shutdown
24 1 John Freeman
#	as shown on slide 13, the "run control" scripts/application should interact with the Cfg Mgmt system to get the list of available components, etc.
25 1 John Freeman
#	I presume that the Process Manager that is mentioned in the slides will be John's DAQInterface plus pmt.rb
26 1 John Freeman
#	The FHiCL Document Creator may need to be created or DAQInterface may fulfill that role