I found three peaks in the DOM launch time during the data check.
The second peak (about 6 micro sec later from the main peak) is understood as the launch that had the first launch but couldn't satisfy the local conincidence condition (neighbor didn't got launched), so the first launch wasn't recorded.
Howerver, there is a third peak at around 25000 ns
Since I only plot here the first launch (the second or later was cleaned by a procedure), the peak should not corresponds neither second nor third launch.
I then checked the 2nd launch or more, that are ignored in the previous analysis. For this study, I only used data of run# 108981 (August 1st, 2007) (EHE filtered data (DOM#>80)).
In fact, I could not find any 3rd launch in the data.
These results are consistent with the hypothisis of that the 2nd peak is due to DOMs that launched but didn't have neighbors to satisfy the local coincidence condition.
However, I don't know how the 3rd peak is formed.
In order to know the nature of the 3rd peak, I plotted the position of DOMs for 3rd peak.
You see that the 3 peak events are correlated in a string.
I also checked those events by the event-viewer, taking those events randomly.
At first, those events are related to physical events and not just noises.
Some of those events looks quite OK. Most of them looks double coincident events, though the first event looks smaller than the following one (can be due to low statistics). I am not 100% sure this early coming events are really physical one. This can be noise. (cross-talk?) I also don't understand why those events make the 3rd peak in launch time if they are really double coincident events.
Comments are welcome!
Keiichi Mase Last modified: Sat Nov 10 15:25:52 JST 2007