· clear out files in directory ~/domcal (eg. move the content to a directory ~/domtest(number of test)/domcal)

· dtsxinit ; testall ; domcal-wrapper

· domcal can take 90 minutes to run nowadays

· make sure domcal ran successfully on all doms (ls *.xml | grep domcal -c)

• Check for fail messages in nohup.out!!!!

· 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 “HV2DB” which makes a call to “java icecube.daq.domcal.HV2DB /mnt/data/testdaq/domcal"

check the hv in mysql again.
all xml output will end up in directory /mnt/data/tesdaq/domcal/ ,
and will overwrite the old xml files: you may want to save them first.  
The output on vertigo should be of this form.
This will create new .xml files in /mnt/data/testdaq/domcal/  (~15min)
There should be one .xml file for each main board with new dates. 
Check that the SIZE of the files about 350kB',
otherwise it means the calibration failed for those. The DOM xml files should be the same for all DOMs.
 
 
If an xml has not been created or updated (check the time of creation!), you can e.g. calibrate only that specific DOM:




 
 
java icecube.daq.domcal.DOMCal ultuna1 5025 1 /home/testdaq/domcal/ calibrate dom calibrate hv
--look up the DOM port (in this example, 5025) in the output of dtsxall-- 
output of the domcal is here