Route#A1: SLAC-DESY, SLAC-SWITCH, SLAC-CESNET, SLAC-FZK, SLAC-NIIT, SLAC-TRIUMF
analysis data (6/22/04 - 9/29/04)
analysis perameters (xtr, dbcap,rtt)
...
Route | Events detected |
Multi-Route # 1 (Multi-Route Analysis) | 20 |
SLAC-CESNET *(Single-Route Analysis) | 14 |
SLAC-DESY // | 37 |
SLAC-FZK // | 39 |
SLAC-SWITCH // | 9 |
SLAC-NIIT // | 157 |
SLAC-TRIUMF // | 23 |
...
* single route analysed for the same time priod as that of multi-route #1 i.e., (6/22/04-9/29/04)
single route | Events | Full overlap to Multi Route # 1 | Partial Overlap to Multi Route#1 |
SLAC-CESNET | 14 | 3 | 0 |
SLAC-DESY | 37 | 5 | 1 |
SLAC-FZK | 39 | 8 | 0 |
SLAC-NIIT | 157 | 4 | 2 |
SLAC-SWITCH | 9 | 1 | 0 |
SLAC-TRIUMF | 23 | 2 | 0 |
Table 2: Overlap comparison of single route events to multi route # A events
Analysis of multi-route #A1 excluding one single route at a time
(1)Events detected in multi-route#1 | 20 |
(2)Events detected in multi-rout#1excluding SLAC-CESNET | 20 |
Overlapping events in 1 and 2 | 20 |
CESNET single route events overlapping with Events detected in 1 | 3 |
CESNET single route events overlapping with Events detected in 1 and 2 | 3 |
Table 3: Multi-route analysis of multi-route#A - CESNET
(1)Events detected in multi-route#1 | 20 |
(2)Events detected in multi-rout#1excluding SLAC-TRIUMF | 20 |
Overlapping events in (1) and (2) | 20 |
TRIUMF single route events overlapping with events detected in (1) | 1 |
TRIUMF single route events overlapping with events detected in (1) and (2) | 1 |
Table 4 : Multi-route analysis of multi-route#A - TRIUMF
(1)Events detected in multi-route#1 | 20 |
(2)Events detected in multi-rout#1excluding SLAC-SWITCH | 20 |
Overlapping events in (1) and (2) | 20 |
SWITCH single route events overlapping with events detected in (1) | 1 |
SWITCH single route events overlapping with events detected in (1) and (2) | 1 |
Table 5: Multi-route analysis of multi-route#A - SWITCH
COMMENTS
First three results (Table 3,4,5) show that corresponding single routes have no effect on multi-route analysis, Their expulsion from analysis provides the same result as in their presence
(1)Events detected in multi-route#1 | 20 |
(2)Events detected in multi-rout#1excluding SLAC-DESY | 20 |
Overlapping events in (1) and (2) | 3 |
DESY single route events overlapping with events detected in (1) | 6 |
DESY single route events overlapping with events detected in (1) and (2) | 3 |
Table 6: Multi-route analysis of multi-route#A - DESY
COMMENTS
Fourth result (Table 6) shows that corresponding single routes has some effect on multi-route analysis, its expulsion from analysis causes 50% events to be disappeared although generating some new events.
(1)Events detected in multi-route#1 | 20 |
(2)Events detected in multi-rout#1excluding SLAC-NIIT | 17 |
Overlapping events in (1) and (2) | 10 |
NIIT single route events overlapping with events detected in (1) | 6 |
NIIT single route events overlapping with events detected in (1) and (2) | 1 |
Table 7: Multi-route analysis of multi-route#A - NIIT
COMMENTS
Fifth result (Table 7) shows that corresponding single routes has great impact on multi-route analysis. Its expulsion from analysis caused 83% events to be disappeared and generating less number of new events.
(1)Events detected in multi-route#1 | 20 |
(2)Events detected in multi-rout#1excluding SLAC-FZK | 23 |
Overlapping events in (1) and ( 2) | 7 |
FZK single route events overlapping with events detected in (1) | 8 |
FZK single route events overlapping with events detected in (1) and (2) | 5 |
Table 8: Multi-route analysis of multi-route#A - FZK
COMMENTS
Sixth result (Table 8) shows that corresponding single routes has some impact on multi-route analysis. Its expulsion from analysis caused 38% events to be disappeared although generating number of new events.