Vertigo is the string processor and database holder.
An introduction to mysql databases (vertigo)
Look into the link:http://icecube.wisc.edu/~krasberg/fat/how_to_start_a_fat/how_we_started_uw_fat_09.html
The information is repeated here, with local modifications for Uppsala (it is a bit out of date, the link above is therefore what you should use!).
1) plug in all DOMs into the DFL
2) on ultuna1: make sure /usr/local/python/dtsxall will pick up all DOMs
cat `which dtsxall`
echo "communications for cards 0 thru 7, 64 DOMs, ports 5000 to 5063 ..."
echo "starting 64 different subprocesses..."
/usr/local/hutil/dtsx -p 5000 /dev/dhc0w0dA &
/usr/local/hutil/dtsx -p 5001 /dev/dhc0w0dB &
/usr/local/hutil/dtsx -p 5002 /dev/dhc0w1dA &
etc.
3) on ultuna1: make sure /usr/local/python/domnames.dat is up-to-date
10dbd5f897a7 | Abrahamsberg |
7dd7dbc1e5aa | Akalla |
40f14ab43b31 | Kista |
8a6763d90eb5 | Alby |
b3732fdb626b | Odenplan |
b5e30e459da4 | Tensta |
etc
4) on ultuna1: edit ~/bin/monitor so that it will ask for info on all DOMs
monitor.py 0 0 a &
#monitor.py 0 0 b &
monitor.py 0 1 a &
#monitor.py 0 1 b &
monitor.py 0 2 a &
monitor.py 0 2 b &
monitor.py 0 3 a &
etc
5) on ultuna1: move /home/testdaq/monitor/monitor.dat so we start fresh
6) on ultuna1: "on all", "gotoiceboot", "dtsxall", 'cd monitor' , "monitor"
the file monitor.dat will be used later. This file should be scanned for DOMs which have pressure leaks and for DOMs which have zero scaler rates...
1) If STF was run in production room, then do this
cat prod_id.sql | mysql -u penguin domprodtest > newdoms.txt
2) If the domids are not in the database yet, then make a file called newdoms.txt which has a list of domids and mainboard ids such as (note that the FIRST LINE NEEDS TO BE SOME KIND OF HEADER LINE):
This is the first line of
newdoms.txt, since prod_id.sql creates a header line...
TP5P0581
347fd0110547
UP5P0582 ec54677bbb9e
TP5P0583
a3ae4b646a70
the file newdoms.txt will be used later (note, in this example, two of the fields were NULL because the production room typed in the domids incorrectly during testing and overwrote already existing DOMs - it is very common for people to remember domids incorrectly)
copy file monitor.dat to vertigo
copy file newdoms.txt to vertigo
run " StartFAT.pl step1" from the directory with the above two files
this will print out a summary like this:
total number of unknown (monitor) doms = 42
total number of known (monitor) doms = 9
total number of
found unknown (newdoms.txt) doms = 42
total number of found
unknown T doms = 18
total number of found unknown U doms = 14
total number of found unknown A doms = 10
MAKE SURE THE SUMMARY ABOVE IS CORRECT ! THIS IS VERY IMPORTANT, OTHEWISE YOUR DFL MIGHT NOT BE LOADED RIGHT
run " StartFAT.pl step2"
this time you will be asked the NAME of each new DOM. Names are best if they are short in length and have themes whereby you can associate NAMEs with particular FATs later on (for example, at pole we wanted to put DOMs from particular FATs last year near the bottom of the string)
a file called InitializeNewDoms.SQL will be created
to enter the info into the database you do this (do loginsql before to get the passwd)
mysql fat -u tester -p < InitializeNewDoms.SQL
clear out files in vertigo directory ~/domcal
"on all", "gotoiceboot", "dtsxall" on ultuna1, "domcal-wrapper" on vertigo (make appropriate edits to domcal-wrapper first)
EXAMPLE:
echo "running calibrate dom calibrate hv on on ports 5001 to 5061 "
nohup java icecube.daq.domcal.DOMCal ultuna1 5001 54 /mnt/data/testdaq/domcal/ calibrate dom calibrate hv &
echo "running calibrate dom calibrate hv on on ports 5063 "
nohup java icecube.daq.domcal.DOMCal ultuna1 5063 1 /mnt/data/testdaq/domcal/ calibrate dom calibrate hv &
echo "running calibrate dom on the 2 syncboards "
nohup java icecube.daq.domcal.DOMCal ultuna1 5000 1 /mnt/data/testdaq/domcal/ calibrate dom &
nohup java icecube.daq.domcal.DOMCal ultuna1 5054 1 /mnt/data/testdaq/domcal/ calibrate dom &
Use 'ps -ef on ultuna1 to get the proper telnet ports.
domcal can take 90 minutes to run nowadays
make sure domcal ran successfully on all doms (ls *.xml | grep domcal -c)
it is a good idea to histogram the domcal HV fits and make sure that they make sense
(note, this program has to be able to open an xterm):
java icecube.daq.domcal.HVHistogramGrapher {indir} {outdir} {base} Example:
java icecube.daq.domcal.HVHistogramGrapher /home/testdaq/domcal/ /home/testdaq/public_html/domcal/ ./
then load "hv.html" into a browser.
Do not forget to put HV values into domtune database using "java icecube.daq.domcal.HV2DB /mnt/data/testdaq/domcal"
on ultuna1: 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)
enter command updateDB.pl
you can either enter the lcmodes one-at-a-time, or enter "99" and then edit the file later (lcmode 0 is for ref boards and isolated DOMs, 1 is normal DOMs within a string, 2 is if there is no DOM below (T DOM only) and 3 is if there is no DOM above on the string). Remember, the "B" or "U" DOMs are above the "A" or "T" DOMs for DOMs on the same wire pair - "on all" prints the pairs in reverse order by the way
update lcchain-wrapper on vertigo to operate on the right DOMs.
then update the domtune database with "mysql fat -u tester < updateFAT.sql"
Enter all traveller information you can into the database on vertigo:
loginsql
use fat; example:
update doms set start_date='2005-04-12',pmtserial='TA1169',hvserial='000450',sphereserial=71097,mbserial='001252' where name='Akalla';
select * from doms where name='Akalla';
Example of what can be filled in (fill in more if you find the data!):
serial | domid | name | start_date | pmtserial | hvserial | sphereserial | mbserial | mbid | bfserial | seal_date | humidity | seal_pressure | pentorque
__________________________________________________________________________________________________________________________
4 | UP4H0026 | Bluetooth | 2004-08-04 | TA0176 | 000219 | 71129 | V5.0L000464 | d030f9de4010 | NULL | NULL | NULL | NULL | NULL |
Note: there is a special discriminator setting in domtune for the sync board
it is necessary to make a special spe threshold discrimator setting of
700 and mpe thres. disc. of 650 for the sync board at UPPSALA prior to generating FAT
steering files.