Before running testdaq, create new steering files:

• on ultuna1: offeverything; on all; gotoiceboot; dtsxall

• on vertigo: mkdir ~/fat-x.y, cd ~/fat-x.y, and "autogen-wrapper" (make sure it is pointing to the correct hubs, and domhub-services must be running on all hubs)

testdaq will email error messages to a selected list of eminent physicists. To add or remove people, edit /home/testdaq/bin/checklogs.pl. If you do not want to get messages about certain doms, exclude them in checklogs.pl like so:    if (/Leukophobia/ || /Knut_Eriksson/ ||  /Karl_Sverkersson/)

Also, make sure you put the right ~/fat-x.y in the ~/bin/automate script


Running testdaq:
(on ultuna1)
offeverything
ready 

Output here

On vertigo:
go (Some comment about the run)

Output here

Data is produced in /home/testdaq/output(run number) directory
Data will end up in directory '/home/testdaq/latest_data'. 
After midnight, that data will be moved to '/home/testdaq/yesterdays_data'
Later on, data get sorted on the second disk /mnt/data, in a date structured directory tree.

Example: /mnt/data/2005/TestDAQ/month/day/
There is one directory created per steering file.

For FAT4 there are 47 steering files. 
The output is about 37 GB.
All data is copied continuously into ~/dropbox.  So you need at least 74 GB free space.
If you are satisfied with the data: for each run, move the corresponding xxx.sem-file from  ~/dropbox/semaphore_files to ~/dropbox (it is a good idea to copy it also into ~/dropbox/backup_semaphores)
After the move, the data in the dropbox will be scp:ed to Madison, and deleted as well as the xxx.sem file.
You can then delete the /mnt/data/2005/TestDAQ/month/day/whatever-run data from disk.


 Testdaq never ends, to stop it: 
"pausetestdaq" on vertigo until all outputxxxx files have disappeared, then:
“stoptestdaq” on vertigo
"stoptestdaq" on ultuna1
Force light sources off:
offeverything

In the beginning of the FAT, check you see rapcal pulses on the sync board by loading in a hit file in ezplot:
java icecube.testdaq.ezplot.Plotter

checking quality of the runs:
calculate the time each run took by going e.g. To directory '/mnt/data/2005/02/22' and doing
uu-log2time.sh
this will spit out the list of tests and their duration ( 7 to 10 minutes depending on the test type)