Data Aquisition System To Do List
April 13, 2004.
Here is a list a items that need some time from each of us. I'd like
get comments and additions, too. This task list will change with
Of course, some tasks are ongoing, and some can be checked off.
Color coding of below "to do" items:
Tasks in black are yet to be done.
Tasks in blue are ongoing.
Tasks marked purple
are completed, or obsolete.
There is no monopoly on good ideas.
If anyone sees something that needs to be done,
or has a better way to implement something, lets talk about it.
General DAQ tasks:
- Understand the basic and current priorities
of the DAQ group.
- Become familiar with the DAQ code.
- Know how to take data.
- Understand how the overall system works,
even if just schematically.
- Find something you would like to document
and go for it. Said document would be posted to the web.
- Connect your local computer to the
MiniBooNE CVS repository, and keep a fresh copy of the DAQ
- Be able to run the AnalysisFramework on the
output of the DAQ to either make root or hbook files.
(some of the below may be delegated...).
- Manage DAQ and general data integration
- Do a final trigger timing study with Activity timers &
- Make scaler data avalable to the Live DAQ monitor.
- Automate Scaler DAQ startup ("init" script) on hal9002.
- Web documentation of the scaler DAQ operation & use.
- Produce chart or diagram of NIM inputs leading to trigger E-bits.
- Commence zerobias events when nearline, uberdaq, GUI ready.
- Documentation & web page.
Keep an eye on the documentation
needs in general.
- Documentation and specs on DAQ
output (what are the various
records and what kind of data is expected from the sources, i.e long
integer, etc; this info exists in the header files, but some written
document will be useful).
- Keep tabs on operations, and on how things
are going in the control room.
- Testing of overall system.
- Taking data and training collaboration
members on taking data.
- Work with Jon Link and Gordon on the
interface between the DAQ and the Nearline (UberDAQ). This mostly
includes management and accountability of data files.
- Sysadmin of the DAQ computers. Deal with
security issues & backing up the system.
- CVS code management, especially with
issuing DAQ software releases.
- Give talks to the collaboration on how to
run the DAQ.
- Documentation and protocol for shifters.
- Work with electronics group to iron out and
document problems with QT & Trigger system.
- Keep up with DAQ equipment & keep PREP
informed on loaned out equipment such as Monoboards, and NIM devices.
(or mitigate) trigger latency problem
"zerobias" event types following beam/strobe events.
with LANL to get scaler inputs working, and restart scaler DAQ.
- Incorportate rack temperature
from QT temperature monitoring into
Chris Cox's slowmon program.
- Live DAQ monitor online via
- Improvements to heartbeat,
- Complete software installation
of UPS power management.
- Work with Rex &
Richard to commission the new trigger boards when they are
- Reduce DAQ downtime:
- Manual end of run: trigger program does not terminate for and
END of run. assembler & streamer just change run number, file,
resets event number and other necessary variables and just starts a new
run on immediately. This will be only a couple of seconds of
- Automatic: In an error condition, send an END event to trigger,
not a pause, keep clearing tracker memories until no events are coming
down the various sockets, then send a START event to trigger.
Downtime should be about 10 sec or less between runs.
- Instigate the "manual" restart first, since it will be easier.
- Investigate further the QT FIFO
- Look at the problem from the
TSA driver standpoint.
- Update the LinuxTest
diagnostic tool so that we may be able to
catch the problem in the act and see if the problem is hardware or
- Work with Shawn & Chris
Green to setup hal9002 as a
development platform to be able to transition the DAQ (mostly PPC
cross-compiler) to newer Linux kernel.
- Setup the new DAQ scalar to run
- Help configure the QT
test stand used to repair QT & receiver boards, and do simple DAQ tests.
- Install Uninterruptible Power Supplies to
the DAQ rack. Plug network routers, serial terminal server, flat
panel display, tape drive and computers into them. Re-cable-tie the
- Add shm variables: rate for each event
type, begin & current event time.
- Better DAQ error checking.
- Supernova stream & error stream.
- Improve the driver code to handle QT FIFO
sync more effectively.
- Interface between the DAQ and a paging
- Work with Shawn, Jon, Terry, Chris &
Gordon to execute run control on "aux" data sources.
- Work with Jon, Shawn & Jen to clean up
the DAQ code and data structures.
- Work with Rex, Ben, and Shawn on the design
of the overall data structures.
- Integrate "Crate 13" data stream. This
will include muon data, scintillator cube data, booster
extraction signals, RF timing signals, target wall monitor
signals,etc. These data will come in a non-standard format and will
require special "qt" code to bring into the data-stream.
- Order & install three new HDs to
hal9000, and two new drives onto hal9004 & 9002 respectively.
- Get the DAQ running under the daqadmin
account and make basic running more user friendly.
- Routines for interpreting and working
with GPS time data. Put time into GPS (no leapseconds) mode.
- Checksum of boone_*.fc files and ".info"
data files which hold information on each data file for use in the data
- Update diagnostic programs, such as
read_data_dump that are in assembler/src with the new VERSION 3 of the
- Work w/Ben & Rex to get trigger sockets
- Compress.c quad design & saturated hits.
- Integrate the new GPS system into the DAQ .
- Install backup tape drive.
- Trigger studies.
- Help with monitoring the quality of the
- Trigger control, design, coding, and
- Manage beam timing project. Gordon (Los
Alamos), and Fermilab beams division (contact Rick Ford) and the Los
Alamos electronics group are also involved with this.
- Manage slow monitoring data
- Work w/ Andrew on QT FIFO sync
- Work w/Andrew to setup the
- Work w/ Janet Conrad to find
the best supernova triggering scheme:
- Which DET to use (4 or 5).
- What is the best hit threshold?
- Design & implement gamma
trigger if we do in fact want it.
- Work out the scheme to use
multiple trigger FIFO loads (longer
NIM inputs) to signal various calibration triggers: e.g. 300ns for
Laser, 500ns for muon tracker, 700ns for muon tracker + cube, ...
- Commission the new
trigger boards with the Los Alamos group.
- Upgrade the trigger code & structs.
- Design of the NIM trigger input crate .
- Scalar purchase for slow monitoring,
implementation and readout. This scalar also should be hooked
up to monitor certain trigger bits, like DET1, VETO1, BEAM, etc.
- Compress.c quads.
Ben Sapp (advisory):
- Keep up work on the driver code, driver
- Continue to make improvements to driver,
qt, assembler, etc. as needed.
- Work w/Andrew, Steve & Panagiotis to
run "ensure" in looking for memory leaks in the DAQ code.
- Trigger latency calculation.
- Get Hal9002 in same security "state" as
hal9004, so it can be connected to the outside in the same way as
9004. Andrew and Morgan can help.
- Get the DAQ software to be able to
handle multiple-day running without crashing.
- Make sure that different port numbers
are usable in the DAQ (other than "31415", for instance).
- Solve the recent assembler seg-fault
problem. Done by using different ways to assign memory to the strings
- Help with the TSA driver & monoboard kernel.
- Power PC compiling on Linux 7x platforms.
- Design of socket-based run control for auxiliary data
- Keep an eye on the
QT FIFO synch problem.
- Setup DAQ development cabability on
- halTalk & uberDAQ
- Command-line run control of the QT &
trigger monoboards (halTalk & qtControl).
- Write test program for exercising FIFO
readout of QT & investigate QT FIFO synch problem.
- Reorganize the /export directory.
- Create a "make install" directive so it is
easy for and end user to setup the DAQ software from scratch on the
- Get the DAQ running under the ~daqadmin
- Document the slomon rack
and slomon DAQ.
- Write code to process the
slow monitoring data.
- Complete slow monitor rack.
Los Alamos Electronics group--
Richard Van de Water, Nate Walbridge, Chuck Alexander, Richard
- Maintain communication with Andrew/DAQ
people regarding issues affecting front end electronics and DAQ.
- Continue work on HV systems & safety,
HV interlock (?), QT front end and power supplies.
- Ensuring that infrastructure (like
power supplies, grounding, clean & dirty power) are operating
- Monitor the health of the HV system.
- Build & install new trigger
- Fix DET3.
- Hardware to allow connections from the muon
system and other systems to plug into the auxiliary "QT" boards
in crate 13.
- QT crate temperature interlock &
interface with the DAQ (so it knows when data taking has stopped).
- Install the new GPS system.
- The crate 13 monoboard needs to be looked
- Work toward 24x7 running of the front end
and HV system.
- Acquisition and installation of a rack
mounted automatic paging system which is tied into the temperature
and HV interlock. This device also needs to be flexible enough
that it can take inputs from other systems, like nearline
- Correct the major hardware problems as
needed: front end noise problem, TSA bus, HV system, noise in
crate 1, etc...
- Connectors to the trigger
bus that will make counting and
- Get Nhit working on the
hardware side. For instance the
stuck bits from the sum PMT cards may need to be corrected.
- Have spare QT, pre-amp boards
associated gain resistors) available.
- Document the RWM operations and data format.
- Resistive Wall Monitor DAQ (RWM)
- uberdaq work with Jon Link, Shawn, and
- Help with physical UPS installation into
- RWM inputs to the DAQ.
- Maintain GUI, etc. on
shift computer, blueisland.fnal.gov.
- Run control perl scripts.
- Nearline monitoring software.
- GUI interface for DAQ
& UberDAQ control.
- Online monitoring.
- Add .info file functionality to the data
- Cyclic file-writing scheme for output of
- Complete setup the daqadmin account.
- Data file processing scripts (moving to
enstore, running on analysis framework, etc.)
- Online logbook.
- Integrate ACNET data into a
data stream. UberDAQ will then
acquire the data.
- Formal documentation of
operation of ACNET data-taking.
- Documentation on the
output structures and files.
- Documentation and streamlining of
- Calibration scheme data taking.
- Work with Los Alamos group to interface
muon system with "crate 13" QT boards.
- Routing of calibration and laser signals
(cables) to the trigger patch panels on rack 7.
- (obsolete) If needed, output of
laser system as c-structs that can be
shipped to the DAQ.
- Assist Jon with blueisland (the
shift computer on the 10th floor).
- Sysadmin help on DAQ computers
- System & hardware upgrades to hal9000-4.
- (obsolete) Assist in moving the
DAQ to the current Linux kernel.
- Help Andrew install the 3 new 36 GB
harddrives onto hal9000 along with better rack-mounting of the
- Setup sendmail so the notification system
can send a message from hal9000.
Panagiotis Spentzouris & Sam Zeller:
- Analysis Framework DAQ interface.
- Get Ensure running on Hal9000 with
- Provide enstore taping scripts (running on
hal9004) to ship the data to FCC from the NFS-mounted local disks.
- Enstore setup & help with
- Setup of Ensure onto hal9000, and
eventually hal9002 (the future DAQ development machine) to help
check for memory leaks.
- Also, you guessed it, bug Andrew about any
new applications that could help with operations or security of the