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]
an instance of artdaq-database running in MongoDB that has pre-populated entries for
the list of available components: e.g. 1 or more RCEs, 1 or more SSPs, 1 or more FELIX cards
the locations where various BoardReaders should run
the possible locations of EventBuilders
possible location(s) of Aggregators
any other dataflow configuration parameters that are needed
a sample RCE BoardReader and electronics configuration - this can be a shell of what will be needed JCF: I can work on getting this into the DB, although one thing I'm not clear on is this: do we need to get the info into the DB using conftool every time we install on a new host, or can we just copy the DB contents over? If it's the former it may make sense to wait until we have the computer running CentOS7 described above to avoid doing the same things more than once. Also, I should add that right now I have yet to add logic to DAQInterface to make the concept of "possible locations of EventBuilders and Aggregators" meaningful - i.e., DAQInterface doesn't currently care what hosts you specify for the processes, although of course pmt.rb might fail and cause DAQInterface to shut down if you specify hosts to which pmt.rb can't connect.
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)
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"]
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) JCF: with commit c2e614d16723a7a311cf59815ac7c707cd282263 in artdaq-utilities-daqinterface, the "./bin/listdaqcomps.sh" command will list the available components, although all this currently does is request DAQInterface to print the contents of .components.txt . Once we put the allowed components list into the database, I imagine we'll need logic to retrieve the list and then cat it to screen.
a user interface that allows a user to pick a set of components to use for a given DAQ session JCF: "./bin/setdaqcomps.sh <component1> <component2> ..."
a user interface that allows the startup all of the artdaq processes JCF: "./bin/send_transition.sh boot <daqinterface config>"
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 JCF: as I understood it from the meeting, this can be done from the command line with conftool
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 JCF: this is handled by DAQInterface using information received during the boot and config transitions
a user interface that allows the configuration all of the artdaq processes JCF: "./bin/send_transition.sh config <physics config>"
a (possibly simple) mechanism for automatically assigning unique run numbers JCF: With artdaq-utilities-daqinterface commit ca0846d8ad62604678e84d78daf73905c44cfc7f, when ./bin/send_transition.sh start is executed the script looks at the run #'s saved in the run records directory (defined in .settings) to determine the number of the most recent run, and sends the next run number as an argument to the "start" transition sent to DAQInterface
a user interface that allows a user to begin a run (without having to explicitly provide a run number) JCF: See above
archiving of the configuration that is used in each run JCF: The FHiCL documents used to initialize the artdaq processes are saved in the *.root files. Even without diskwriting on, data about the run is saved in the run records directory and if we're using the database, saved in the database as well. The script "compare_run_record_and_rootfile.sh" in artdaq-utilities-daqinterface can be used to confirm that the FHiCL documents saved in the run records directory and those saved in the output *.root file are the same.
archiving of some amount of run history information, such as begin-run time, end-run time, and number of events in the run JCF: handled via artdaq-utilities-daqinterface commits c995e54eec3f5f85675f26dc42a0e836ee827c35 (total events) and f556188156c9630f4466cba8a75f489024258392 (start and stop times)
a user interface that allows end run; and later, shutdown JCF: ./bin/send_transition.sh stop followed by ./bin/send_transition.sh terminate
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.
I presume that the Process Manager that is mentioned in the slides will be John's DAQInterface plus pmt.rb JCF: correct
The FHiCL Document Creator may need to be created or DAQInterface may fulfill that role JCF: handled in DAQInterface using information received during the boot and config transitions