To-do list 27-Dec-2012 » History » Version 12

« Previous - Version 12/48 (diff) - Next » - Current version
Alessandro Razeto, 12/29/2012 04:08 AM

To-do list 27-Dec-2012

KAB - some notes on things to do (ordering and grouping is rather arbitrary)

  1. SCF - get PMT working with latest boardreader and eventbuilder apps
    • include both single-node and multi-node running
  2. SCF - modify the init, startRun, and stopRun scripts to use the PMT cfg file
  3. finish documenting the initialization PSet contents
    • this should include whatever code modifications are needed to get the hard-coded paths out of the PSet strings
  4. SCF - test the stopping and restarting of runs with real V1720 readout. Fix any problems that are uncovered.
  5. merge the latest feature/pmt branch code to the develop branch, when appropriate
  6. update the instructions on the Wiki pages to change references to the feature/board_reader branch to the develop branch
  7. plan for a simple demo system that Stefano can use in his System Control tests (document the use of it on the Wiki)
  8. refresh our memory of what the shutdown command should do, and add that to the applications
  9. look into improving the filenames on disk (see art and artdaq Redmine issues, esp. art #3189)
  10. look into feeding the initialization string directly to art (art Redmine issue #3191)
  11. look into supporting multiple fragment generators within a single boardreader app
  12. write a simple "event dump" application that we can use on the disk files that we create to verify that the data makes sense (number of events, number of fragments in each event, etc.)
  13. investigate the drop in maximum rate (from 55 to 50 Hz) when running the full system (compared to just
  14. document the plan for providing events to online data quality monitoring applications
  15. document the C++ classes in ds50daq
  16. remove junk code ( and move higher level code to a different dir (DS50CompressedEvent.hh which in turn should be renamed V172xCompressedFragment).
  17. modify V172xFragment to know how many bits are valid (request from Marc)
  18. SCF - look into forcing real-time priority for DAQ processes (MPI program elements)
  19. re-check the initial fragment number assignment and testing in V172xDriver_generator
  20. start using a set of directories to provide named configuration sets. A proposed schema is the following:
    • <baseDirectory>/<configurationName>/<applicationName>_def.fcl (will contain the defaults within BEGIN_PROLOG ... END_PROLOG)
    • <baseDirectory>/<configurationName>/<applicationName>_<machineName>_<portNumber>_<on|off>.fcl
    • <baseDirectory>/runs.txt (list of runs with start time, stop time and configuration name)
    • PMT and the SC will be given the configuration name and they will loop on all <applicationName>_<machineName>_<portNumber>_on.fcl files: the content of <applicationName>_def.fcl will be prepended.