forked from grbhess/grbhess.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
115 lines (101 loc) · 5.24 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
<html>
<link rel="stylesheet" href="./css/w3.css">
<head>
<meta http-equiv='cache-control' content='no-cache'>
<meta http-equiv='expires' content='0'>
<meta http-equiv='pragma' content='no-cache'>
</head>
<style>
</style>
<body style='margin-top:20;margin-left:20;margin-right:20;' onload=loadTable()>
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js"></script>
<script>
function formatTable(content){
var dataArr = content.split("\n");
//for each line in array
$.each(dataArr,function(){
if (this != "") {
//split line and create row
var row = new String("");
valArr = this.split(",");
row += "<tr>"
$.each(valArr, function(){
row += "<td>" + this +"</td>"
});
row += "</tr>"
//Add row to table
$('tbody').append(row);
}
})
}
function loadTable()
{
var content;
//Parse CSV File
//split on new line
fetch("obstable.csv") //here you would put the url of the file (if it's in the same directory just the name should suffice
.then((response) => response.text())
.then((data) => formatTable(data));
// .then((data) => console.log(data))
}
</script>
For an explanation of the columns and entries, please <a href="#explanation">click here</a>
<br></br>
<div class="w3-container, w3-responsive">
<table class="w3-table-all" style='font-size:90%'>
<thead>
<tr>
<th> GRB ID </th>
<th class="w3-center"> Triggering<br>instrument</th>
<th class="w3-center"> Alert time (T0)</th>
<th class="w3-center"> GRB RA (J2000)</th>
<th class="w3-center"> GRB Dec (J2000)</th>
<th> H.E.S.S. window start</th>
<th> H.E.S.S. window end</th>
<th class="w3-center"> Obs mode</th>
<th class="w3-center"> Reaction</th>
<th> Contact</th>
</tr>
</thead>
<tbody>
</tbody>
</table>
<p></p>
<p>
<br><font size="+1">Summary</font></br>
<br id="explanation">
The above table summarizes H.E.S.S. GRB observations since the most recent camera upgrade in late 2019. It includes <i>completed</i> observations as well as <i>planned</i> ones.
<b>Please note that planned observations are subject to external effects such as weather conditions and technical difficulties, as well as burst advocate decisions, and are not guaranteed.</b>
In general, the H.E.S.S. burst advocate who is on call for a particular GRB will modify the table the morning after observations have been taken;
after this point, the table elements will reflect the actual observations and not the planned ones.
</br>
<br>
The current H.E.S.S. GRB observation policy is to observe all well-localized GRBs that can be observed within 24 hours of the GRB trigger time,
for the entirety of the observable window on the first night.
H.E.S.S. also observes a subset of GRBs with larger localization uncertainties using a tiled observing pattern.
We observe around 20-25 GRBs per year, of which roughly three quarters are observed with pointed observations and a quarter with tiled observations.
In general, a small fraction of GRBs that pass our observing criteria are never observed due to burst advocate decision.
Possible reasons are: The delay time is long and the observable window is short; the GRB notice was later retracted; the GRB was determined to be at a large redshift.
</br>
<br>
For questions or comments, including requests for more information on a particular GRB, please email <a href="mailto:[email protected]">[email protected]</a>.
</br>
<br>
For general information about H.E.S.S. see <a href="https://www.mpi-hd.mpg.de/hfm/HESS/">https://www.mpi-hd.mpg.de/hfm/HESS/</a>.
</br>
</p>
<br><font size="+1">Explanations of columns</font></br>
<ul>
<li><b>GRB ID</b>: GRB identifier from the triggering instrument (derived from automated notices) and/or the full alphanumeric name where applicable (manually entered)</li>
<li><b>Triggering instrument</b>: The GRB detector whose notification triggered H.E.S.S.; this is usually the detector with the best available localization at the time of the H.E.S.S. observations</li>
<li><b>Alert time (T0)</b>: Trigger time of the GRB, for the triggering instrument, in UTC</li>
<li><b>GRB RA (J2000), GRB Dec (J2000)</b>: Localization of the GRB by the triggering instrument, right ascension and declination, in both degrees and hms/dms. For <b>tiled observations</b>, this is the position of the <i>first</i> tile that H.E.S.S. observed or plans on observing.</li>
<li><b>H.E.S.S. window start, H.E.S.S. window end</b>: Either: The start and end of the time period when the GRB is visible to H.E.S.S. (usually below 60° zenith angle, sometimes below 45°) OR the start and end of the time period during which H.E.S.S. observed the GRB</li>
<li><b>Obs mode</b>: H.E.S.S. observation mode, either Pointed (for all well-localized GRBs) or Tiled (for GRBs with larger localization regions)</li>
<li><b>Reaction</b>: H.E.S.S. array reaction mode, either Automatic (for GRBs with very short observation delays) or Manual</li>
<li><b>Contact</b>: The name of the H.E.S.S. burst advocate for this GRB</li>
<ul>
</p>
</div>
</body>
</html>