Project

General

Profile

DaqTaskMeeting 5242011

DAQ tasks meeting:

LSST - start date ~ June 1, 2011

ADM 1 Establish project and working environment, including dependent products.
ADM 1 RTEMS setup under VM either on cloud or on oink
DES 2 Design experiment that will answer questions posed in the work proposal.
PORT 2 Start evaluating the port to RTEMS.
DDS 2 configuration and use specification.

NOvA -

DCS 1 user interface (control room) work.
DCS 1 archiver application.
DCS 2 integration with run control states.
DCS 3 design for far detector.
DCS 2 new device scan procedure (maybe result array support?).
DCS 3 additional DCM status and other devices.
DCS 2 training new people.
DCS 3 interface with accelerator controls system.
DDT 2 shared memory exchange.
DDT 3 art input source
DDT 3 algorithm port and product definitions
DDT 3 trigger result output module.
DDT 3 test facility.
EVB 2 multithreaded event search and construct algorithm
EVB 2 configuration, socket buffer sizes, logging mask, etc..
DCM 2 memory test, ECC aware.
DCM 2 diagnostic check-out suite, will Sue’s do the job? (encapsulation as unit/integration tests)
MSG 3 separate domain participant for each DDS connection
MSG 1 maintenance and upgrades (as needed)
MSG 2 handling sigstop and sigcont in a DDS-using application
MF 2 organize configuration files and provide method to store and use options properly
MF 3 message viewer performance when lots of messages are displayed
CFG 1 run config into DB, providing GUI tools to manage data in DB
ERR 1 error handling diagnostic rule engine from mf messages
ERR 2 use of the rule engine, including GUI and DB perhaps to manage the configuration
APP 2 application management in production (managing state of applications on nodes)
ADM 3 release management and building DAQ software, aiding in constructing releases and testing
ADM 2 development of standard linux configuration parameters and startup procedures
ADM 2 linux distribution for DCM/TDU (mostly documentation)
TST ? load testing will continue
DRV 3 driver code support for TDU and perhaps communications with FEB (register writes verified)

note: far detector might generate more work depending on how well things scale.

mu2e - priority item by mid July

LT Update configuration to work with same-node detector.
LT Update configuration to work with the fixed scheduling algorithm.
LT Create a performance model that can predict resource needs.
LT Add art trigger framework to the load simulator.
LT Run the tool and analyze the results.
PRJ Planning within phases continues (1)
PRJ answering questions from previous review (1)
PRJ project setup, including fact repository (2)
CTL EPICS/labview slow controls / DAQ for test stands and other testing (early standardization work)
CTL alternative technologies for experiment software in the DAQ area (flex for example)
REQ collecting requirements from offline simulation, such as algorithm performance and event ordering (2)

uBooNE - now for priority one items

Test stand setup and maintenance (1)
Understand the scope and components that we will be responsible for. (1)
List of tools that can be used to construct this system (1)
Propose way to develop a modern, maintainable software system. (what should this be?) (2)
Show simple prototype of modern tools used for similar problem. (2)
Slow controls - because they want to manage node configuration and monitoring
slow controls - perhaps with training