IceCube related Work
IceCube DOMMB V2 Tests
Ongoing discussion minutes on the "Hit" definition for IceCube (in progress)
Status report for String-18 analysis (in progess)
Buffered data from 3 DOMs at pole, (a few seconds worth of hits including the new ADC info) and a script to parse them
Two-DOM-per-twisted-pair study: Study of effects of an unterminated twisted cable (high impedance)
DOM Waves for Feature Extraction Studies Mar 2002
String 18 Commissioning Talk at Berkeley Collaboration Meeting March 2002
String-18 workshop (session 11 of Berkeley AMANDA/ICECUBE collaboration meeting march 2002)
TAUP IceCube talk
Flasher Studies: Lab Measurements
Flasher Studies: Measurements at Pole
of problem channels from Feb 2002: Analog/DOM/DOMCOM/other
The list above have information about bad DOMs, bad ATWDs, bad bases, and also surface hardware related problems.
Info is also included for the analog problems.
Cable Length Data from New 2002 DOMCOM Hardware
After the successfull installation at pole by
K.H. Sulanke of the new version
of the surface electronics, I took some data of cable lengths for all the 37 DOMs
that are connected. The tar file containing the 37 gzipped files.
These data is mainly useful for the experts to verify calibration codes
and study the systematics of the cable delay measurement and the
time synchronization as well as clock stabilities, etc.
New Data: UTC time
stamps for the DOM quartet corresponding to Days 149-163.
Data format is day and sec within the day (Jan 1 2001 is 1)
Here is a tar file with waveforms and UTC time-stamps from DOM-Quartet .
The files dom10xx.utc_stamps.dat contain the list of the UTC time
the individual waveforms from file waveforms_dom10xx_utc.dat.gz (in 1-to-1 correspondence).
Where xx is 11,38,23, the DOM ID, which corresponds to the following AMANDA
|DOM ID||Ch.||TB ID||depth (m)||z(m)|
The hits were taken with a hardware Local Coincidence requirement
with a ~1 usec window. The time elapsed is of about 4 hours,
starting at (UTC) ~23:43 of day 149.
The actual livetime in these file is actually about a factor of
10 lower because of the small duty cycle.
The UTC time stamps have been checked against the AMANDA
time stamps for a subset of downgoing muons. At present you can
expect ~ 10-20 usec of overall offset between AMANDA and DOM
The waveform files have 4x128 = 512 lines per PMT hit.
The first 128 (channel 0 of ATWD) are the high gain PMT pulse (x10).
The following 128 (channel 1 0f ATWD) are the low gain pulse(x2).
The following 256 lines should not be of interest to the "general public".
A few lines to display wavesforms in paw would look something like
* showing only the high gain channel
* create a vector to put the first 100 waves
* 128 samples
* 4 channels
v/create waves(128,4,100) r
v/read waves waveforms_dom10xx_utc.dat
DOM Waves for Feature
Extraction Studies Mar 2002
This tar file contains files of waveforms from three DOMs in the ice taken in Mar 2002.
DOM 1025, 1023, 1034 (the deepest three in the string) for three different triggering conditions:
1. pedestal 2. spes without local coincidence and 3. spes with local coincidence.
Here's a sample from each (for DOM1025):
2. spe trigger without Local coincidence requirement
3. spe trigger with Local coincidence requirement (here's an extreme
The type of trigger can be deduced from the time stamp in the filename,
the runs were taken in the
time sequence 1,2,3.
Notice that the files are in the DomLogger format (ascii but you will
need parsing of the data).
Notice also that for each DOM there are two ATWDs and the data for both is present in the data files:
A line like this at the beginning of the waveform signals a waveforms from ATWD0
DOM 1033 ATWD0: 1036 bytes, FIDUCIAL 0xaa000000 TRIG 0xcc7919b0,0x1000
and correspondingly ATWD1 for the other.
Also, remember that for each ATWD vaveform there are 4 channels (ch0...ch3),
which are the
high-gain, low-gain, spare-for-now, shaped-clock.
Please send email if something is unclear about the data.
Please let me know of comments/questions at