TABLE OF CONTENTS:
The GCN system has been modified to incorporate the distribution of candidate coincidence events
produced within a single instrument and/or between multiple instruments within the AMON project.
The HESE notices (High Energy Starting Event) and the EHE notices (Extremely High Energy)
from the IceCube instrument were replaced by the ICECUBE_ASTROTRACK_GOLD and _BRONZE notice types.
For the HESE notice type; the occurrence rate will be about 3.5/yr. DISCONTINUED, REPLACED BY GOLD/BRONZE
For the EHE notice type; the occurrence rate will be about 4-6/yr. DISCONTINUED, REPLACED BY GOLD/BRONZE
For the HAWC_BURST_MONITOR notice type; the occurence rate will be about 1/yr; >??% are astrophysical.
For the ICECUBE_ASTROTRACK GOLD notice type; the occurence rate will be about 12/yr; >50% are astrophysical.
For the ICECUBE_ASTROTRACK BRONZE notice type; the occurence rate will be about 16/yr; >30% are astrophysical.
For the NU_EM_COINC notice type; the occurance rate will be 2-4/yr for HAWC-IceCube and 2-4/yr for Fermi-ANTARES.
For the AMON_ICECUBE_CASCADE notice type; the occurance rate will be 8/yr; and >85% are astrophysical.
Like all the other sources of GRB/transient information within the GCN system,
users can elect to receive (or not) each of these AMON Notice types.
The AMON notices are archived at:
Table of AMON_ICECUBE_HESE Events,
Table of AMON_ICECUBE_EHE Events.
Table of ICECUBE_ASTROTRACK_GOLD-n-BRONZE ,
Table of HAWC_BURST_MONITOR Events,
Table of AMON_NU_EM_COINC Events,
Table of AMON_ICECUBE_CASCADE Events.
2. Notice Types, Content, and Purpose
There are 7 GCN/AMON Notice types. (Of these, only the GOLD, BRONZE, HAWC, NU_EM_COINC, and CASCADE) are currently available; HESE & ESE are discontinued.)
They are:
1) AMON_ICECUBE_HESE Notice: a single high-energy IceCube neutrino. DISCONTINUED, REPLACED BY ICECUBE_ASTROTRACK_GOLD and _BRONZE
2) AMON_ICECUBE_EHE Notice: an extremely high-energy IceCube neutrino. DISCONTINUED, REPLACED BY ICECUBE_ASTROTRACK_GOLD and _BRONZE
3) ICECUBE_ASTROTRACK_GOLD Notice: a single high-energy IceCube track neutrino event.
4) ICECUBE_ASTROTRACK_BRONZE Notice: a single high-energy IceCube track neutrino event.
5) HAWC_BURST_MONITOR Notice: HAWC alerts from short time-scale searches looking for GRBs.
6) AMON_NU_EM_COINC Notice: a coincidence between an X-/gammaray instrument and a neutrino instrument (IceCube or ANTARES).
7) AMON_ICECUBE_CASCADE Notice: a low-latency single high energy IceCube cascade neutrino event direction.
3. Positions, Error and Time_delays
The AMON automated pipeline will ingest the data from all their contributing
missions and instruments, scan these trigger streams for correlations
between instruments and within instruments, and produce spatial and/or
temporal coincidences within a few sec after receiving the data from the respective detectors (IceCube, Antares, Auger).
For the two IceCube notice types, it takes 20-180 sec for the IceCube processing
to determine if there is an event.
The localization precisions and time_delays of the various AMON Notice types
are as follows:
POS_ERROR TIME SINCE
TYPE [radius] TRIGGER COMMENTS
========================= =========== ========== ==================================================
AMON_ICECUBE_HESE 2-9deg 0.5-3 min Direction of a single hi-energy neutrino DISCONTINUED, REPLACED BY GOLD/BRONZE
AMON_ICECUBE_EHE 0.2-0.8deg 0.5-3 min Direction of a single extremely hi-energy neutrino DISCONTINUED, REPLACED BY GOLD/BRONZE
HAWC_BURST_MONITOR 0.4-0.8deg 0.5-1 min HAWC alert of GRB-like events
ICECUBE_ASTROTRACK_GOLD 0.2-0.75deg 0.5-1 min Hi-energy single neutrino directions
ICECUBE_ASTROTRACK_BRONZE 0.2-0.75deg 0.5-1 min Hi-energy single neutrino directions
AMON_NU_EM_COINC 0.2-1deg LT 7 hr Coincidence between neutrino instruments and EM Instruments.
AMON_ICECUBE_CASCADE 2-20deg 0.5-1 min Direction of a single hi-energy neutrino
========================= =========== ========== ==================================================
ERROR CIRCLES:
HESE: (Replaced by ICECUBE_ASTROTRACK_GOLD/_BRONZE)
The uncertainty in the location will depend on:
(a) the energy of the neutrino, and
(b) the track-vs-cascade nature of the energy deposited in IceCube.
The typical error is (for signal_trackness > 0.1):
2 to 8.9 [deg], radius, statistical plus systematic, 90% containment.
0.4 to 1.6 [deg], radius, statistical plus systematic, 50% containment.
EHE: (Replaced by ICECUBE_ASTROTRACK_GOLD/_BRONZE)
The uncertainty in the location is nearly flat across neutrino energies
for this stream of through-going neutrino tracks. This uncertainty represents
a quality of the online position reconstruction, and it is computed in real time for each alert.
The typical error is (for signal_trackness > 0.1):
0.1 to 0.4 [deg], radius, statistical plus systematic, 50% containment.
Only 50% containment error circle will be provided in real-time for this stream.
ICECUBE ASTROTRACK GOLD and BRONZE:
The uncertainty in the location will depend on:
(a) the energy of the neutrino, and
(b) the track-vs-cascade nature of the energy deposited in IceCube.
The typical error is:
0.2 to 0.75 [deg], radius, statistical only, does not include systematic, 50% containment.
HAWC_BURST_MONITOR:
The uncertainty in the location will depend on backgrond events during the search.
0.4 to 0.8 [deg], radius, statistical only, does not include systematic, 68% containment.
NU_EM_COINC:
The uncertainty in the location will depend on the other participating instruments.
AMON_ICECUBE_CASCADE:
The typical error is:
3 - 30 occasionally up to 90 [deg], radius, statistical plus systematic, 90% containment.
2 - 20 occasionally up to 90 [deg], radius, statistical plus systematic, 50% containment.
The rates from the various notice types are:
TYPE RATE COMMENTS ==================== ========= ================================================== AMON_ICECUBE_HESE 0.4/month Direction of a single hi-energy neutrino DISCONTINUED, REPLACED BY ICECUBE_ASTROTRACK_GOLD AMON_ICECUBE_EHE 0.5/month Direction of a single extremely hi-energy neutrino DISCONTINUED, REPLACED BY ICECUBE_ASTROTRACK_BRONZE AMON_ICECUBE_COINC 1/month Temporal/spatial coinc between IceCube neutrinos NOT YET PUBLIC HAWC_BURST_MONITOR 1/year HAWC alert of GRB-like events ICECUBE_ASTROTRACK_GOLD 1/month Hi-energy single neutrino directions ICECUBE_ASTROTRACK_BRONZE 1.3/month Hi-energy single neutrino directions AMON_NU_EM_COINC 4-8/yr Combined IC+HAWC and ANTARES+Fermi AMON_ICECUBE_CASCADE 8/yr Hi-energy single neutrino cascade event direction ==================== ========= ==================================================
The sequence of activities for a typical event follows:
ICECUBE_ASTROTRACK_GOLD & ICECUBE_ASTROTRACK_BRONZE
(now active and replacing ICECUBE_HESE, ICECUBE_EHE; & ICECUBE_COINC obsolete):
1) The real-time IceCube processing pipeline determines they have:
a) For the High Energy Starting Event (HESE) stream: an
up/downward going track-like neutrino, which passes HESE filter and
has charge > 6000 p.e. (see the AMON-IceCube HESE public document for more
information here).
b) For the Extremely High Energy (EHE) stream: an up/downward through-going track-like neutrino,
which passes EHE filter that is optimized for astrophysical neutrinos with energies exceeding several hundreds TeV
(see the AMON-IceCube EHE public document for more information here here).
c) For the private IceCube coincidence stream: two or more
high-quality muon neutrinos within 100 sec time window and within 3.5 deg
angular separation. An additional test statistic cut is placed in order
not to exceed a given number of alerts per each of the follow-up telescopes
that signed IceCube MoU.
2) They send a message to AMON processing pipeline:
Each IceCube alert gets written to the AMON database and a VOEvent
is created and sent to GCN. The alert will be also used in the
standard AMON coincidence analysis with event streams from other observatories
At the moment (September 2016), AMON is receiving only IceCube streams in real-time,
however the real-time coincidence analysis is running in case AMON
starts receiving events from any other stream (e.g., HAWC, Pierre Auger, ANTARES).
The standard coincidence analysis looks for coincidences between events
from subthreshold data streams within a time window of 100 seconds and
an angular separation of 3 sigma. In case that a HESE/EHE event is found in councidence
with an event from another stream, the AMON alert would be created and
distributed via GCN inside the AMON network (i.e. private GCN stream).
The recipients of these coincidences will be follow-up observatories
that signed MoU with AMON and AMON networks triggering observatories
whose event streams are used in this coincidence analysis.
3) AMON sends a message to GCN.
4) GCN converts the message into all the standard GCN Notice formats, and
distributes it to those sites enabled for that notice type and that meets the site's filtering functions.
If the initial identification of an event is no longer true (not astrophysical),
then a retraction notice is issued.
It will be a re-issue of the original notice, this time with the Retraction flag set.
EMAIL-BASED: Samples of the E-mail, Cell/Pager, Short-form Cell/Pager, & Subject-only
distribution methods of the GCN/AMON Notice types are included below.
The format is very similar to the other spacecraft-instrument sources
of GRB/Transient locations -- the GCN-standard "TOKEN: value" format.
SOCKET-BASED: The 160-byte binary socket packet contents and format
are similar to the other mission-specific packet types
and are described in detail in the socket packet definition document.
This document also has explanations of the various fields in the packet
(their content, values, and implications for use).
and those same fields are appear in the email-based formats.
(Therefore, it is useful for email/cell/pager recipients to read the
socket packet definition document
to understand the contents of the email/cell/pager/VOEvent notifications are.)
NUM TYPE VOEVENT SOCKET EMAIL PAGER/CELL XML
(full format) (all 4 variants)
=== ======================= ======= ====== ============= ================ ====
157 ICECUBE_COINC Y P B B B
158 ICECUBE_HESE Y P B B B DISCONTINUED, REPLACED BY ICECUBE_ASTROTRACK_GOLD
169 ICECUBE_EHE Y P B B B DISCONTINUED, REPLACED BY ICECUBE_ASTROTRACK_BRONZE
171 HAWC_BURST_MONITOR Y P B B B
173 ICECUBE_ASTROTRACK_GOLD Y P B B B
174 ICECUBE_ASTROTRACK_BRONZE Y P B B B
172 AMON_NU_EM_COINC Y P B B B
176 AMON_ICECUBE_CASCADE Y P B B B
where:
Y = Also available in XML VOEvent format for XML_Sockets and VOEvent server sockets.
P = Packet (the GCN-standard 40 longword socket packet format).
B = Body of email (the GCN-standard "TOKEN: value" format)
U = URL (the URL is contained in the packet and the body of the email)
A = Attachment (the actual data product is optionally attached to the email)
Sites can elect to receive each of the AMON Notice types on a Notice-by-Notice basis.
There is a separate dis/enable bit for each type.
And for the HESE notices only the Error and Delay filters are active.
And for the ICECUBE_ASTROTRACK_GOLD and _BRONZE notices only the Error and Delay filters are active.
And for the HAWC_BURST_MONITOR notices only the Error and Delay filters are active.
And for the AMON_NU_EM_COINC notices only the Delay filter is active.
And for the ICECUBE_CASCADE notices only the Error and Delay filters are active.
See filtering to see which filter functions are applicable.
These filters apply to all the existing distribution methods/media.
There is only one "TEST" type notice for the varous types withing the AMON collections of notices.
As such, its abiltiy to allow sites to "practice" on AMON Notices is somewhat limited.
The AMON_TEST Notice duplicates the AMON_ICECUBE_HESE Notice (all socket packet, email, and cell/page formats).
(Even though the HESE type is no longer available, the TEST notice still keeps the HESE format/content
to reduce the changes recipients wold have to make in the processing at their end.)
Sites can elect to receive this Test Notice.
These Test Notices are issued every ~3.8 hours.
The RA,Dec positions rotate through a grid on the Northern & Southern celestial skies.
The IceCube detector has 4pi coverage of the sky and almost 100% up-time,
which means that its alerts can be used to trigger telescopes around the globe
in real-time. In particular, ICECUBE_ASTROTRACK_GOLD and _BRONZE streams have all-sky coverage.
The HAWC instrument has an instantaneous FoV of 2 sr. During the course of a 24 hour day, it covers 2/3 of the entire 4pi sky.
Fermi-LAT's FoV is >2sr. It can cover the whole sky is 2-3 orbits. Each orbit lasts around 90 minutes.
Sites are encouraged to acknowledge IceCube and AMON in their publications
based on follow-up observations using these GCN/ICECUBE_ASTROTRACK_GOLD, GCN/ICECUBE_ASTROTRACK_BRONZE,
GCN/HAWC_BURST_MONITOR, GCN/AMON_NU_EM_COINC, and GCN/AMON_ICECUBE_CASCADE locations.
For further information on this, please contact
Scott Barthelmy (for GCN issues),
or see the:
ICECUBE_HESE document, and
ICECUBE_EHE document, and
ICECUBE_ASTROTRACK Gold and Bronze document, and
HAWC_BURST_MONITOR document, and
AMON_NU_EM_COINC document, and
ICECUBE_CASCADE document (High_Energy_Neutrino_Cascade_Alerts.pdf), and
these GCN web pages, and
All past notices are archived at:
AMON_ICECUBE_HESE Triggers table,
AMON_ICECUBE_EHE Triggers table,
ICECUBE_ASTROTRACK_GOLD-n-BRONZE Triggers table,
HAWC_BURST_MONITOR Triggers table,
AMON_NU_EM_COINC Triggers table,
ICECUBE_CASCADE Triggers table.
Full Format Email:
Examples of the Notice types of the e-mail formats are shown below.
The "/////" divider bars are NOT part of the messages.
Do not take the actual values shown in these examples as real neutrino events
While based on ground-test data from the mission,
they have been adjusted to provide a broader representation
of the various combinations of fields and value ranges.
For those sites/people that use demons and/or incoming e-mail filters (e.g. procmail),
the "Subject" lines for the all notice types are constant.
The subject-line strings are (respectively):
The 'raw' versions:
GCN/AMON_ICECUBE_HESE [obsolete notice type]
GCN/AMON_ICECUBE_EHE [obsolete notice type]
GCN/AMON_ICECUBE_COINC
GCN/HAWC_BURST_MONITOR
GCN/ICECUBE_ASTROTRACK_GOLD
GCN/ICECUBE_ASTROTRACK_BRONZE
GCN/AMON_NU_EM_COINC
GCN/AMON_ICECUBE_CASCADE
//////////////////////// HESE e-mail format ////////////////////////////////
TITLE: GCN/AMON NOTICE
NOTICE_DATE: Tue 05 Apr 16 01:52:25 UT
NOTICE_TYPE: AMON ICECUBE HESE
RUN_NUM: 127770
EVENT_NUM: 8694362
SRC_RA: 236.1036d {+15h 44m 25s} (J2000),
236.3122d {+15h 45m 15s} (current),
235.4627d {+15h 41m 51s} (1950)
SRC_DEC: -0.1705d {-00d 10' 13"} (J2000),
-0.2208d {-00d 13' 14"} (current),
-0.0139d {-00d 00' 49"} (1950)
SRC_ERROR: 300.00 [arcmin radius, stat+sys, 90% containment]
SRC_ERROR50: 60.00 [arcmin radius, stat+sys, 50% containment]
DISCOVERY_DATE: 17483 TJD; 96 DOY; 16/04/05 (yy/mm/dd)
DISCOVERY_TIME: 6686 SOD {01:51:26.00} UT
REVISION: 0
N_EVENTS: 1 [number of neutrinos]
STREAM: 1
DELTA_T: 0.0000 [sec]
SIGMA_T: 0.0000 [sec]
FALSE_POS: 1.2303e-09 [s^-1 sr^-1]
PVALUE: 2.3405e-09 [dn]
CHARGE: 1510.00 [pe]
SIGNAL_TRACKNESS: 0.01 [dn]
SUN_POSTN: 14.48d {+00h 57m 55s} +6.19d {+06d 11' 08"}
SUN_DIST: 137.83 [deg] Sun_angle= 9.2 [hr] (West of Sun)
MOON_POSTN: 343.39d {+22h 53m 33s} -6.25d {-06d 14' 59"}
MOON_DIST: 106.95 [deg]
GAL_COORDS: 6.89, 40.31 [deg] galactic lon,lat of the event
ECL_COORDS: 233.83, 19.11 [deg] ecliptic lon,lat of the event
COMMENTS: AMON_ICECUBE_HESE.
//////////////////////// EHE e-mail format ////////////////////////////////////////
TITLE: GCN/AMON NOTICE
NOTICE_DATE: Sun 01 Jul 16 19:56:28 UT
NOTICE_TYPE: AMON ICECUBE EHE
RUN_NUM: 128223
EVENT_NUM: 26476564
SRC_RA: 128.4989d {+08h 34m 00s} (J2000),
128.6472d {+08h 34m 35s} (current),
128.0502d {+08h 32m 12s} (1950)
SRC_DEC: -41.3631d {-41d 21' 46"} (J2000),
-41.4205d {-41d 25' 13"} (current),
-41.1906d {-41d 11' 25"} (1950)
SRC_ERROR: 32.98 [arcmin radius, stat+sys, 50% containment]
DISCOVERY_DATE: 17579 TJD; 192 DOY; 16/07/01 (yy/mm/dd)
DISCOVERY_TIME: 71753 SOD {19:55:53.00} UT
REVISION: 0
N_EVENTS: 1 [number of neutrinos]
STREAM: 2
DELTA_T: 0.0000 [sec]
SIGMA_T: 0.0000 [sec]
ENERGY: 931.331 [TeV]
SIGNALNESS: 2.4519e-04 [dn]
CHARGE: 5144.23 [pe]
SUN_POSTN: 110.54d {+07h 22m 10s} +22.09d {+22d 05' 38"}
SUN_DIST: 65.70 [deg] Sun_angle= -1.2 [hr] (East of Sun)
MOON_POSTN: 186.11d {+12h 24m 27s} -0.56d {-00d 33' 45"}
MOON_DIST: 65.81 [deg]
GAL_COORDS: 260.35, -0.70 [deg] galactic lon,lat of the event
ECL_COORDS: 149.42,-57.13 [deg] ecliptic lon,lat of the event
COMMENTS: AMON_ICECUBE_EHE.
//////////////////////// GOLD e-mail format ///////////////////////////////////////
TITLE: GCN/AMON NOTICE
NOTICE_DATE: Wed 12 Jun 19 09:23:49 UT
NOTICE_TYPE: ICECUBE Astrotrack Gold
STREAM: 24
RUN_NUM: 132679
EVENT_NUM: 57134236
SRC_RA: 5.9805d {+00h 23m 55s} (J2000),
6.2156d {+00h 24m 52s} (current),
5.3739d {+00h 21m 30s} (1950)
SRC_DEC: -50.7665d {-50d 45' 58"} (J2000),
-50.6589d {-50d 39' 31"} (current),
-51.0435d {-51d 02' 36"} (1950)
SRC_ERROR: 30.80 [arcmin radius, stat-only, 90% containment]
SRC_ERROR50: 12.00 [arcmin radius, stat-only, 50% containment]
DISCOVERY_DATE: 18646 TJD; 163 DOY; 19/06/12 (yy/mm/dd)
DISCOVERY_TIME: 33802 SOD {09:23:22.38} UT
REVISION: 0
ENERGY: 1.3782e+03 [TeV]
SIGNALNESS: 1.6858e-03 [dn]
FAR: 87.9023 [yr^-1]
SUN_POSTN: 80.37d {+05h 21m 29s} +23.14d {+23d 08' 27"}
SUN_DIST: 98.32 [deg] Sun_angle= 4.9 [hr] (West of Sun)
MOON_POSTN: 199.70d {+13h 18m 48s} -2.66d {-02d 39' 33"}
MOON_DIST: 125.44 [deg]
GAL_COORDS: 313.58,-65.79 [deg] galactic lon,lat of the event
ECL_COORDS: 338.51,-47.47 [deg] ecliptic lon,lat of the event
COMMENTS: IceCube Gold event.
COMMENTS: The position error is statistical only, there is no systematic added.
//////////////////////// BRONZE e-mail format /////////////////////////////////////
TITLE: GCN/AMON NOTICE
NOTICE_DATE: Wed 12 Jun 19 11:52:28 UT
NOTICE_TYPE: ICECUBE Astrotrack Bronze
STREAM: 25
RUN_NUM: 132680
EVENT_NUM: 5503854
SRC_RA: 191.9816d {+12h 47m 56s} (J2000),
192.2678d {+12h 49m 04s} (current),
191.2503d {+12h 45m 00s} (1950)
SRC_DEC: -58.4503d {-58d 27' 00"} (J2000),
-58.5561d {-58d 33' 21"} (current),
-58.1776d {-58d 10' 38"} (1950)
SRC_ERROR: 144.26 [arcmin radius, stat-only, 90% containment]
SRC_ERROR50: 56.20 [arcmin radius, stat-only, 50% containment]
DISCOVERY_DATE: 18646 TJD; 163 DOY; 19/06/12 (yy/mm/dd)
DISCOVERY_TIME: 42720 SOD {11:52:00.77} UT
REVISION: 0
ENERGY: 5.7174e+03 [TeV]
SIGNALNESS: 1.1877e-03 [dn]
FAR: 140.5724 [yr^-1]
SUN_POSTN: 80.48d {+05h 21m 54s} +23.15d {+23d 08' 50"}
SUN_DIST: 120.89 [deg] Sun_angle= -7.5 [hr] (East of Sun)
MOON_POSTN: 201.03d {+13h 24m 06s} -3.20d {-03d 11' 57"}
MOON_DIST: 55.78 [deg]
GAL_COORDS: 302.47, 4.42 [deg] galactic lon,lat of the event
ECL_COORDS: 220.60,-47.62 [deg] ecliptic lon,lat of the event
COMMENTS: IceCube Bronze event.
COMMENTS: The position error is statistical only, there is no systematic added.
//////////////////////// COINC e-mail format //////////////////////////////////////
TITLE: GCN/AMON NOTICE
NOTICE_DATE: Thu 22 May 20 20:24:59 UT
NOTICE_TYPE: AMON Neutrino-EM Coincidence
AMON_STREAM: 1
EVENT_DATE: 200522A
EVENT_NUM: 48580
REVISION: 0
RUN_NUM: 0
SRC_RA: 23.0100d {+01h 32m 02s} (J2000),
23.2633d {+01h 33m 03s} (current),
22.3889d {+01h 29m 33s} (1950)
SRC_DEC: -10.1300d {-10d 07' 47"} (J2000),
-10.0256d {-10d 01' 31"} (current),
-10.3868d {-10d 23' 12"} (1950)
SRC_ERROR: 35.93 [arcmin radius, stat-only, 90% containment]
SRC_ERROR50: 19.80 [arcmin radius, stat-only, 50% containment]
DISCOVERY_DATE: 18991 TJD; 143 DOY; 20/05/22 (yy/mm/dd)
DISCOVERY_TIME: 66098 SOD {18:21:38.00} UT
COINC_PAIR: 1 IC-HAWC [index and actual string]
DELTA_T: 17056.25 [sec]
FAR: 3.2255e+04 [yr^-1]
TRIG_ID18: 0x40
MISC19: 0xAC000000
SUN_POSTN: 66.19d {+04h 24m 45s} +21.63d {+21d 37' 55"}
SUN_DIST: 52.69 [deg] Sun_angle= 2.9 [hr] (West of Sun)
MOON_POSTN: 145.05d {+09h 40m 12s} +18.40d {+18d 23' 48"}
MOON_DIST: 123.17 [deg]
GAL_COORDS: 154.23,-70.49 [deg] galactic lon,lat of the event
ECL_COORDS: 17.35,-18.33 [deg] ecliptic lon,lat of the event
COMMENTS: AMON NEUTRINO-EM Coincidence.
//////////////////////// HAWC_BURST_MONITOR e-mail format /////////////////////////
TITLE: GCN/AMON NOTICE
NOTICE_DATE: Mon 01 Jun 19 11:13:47 UT
NOTICE_TYPE: HAWC BURST MONITOR
STREAM: 3
RUN_NUM: 0
EVENT_NUM: 99999
SRC_RA: 123.4568d {+08h 13m 50s} (J2000),
123.5801d {+08h 14m 19s} (current),
123.1394d {+08h 12m 33s} (1950)
SRC_DEC: -54.3208d {-54d 19' 14"} (J2000),
-54.3806d {-54d 22' 49"} (current),
-54.1680d {-54d 10' 04"} (1950)
SRC_ERROR: 33.00 [arcmin radius, stat+sys, 90% containment]
REVISION: 4
FAR: 8.2482 [yr^-1]
Pvalue: 0.9100 [0.0 - 1.0]
delta_T: 500.00 [sec]
SUN_POSTN: 77.94d {+05h 11m 47s} +22.97d {+22d 58' 24"}
SUN_DIST: 86.70 [deg] Sun_angle= -3.0 [hr] (East of Sun)
MOON_POSTN: 169.15d {+11h 16m 36s} +9.50d {+09d 29' 59"}
MOON_DIST: 74.46 [deg]
GAL_COORDS: 269.16,-10.82 [deg] galactic lon,lat of the event
ECL_COORDS: 159.01,-69.86 [deg] ecliptic lon,lat of the event
COMMENTS: HAWC burst monitor event.
//////////////////////// AMON_NU_EM_COINC e-mail format /////////////////////////
TITLE: GCN/AMON NOTICE
NOTICE_DATE: Fri 17 Jul 20 21:55:50 UT
NOTICE_TYPE: AMON Neutrino-EM Coincidence
AMON_STREAM: 1
EVENT_DATE: 200717A
EVENT_NUM: 54519
REVISION: 0
RUN_NUM: 0
SRC_RA: 118.5000d {+07h 54m 00s} (J2000),
118.7603d {+07h 55m 02s} (current),
117.8661d {+07h 51m 28s} (1950)
SRC_DEC: -1.6200d {-01d 37' 11"} (J2000),
-1.6748d {-01d 40' 28"} (current),
-1.4885d {-01d 29' 18"} (1950)
SRC_ERROR: 22.76 [arcmin radius, stat-only, 90% containment]
SRC_ERROR50: 12.59 [arcmin radius, stat-only, 50% containment]
DISCOVERY_DATE: 19047 TJD; 199 DOY; 20/07/17 (yy/mm/dd)
DISCOVERY_TIME: 76946 SOD {21:22:26.00} UT
COINC_PAIR: 1 IC-HAWC [index and actual string]
DELTA_T: 19395.52 [sec]
FAR: 1.8197e+00 [yr^-1]
TRIG_ID18: 0x40
MISC19: 0xAC000000
SUN_POSTN: 117.74d {+07h 50m 58s} +20.99d {+20d 59' 22"}
SUN_DIST: 22.69 [deg] Sun_angle= -0.1 [hr] (East of Sun)
MOON_POSTN: 80.41d {+05h 21m 38s} +22.36d {+22d 21' 35"}
MOON_DIST: 44.45 [deg]
GAL_COORDS: 221.68, 13.12 [deg] galactic lon,lat of the event
ECL_COORDS: 120.97,-22.05 [deg] ecliptic lon,lat of the event
COMMENTS: AMON NEUTRINO-EM Coincidence.
//////////////////////// AMON_ICECUBE_CASCADE e-mail format /////////////////////////
TITLE: GCN/AMON NOTICE
NOTICE_DATE: Fri 31 Jul 20 17:12:52 UT
NOTICE_TYPE: ICECUBE Cascade
EVENT_NAME: IceCubeCascade-200701b
STREAM: 26
RUN_NUM: 134244
EVENT_NUM: 34406854
SRC_RA: 220.0434d {+14h 40m 10s} (J2000),
220.2371d {+14h 40m 57s} (current),
219.5707d {+14h 38m 17s} (1950)
SRC_DEC: +43.1731d {+43d 10' 23"} (J2000),
+43.0859d {+43d 05' 09"} (current),
+43.3870d {+43d 23' 13"} (1950)
SRC_ERROR: 44.06 [deg radius, stat+systematic, 90% containment]
SRC_ERROR50: 24.17 [deg radius, stat+systematic, 50% containment]
DISCOVERY_DATE: 19031 TJD; 183 DOY; 20/07/01 (yy/mm/dd)
DISCOVERY_TIME: 69893 SOD {19:24:53.44} UT
REVISION: 0
ENERGY: 10.99 [TeV]
SIGNALNESS: 8.7016e-01 [dn]
FAR: 0.4021 [yr^-1]
SUN_POSTN: 131.38d {+08h 45m 31s} +18.02d {+18d 01' 06"}
SUN_DIST: 76.99 [deg] Sun_angle= -5.9 [hr] (East of Sun)
MOON_POSTN: 273.18d {+18h 12m 43s} -23.86d {-23d 51' 49"}
MOON_DIST: 82.75 [deg]
GAL_COORDS: 76.15, 62.79 [deg] galactic lon,lat of the event
ECL_COORDS: 195.83, 54.53 [deg] ecliptic lon,lat of the event
SKYMAP_FITS_URL: https://roc.icecube.wisc.edu/public/hese_cascades/hese_59031_run00134244.evt000034406854.fits
SKYMAP_PNG_URL: https://roc.icecube.wisc.edu/public/hese_cascades/hese_59031_run00134244.evt000034406854.png
COMMENTS: IceCube Cascade event.
COMMENTS: The position error is the combined statistical and the systematic.
Examples of the (regular) cell/pager formats are shown below.
There are no "Subject" lines for these e-mails sent to the cell/pager companies
because the Subject line would use up valuable character counts
from the maximum displayable for the body of the message.
RA,Dec values are in Current epoch.
///////////////////////// Cell/Pager format /////////////////////////////////////// GCN/AMON ICECUBE HESE Event RA=236.3122d DEC=-0.2208d ERR=300.0arcmin T=01:51:26.00 UT TRIGGER_NUM=8694362 FALSE_POS=1.2303e-09 [s^-1 sr^-1] PVALUE=2.3405e-09 [dn] N_EVENTS=1 [num neutrinos] /////////////////////////////////////////////////////////////////////////////////// [i need to fill in the EHE example!!!] /////////////////////////////////////////////////////////////////////////////////// [i need to fill in the GOLD example!!!] /////////////////////////////////////////////////////////////////////////////////// [i need to fill in the BRONZE example!!!] /////////////////////////////////////////////////////////////////////////////////// [i need to fill in the HAWC_BURST_MONITOR example!!!] /////////////////////////////////////////////////////////////////////////////////// [i need to fill in the ICECUBE_NU_EM example!!!] /////////////////////////////////////////////////////////////////////////////////// GCN/TEST ICECUBE CASCADE EVENT RA=123.587d DEC=-54.384d ERR=33.0arcmin,90% stat+sys T=17:01:40.12 UT TRIGGER_NUM=99999 FAR=2.3448 [yr^-1] SIGNALNESS=1.2348e-02 [dn] ENERGY= 6.7795e+01 [TeV] ///////////////////////////////////////////////////////////////////////////////////
Examples of the short-form pager format are shown below.
There are no "Subject" lines for these e-mails sent to the pager companies,
because the Subject-line would use up valuable character counts
from the maximum displayable for the body of the message.
And it was the very limited display character count of some companies
that motivated the short-form pager method in the first place.
RA,Dec are in B1950 epoch.
///////////////////////// Short-Cell/Pager format ///////////////////////////////// [i need to fill in the examples!!!] ///////////////////////////////////////////////////////////////////////////////////
There are two variations of the Subject-only format: decimal degrees (Current epoch)
and RA=hh:mm:ss Dec=DDdMMmSSs format (J2000 epoch). The two variations are shown below:
///////////////////////// Subject-only format ///////////////////////////////////// [i need to fill in the other examples!!!] ///////////////////////////////////////////////////////////////////////////////////
///////////////////////// VOEvent XML format //////////////////////////////////////ICECUBE_EHE:
///////////////////////////////////////////////////////////////////////////////NU_EM_COINC:
///////////////////////////////////////////////////////////////////////////////AMON_ICECUBE_CASCADE:
16. Socket-based Packing Documentations, Includes Parameter Definitions
For socket-based, email-based, and voevent-based notice formats:
Many of the parameters discussed below mention scaling factors and integerization.
These have to do with the 160-byte binary socket packet format that is also used
as the base format for all internal activities within GCN processing (in addition
to the public distribution format). These scalings and integerizations
indicate the max possible dynamic range and qunatization of each parameter.
The parameter definitions listed below were taken from the
socket packet definition document,
and this document is the formal keeper of the definitions, so if things
are not making sense from the definitions below, then please refer to
socket packet definition document
for the current official definitions (and send me an email pointing out a difference
between here and the socket packet definition document).
A) HESE Field Descriptions:
The "event_num" is a uniquely identifying number for each event/trigger.
(See also 'run_num' below.)
The "trig_tjd" is the Truncated Julian Day of the AMON event,
eg. TJD=14466 is 01 Jan 2008.
The "trig_sod" is the UT seconds-of-day (SOD) of the AMON event.
The units are in centi-seconds (ie the fl.pt. seconds were multiplied by 100
and then integerized). The trigger time can be off by TBD msec.
The "ra" and "dec" fields specify the RA,Dec location of the multiply detected
event (in J2000 epoch). These intrinsically floating point quantities
have been multiplied by 10,000 and then integerized to make
an integer quantity with units of 10^-4-degrees.
The "n_events" field contains the number of events (ie neutrinos)
that occurred during the deltaT window. For ICECUBE_HESE type,
this number will always be 1 (ie one PeV neutrino). (Alway one, but this field
is still included in the HESE type to be symetric with the EHE and COINC types.)
The "false_pos" (flase positive rate) field specifies how often a trigger of this intensity
would happen from just noise fluctuations (an identically 0 value means it was not calculated).
The units are number per steradian per second.
The range of valuesi 0.0 to 1.0.
The quantity stored in slot 10 is the log10() of the False_pos value from AMON
multiplied by 10,000 and then intergerized. To retrieve the False_pos value at the
receiving end, call false_pos=pow(10.0,slot[10]/10000.0).
The "event_error90" is the radius of the circle that will contain on average
90% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized).
It contains the statistical error and the systematic error(TBD).
The "deltaT" field contains the Time window of the burst.
The units are centi-sec (ie the deltaT was multiplied by 100 and
then integerized).
This will always be identically 0 for HESE notice type.
The "sigmaT" field contains the Uncertainty of the time window.
The units are centi-sec (ie the sigmaT was multiplied by 100 and
then integerized).
This will always be identically 0 for HESE notice type.
The "stream" field contains the index number identifying
which analysis stream produced this trigger. It ranges from 1 - NN.
The list of streams are: 0=undefined, 1=ICECUBE_HESE, 2=abc, 3=def, ...
The "rev" field contains the number of times this notice was revised (ie updated).
rev=0 means the first notice, 1 is the 1st revision, 2 is 2nd revision, etc.
For AMON_ICECUBE_HESE type notices, the changes are most likely due to the RA,Dec,Error
values changing.
The "trig_id" field contains (a) flag bits on the type of solution
that was found by the AMON processing and
(b) flag bits that are assigned in the GCN ground-processing.
The bit packing of the "trig_id" entry in the packet is:
BitNum F-v-G Item_name Description
------ ---- --------- -----------
0 - spare spare for future use
1 G role=test Received with role="test"
2-4 - spare spare for future use
5 G retraction 0=No or 1=Yes, it is definitely not real, a Retraction
6-27 - spare spare for future use
28 G spatial_coinc 0=No or 1=Yes, there was a spatial coincidence with another event
29 G temporal_coinc 0=No or 1=Yes, there was a temporal coincidence with another event
30-31 - spare spare for future use
The columns are: "BitNum" is the 2^N location within the 4-byte word;
"Item_name" is the short-description name of the quantity; and
"Description" is the longer description of the quantity.
The "misc" field contains various bit_flags.
The bit packing is:
Bit_Number Item_name Description
---------- --------- -----------
0-7 spare Spare bits within 'misc'.
8-9 cite_type Citation type (0=undef,1=followup,2=supersedes,3=retraction)
10-23 spare Spare bits within 'misc'.
24-31 sernum 8 bits containing the type of the HESE serial number(tbd)
P-value is a chance probability of alert being an atmospheric neutrino.
Low p-value (p < 0.0027 (3 sigma) indicates a given alert is less likely to be background.
The range is from 0 to 1 (an identically 0 value means it was not calculated).
The quantity stored in slot 20 is the log10() of the Prob_value value from AMON
multiplied by 10,000 and then intergerized. To retrieve the Prob_value value at the
receiving end, call pvalue=pow(10.0,slot[20]/10000.0).
The "charge" field contains the total neutrino event charge (in units of photo-electrons).
The units are centi-pe (ie the pe-count was multiplied by 100.0 and
then integerized).
[Note that this is not the same packing method as 'charge' in the AMON_ICECUBE_EHE packet.]
The "signal_trackness" field contains the probability that the neutrino event was signal and track-like.
The range is 0.0 to 1.0.
The units are centi-probability (ie the magnitude was multiplied by 100.0 and
then integerized).
The 'run_num' is the 2nd of two parts ('event_num' is first part, see above)
that uniquely identifies this event.
The "event_error50" is the radius of the circle that will contain on average
50% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized).
It contains the statistical error and the systematic error(TBD).
The "sub_sec" field contains the subseconds portion of the trigger_sod.
It contains the fractional-seconds portion to 6 significant digits;
0.123456*1e6 and then integerized.
There are a total of TBD "spare" items in the packet (usually filled
with zeros). They are located at items TBD-TBD.
B) EHE Field Descriptions:
The "event_num" is a uniquely identifying number for each event/trigger.
(See also 'run_num' below.)
The "trig_tjd" is the Truncated Julian Day of the AMON event,
eg. TJD=14466 is 01 Jan 2008.
The "trig_sod" is the UT seconds-of-day (SOD) of the AMON event.
The units are in centi-seconds (ie the fl.pt. seconds were multiplied by 100
and then integerized). The trigger time can be off by TBD msec.
The "ra" and "dec" fields specify the RA,Dec location of the multiply detected
event (in J2000 epoch). These intrinsically floating point quantities
have been multiplied by 10,000 and then integerized to make
an integer quantity with units of 10^-4-degrees.
The "n_events" field contains the number of events (ie neutrinos)
that occurred during the deltaT window. For ICECUBE_EHE type,
this number will always be 1 (ie one PeV neutrino). (Alway one, but this field
is still included in the EHE type to be symetric with the HESE and COINC types.)
The "event_error50" is the radius of the circle that will contain on average
90% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized).
It contains the statistical error and the systematic error(TBD).
The "deltaT" field contains the Time window of the burst.
The units are centi-sec (ie the deltaT was multiplied by 100 and then integerized).
The "sigmaT" field contains the Uncertainty of the time window.
The quantity stored in slot 14 is the log10() of the Sigma_T value from AMON
multiplied by 10,000 and then intergerized. To retrieve the time_interval value at the
receiving end, call sigma_t=pow(10.0,slot[14]/10000.0).
The "energy" field contains the lower bound energy estimate of the neutrino (in units of TeV).
The quantity stored in slot 15 is the log10() of the Energy value (in TeV)
multiplied by 10,000 and then intergerized. To retrieve the time_interval value at the
receiving end, call energy=pow(10.0,slot[14]/10000.0).
The "stream" field contains the index number identifying
which analysis stream produced this trigger. It ranges from 1 - NN.
The list of streams are: 0=undefined, 1=ICECUBE_HESE, 2=abc, 3=def, ...
The "rev" field contains the number of times this notice was revised (ie updated).
rev=0 means the first notice, 1 is the 1st revision, 2 is 2nd revision, etc.
For AMON_EHE type notices, the changes are most likely due to the RA,Dec,Error
values changing.
The "trig_id" field contains (a) flag bits on the type of solution
that was found by the AMON processing and
(b) flag bits that are assigned in the GCN ground-processing.
The bit packing of the "trig_id" entry in the packet is:
BitNum F-v-G Item_name Description
------ ---- --------- -----------
0 - spare spare for future use
1 G role=test Received with role="test"
2-4 - spare spare for future use
5 G retraction 0=No or 1=Yes, it is definitely not real, a Retraction
6-27 - spare spare for future use
28 G spatial_coinc 0=No or 1=Yes, there was a spatial coincidence with another event
29 G temporal_coinc 0=No or 1=Yes, there was a temporal coincidence with another event
30-31 - spare spare for future use
The columns are: "BitNum" is the 2^N location within the 4-byte word;
"Item_name" is the short-description name of the quantity; and
"Description" is the longer description of the quantity.
The "misc" field contains various bit_flags.
The bit packing is:
Bit_Number Item_name Description
---------- --------- -----------
0-7 spare Spare bits within 'misc'.
8-9 cite_type Citation type (0=undef,1=followup,2=supersedes,3=retraction)
10-23 spare Spare bits within 'misc'.
24-31 sernum 8 bits containing the type of the EHE serial number(tbd)
The "charge" field contains the total neutrino event charge (in units of photo-electrons).
The quantity stored in slot 21 is the log10() of the charge value (photo-electronics)
multiplied by 10,000 and then intergerized. To retrieve the Charge value at the
receiving end, call charge=pow(10.0,slot[21]/10000.0).
[Note that this is not the same packing method as 'charge' in the AMON_ICECUBE_HESE packet.]
The "signalness" field contains the probability that the neutrino event was signal and track-like.
The range is 0.00001 to 1.0.
The quantity stored in slot 22 is the log10() of the Signalness value from AMON
multiplied by 10,000 and then intergerized. To retrieve the Prob_value value at the
receiving end, call signalness=pow(10.0,slot[22]/10000.0).
The 'run_num' is the 2nd of two parts ('event_num' is first part, see above)
that uniquely identifies this event.
The "sub_sec" field contains the subseconds portion of the trigger_sod.
It contains the fractional-seconds portion to 6 significant digits;
0.123456*1e6 and then integerized.
C) COINC Field Descriptions:
The "trig_num" is a uniquely identifying number for each trigger within each given 'stream'. The "trig_tjd" is the Truncated Julian Day of the AMON event, eg. TJD=14466 is 01 Jan 2008. The "trig_sod" is the UT seconds-of-day (SOD) of the AMON event. The units are in centi-seconds (ie the fl.pt. seconds were multiplied by 100 and then integerized). The trigger time can be off by TBD msec. The "ra" and "dec" fields specify the RA,Dec location of the multiply detected event (in J2000 epoch). These intrinsically floating point quantities have been multiplied by 10,000 and then integerized to make an integer quantity with units of 10^-4-degrees. The "n_events" field contains the number of events (ie neutrinos) that occurred during the deltaT window. The "false_pos" (flase positive rate) field contains the expected number of this type of alerts per steradian per second in the vicinity of a given alert. The quantity stored in slot 10 is the log10() of the False_pos value from AMON multiplied by 10,000 and then intergerized. To retrieve the False_pos value at the receiving end, call false_pos=pow(10.0,slot[10]/10000.0). The "event_error90" is the radius of the circle that will contain on average 90% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied by 10000 and then integerized). It contains the statistical error and the systematic error(TBD). //The "event_type" field contains the. //The . The "deltaT" field contains the Time window of the burst. The units are centi-sec (ie the deltaT was multiplied by 100 and then integerized). The "sigmaT" field contains the Uncertainty of the time window. The units are centisec (ie the sigmaT was multiplied by 100 and then integerized). The "observing" is a bitmask field containing which detectors/instrument/observatories which had within their field of view a part of the sky where a given alert originated. This number is computed as a Sum(2^k), where k is observatory stream number. For example, IceCube is stream 0 for AMON, ANTARES is stream 1, so if both of these observatories are observing, this number would be 2^0+2^1=3.) Bit_Number Description ---------- ----------- 0 IceCube 1 ANTARIES 2 tbd 3 tbd 4 tbd The "stream" field contains the index number identifying which analysis stream produced this trigger. It ranges from 1 - NN. "Stream" (aka search_criteria_index / trigger_criteria_index) for the AMON alert means a specific set of search/analysis criteria used to define set of events as a special/temporal coincidence (maybe something as "trigger"). For example, the default stream looks for 100 sec time window and 2 sigma angular separation in order to accept events from different experiments as being in coincidence. There could be other analysis streams looking for coincidences using different search criteria (e.g. smaller or larger time window, requiring specific events to occur: e.g. requiring to have the IceCube HESE neutrinos in an alert). The list of streams are: 0=undefined, 1=ICECUBE_HESE, 2=abc, 3=def, ... The "rev" field contains the number of times this notice was revised (ie updated). rev=0 means the first notice, 1 is the 1st revision, 2 is 2nd revision, etc. Revisions can happen when (a) one of the original detectors updates their information (eg change in the number of neutrinos in their event), or (b) a 3rd detector now has a coincidence with the original two detectors (ie some detectors have longer data analysis times). The "trig_id" field contains (a) flag bits on the type of solution that was found by the AMON processing and (b) flag bits that are assigned in the GCN ground-processing. The bit packing of the "trig_id" entry in the packet is: BitNum F-v-G Item_name Description ------ ---- --------- ----------- 0-4 - spare spare for future use 5 G retraction 0=No or 1=Yes, it is definitely not real, a Retraction 6-27 - spare spare for future use 28 G spatial_coinc 0=No or 1=Yes, there was a spatial coincidence with another event 29 G temporal_coinc 0=No or 1=Yes, there was a temporal coincidence with another event 30-31 - spare spare for future use The columns are: "BitNum" is the 2^N location within the 4-byte word; "Item_name" is the short-description name of the quantity; and "Description" is the longer description of the quantity. The "misc" field contains various bit_flags. The bit packing is: Bit_Number Item_name Description ---------- --------- ----------- 0 IceCube They constributed to the AMON coincidence event 1 ANTARES They constributed to the AMON coincidence event 2-7 spare Spare bits within 'misc'. 8-9 cite_type Citation type (0=undef,1=followup,2=supersedes,3=retraction) 10-31 spare Spare bits within 'misc'. The "pvalue" field contains the probability value that the trigger is real (ie astrophysical, and not a chance coincidence). This alert p-value is calculated by combining p-values of each individual neutrino contributing to a given alert. Observatories should send AMON the p-values for their events. These event p-values measure some event quality from each observatory (e.g., for IceCube subthrehsold stream event p-value is a probability of an event being atmospheric neutrino of energy larger or equal than energy observed P(E>=E_observed)). In case that some observatory does not send AMON their event p-value, we can only report false alarm rate, but not valid combined p-value associated with the corresponding alert. The range of valuesi 0.0 to 1.0. The quantity stored in slot 20 is the log10() of the Prob_value value from AMON multiplied by 10,000 and then intergerized. To retrieve the Prob_value value at the receiving end, call pvalue=pow(10.0,slot[20]/10000.0). The "substream" field contains the index number identifying to which instrument should receive it during the proprietary phase. It ranges from 1 - NN. The "event_error50" is the radius of the circle that will contain on average 50% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied by 10000 and then integerized). It contains the statistical error and the systematic error(TBD). The "sub_sec" field contains the subseconds portion of the trigger_sod. It contains the fractional-seconds portion to 6 significant digits; 0.123456*1e6 and then integerized.
C) HAWC_BURST_MONITOR Field Descriptions:
The "event_ID" is a uniquely identifying number for each event/trigger.
(See also 'run_num' below.)
The "trig_tjd" is the Truncated Julian Day of the AMON event,
eg. TJD=14466 is 01 Jan 2008.
The "trig_sod" is the UT seconds-of-day (SOD) of the AMON event.
The units are in centi-seconds (ie the fl.pt. seconds were multiplied by 100
and then integerized). The trigger time can be off by TBD msec.
The "ra" and "dec" fields specify the RA,Dec location of the multiply detected
event (in J2000 epoch). These intrinsically floating point quantities
have been multiplied by 10,000 and then integerized to make
an integer quantity with units of 10^-4-degrees.
The "event_error" is the radius of the circle that will contain on average
68% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized).
It contains only the statistical error component; there is no systematic error component.
The "FAR" (False Alarm Rate) is the occurance rate of non-astrophysical events
that are of the same intensity (significance) as the current event.
The quantity stored in slot 12 is the log10() of the rate
multiplied by 10,000 and then integerized. To retrieve the "FAR" value at the
receiving end, call FAR=pow(10.0,slot[12]/10000.0).
The "deltaT" field contains the Time window of the burst.
The units are centi-sec (ie the deltaT was multiplied by 100 and then integerized).
The deltaT values are 0.2, 1.0, 10,0, and 100 seconds.
The "event_ID" is a uniquely identifying number for each event/trigger.
(See also 'run_ID' below.)
The "stream" field contains the index number identifying
which analysis stream produced this trigger. It ranges from 1 - NN.
The list of streams are: 0=undefined, 1=ICECUBE_HESE, 2=EHE, 3-6=tbd,
7 =HAWC_Burst, 8-23=tbd, 24=IceCube_Gold, 25=IceCube_Bronze, ...
The "rev" field contains the number of times this notice was revised (ie updated).
rev=0 means the first notice, 1 is the 1st revision, 2 is 2nd revision, etc.
For AMON_HAWK_BURST_MONITOR type notices, the changes are most likely due to the RA,Dec,Error
values changing. (TBR)
The "trig_id" field contains (a) flag bits on the type of solution
that was found by the AMON processing and
(b) flag bits that are assigned in the GCN ground-processing.
The bit packing of the "trig_id" entry in the packet is:
BitNum F-v-G Item_name Description
------ ---- --------- -----------
0 - spare spare for future use
1 G role=test Received with role="test"
2-4 - spare spare for future use
//5 G retraction 0=No or 1=Yes, it is definitely not real, a Retraction
6-27 - spare spare for future use
//28 G spatial_coinc 0=No or 1=Yes, there was a spatial coincidence with another event
29 G temporal_coinc 0=No or 1=Yes, there was a temporal coincidence with another event
30-31 - spare spare for future use
The columns are: "BitNum" is the 2^N location within the 4-byte word;
"Item_name" is the short-description name of the quantity; and
"Description" is the longer description of the quantity.
i
The "misc" field contains various bit_flags.
The bit packing is:
Bit_Number Item_name Description
---------- --------- -----------
0-7 spare Spare bits within 'misc'.
//8-9 cite_type Citation type (0=undef,1=followup,2=supersedes,3=retraction)
10-31 spare Spare bits within 'misc'.
The "pvalue" field contains the post-trials probability value of the event.
The quantity stored in slot 20 is the log10() of the rate
multiplied by 10,000 and then integerized. To retrieve the "pvalue" value at the
receiving end, call pvalue=pow(10.0,slot[20]/10000.0).
The 'run_ID' is the 2nd of two parts ('event_ID' is first part, see above)
that uniquely identifies this event.
The "url" is just the filename portion of the skymap URL -- the leading path
for the full URL is "http://not.yet.defined/notices/" for thr AMON archive and
"http://gcn.gsfc.nasa.gov/gcn/not-yet-defined/(TBD)" for the GCN archive.
This item in the packet spans 10 longwords (ie 40 bytes, ie up to 40 character) and contains
the ASCII string of the filename portion of the URL. This string
can be up to 39 characters long, and will always be null-terminated.
The combined/full url will look like:
"http://not.yet.defined/not-yet-defined/
D) ICECUBE_ASTROTRACK_GOLD Field Descriptions:
The "event_ID" is a uniquely identifying number for each event/trigger.
(See also 'run_ID' below.)
The "trig_tjd" is the Truncated Julian Day of the AMON event,
eg. TJD=14466 is 01 Jan 2008.
The "trig_sod" is the UT seconds-of-day (SOD) of the AMON event.
The units are in centi-seconds (ie the fl.pt. seconds were multiplied by 100
and then integerized). The trigger time can be off by TBD msec.
The "ra" and "dec" fields specify the RA,Dec location of the multiply detected
event (in J2000 epoch). These intrinsically floating point quantities
have been multiplied by 10,000 and then integerized to make
an integer quantity with units of 10^-4-degrees.
The "event_error90" is the radius of the circle that will contain on average
90% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized).
It contains only the statistical error component; there is no systematic error component.
The "event_ID" is the first part of the identification of the IceCube event.
The "energy" field contains the lower bound energy estimate of the neutrino (in units of TeV).
The quantity stored in slot 15 is the log10() of the Energy value (in TeV)
multiplied by 10,000 and then integerized. To retrieve the energy value at the
receiving end, call energy=pow(10.0,slot[15]/10000.0).
The "stream" field contains the index number identifying
which analysis stream produced this trigger. It ranges from 1 - NN.
The list of streams are: 0=undefined, 1=ICECUBE_HESE, 2=EHE, 3-6=tbd,
7 =HAWC_Burst, 8-23=tbd, 24=IceCube_Gold, 25=IceCube_Bronze, ...
The "rev" field contains the number of times this notice was revised (ie updated).
rev=0 means the first notice, 1 is the 1st revision, 2 is 2nd revision, etc.
For ICECUBE_ASTROTRACK_GOLD type notices, the changes are most likely due to the RA,Dec,Error
values changing.
The "trig_id" field contains (a) flag bits on the type of solution
that was found by the AMON processing and
(b) flag bits that are assigned in the GCN ground-processing.
The bit packing of the "trig_id" entry in the packet is:
BitNum F-v-G Item_name Description
------ ---- --------- -----------
0 - spare spare for future use
1 G role=test Received with role="test"
2-4 - spare spare for future use
//5 G retraction 0=No or 1=Yes, it is definitely not real, a Retraction
6-27 - spare spare for future use
28 G spatial_coinc 0=No or 1=Yes, there was a spatial coincidence with another event
29 G temporal_coinc 0=No or 1=Yes, there was a temporal coincidence with another event
30-31 - spare spare for future use
The columns are: "BitNum" is the 2^N location within the 4-byte word;
"Item_name" is the short-description name of the quantity; and
"Description" is the longer description of the quantity.
The "misc" field contains various bit_flags.
The bit packing is:
Bit_Number Item_name Description
---------- --------- -----------
0-7 spare Spare bits within 'misc'.
8-9 cite_type Citation type (0=undef,1=followup,2=supersedes,3=retraction)
10-23 spare Spare bits within 'misc'.
24-31 sernum 8 bits containing the type of the EHE serial number(tbd)
The "FAR" (False Alarm Rate) field contains the rate of background events
that are "like this alert" that would be seen by IceCube per year.
The quantity stored in slot 20 is the log10() of the rate
multiplied by 10,000 and then integerized. To retrieve the "FAR" value at the
receiving end, call FAR=pow(10.0,slot[21]/10000.0).
The "signalness" field contains the probability that the neutrino event was signal and track-like.
The range is 0.00001 to 1.0.
The quantity stored in slot 22 is the log10() of the Signalness value from AMON
multiplied by 10,000 and then integerized. To retrieve the Prob_value value at the
receiving end, call signalness=pow(10.0,slot[22]/10000.0).
The 'run_ID' is the 2nd of two parts ('event_ID' is first part, see above)
that uniquely identifies this event.
The "event_error50" is the radius of the circle that will contain on average
50% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized).
It contains only the statistical error component; there is no systematic error component.
E) ICECUBE_ASTROTRACK_BRONZE Field Descriptions:
The "event_num" is a uniquely identifying number for each event/trigger.
(See also 'run_num' below.)
The "trig_tjd" is the Truncated Julian Day of the AMON event,
eg. TJD=14466 is 01 Jan 2008.
The "trig_sod" is the UT seconds-of-day (SOD) of the AMON event.
The units are in centi-seconds (ie the fl.pt. seconds were multiplied by 100
and then integerized). The trigger time can be off by TBD msec.
The "ra" and "dec" fields specify the RA,Dec location of the multiply detected
event (in J2000 epoch). These intrinsically floating point quantities
have been multiplied by 10,000 and then integerized to make
an integer quantity with units of 10^-4-degrees.
The "event_error90" is the radius of the circle that will contain on average
90% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized).
It contains only the statistical error component; there is no systematic error component.
The "event_ID" is the first part of the identification of the IceCube event.
The "energy" field contains the lower bound energy estimate of the neutrino (in units of TeV).
The quantity stored in slot 15 is the log10() of the Energy value (in TeV)
multiplied by 10,000 and then integerized. To retrieve the energy value at the
receiving end, call energy=pow(10.0,slot[15]/10000.0).
The "stream" field contains the index number identifying
which analysis stream produced this trigger. It ranges from 1 - NN.
The list of streams are: 0=undefined, 1=ICECUBE_HESE, 2=EHE, 3-6=tbd,
7 =HAWC_Burst, 8-23=tbd, 24=IceCube_Gold, 25=IceCube_Bronze, ...
The "rev" field contains the number of times this notice was revised (ie updated).
rev=0 means the first notice, 1 is the 1st revision, 2 is 2nd revision, etc.
For ICECUBE_ASTROTRACK_BRONZE type notices, the changes are most likely due to the RA,Dec,Error
values changing.
The "trig_id" field contains (a) flag bits on the type of solution
that was found by the AMON processing and
(b) flag bits that are assigned in the GCN ground-processing.
The bit packing of the "trig_id" entry in the packet is:
BitNum F-v-G Item_name Description
------ ---- --------- -----------
0 - spare spare for future use
1 G role=test Received with role="test"
2-4 - spare spare for future use
//5 G retraction 0=No or 1=Yes, it is definitely not real, a Retraction
6-27 - spare spare for future use
28 G spatial_coinc 0=No or 1=Yes, there was a spatial coincidence with another event
29 G temporal_coinc 0=No or 1=Yes, there was a temporal coincidence with another event
30-31 - spare spare for future use
The columns are: "BitNum" is the 2^N location within the 4-byte word;
"Item_name" is the short-description name of the quantity; and
"Description" is the longer description of the quantity.
The "misc" field contains various bit_flags.
The bit packing is:
Bit_Number Item_name Description
---------- --------- -----------
0-7 spare Spare bits within 'misc'.
8-9 cite_type Citation type (0=undef,1=followup,2=supersedes,3=retraction)
10-23 spare Spare bits within 'misc'.
24-31 sernum 8 bits containing the type of the EHE serial number(tbd)
The "FAR" (False Alarm Rate) field contains the rate of background events
that are "like this alert" that would be seen by IceCube per year.
The quantity stored in slot 20 is the log10() of the rate
multiplied by 10,000 and then integerized. To retrieve the "FAR" value at the
receiving end, call FAR=pow(10.0,slot[20]/10000.0).
The "signalness" field contains the probability that the neutrino event was signal and track-like.
The range is 0.00001 to 1.0.
The quantity stored in slot 22 is the log10() of the Signalness value from AMON
multiplied by 10,000 and then integerized. To retrieve the Prob_value value at the
receiving end, call signalness=pow(10.0,slot[22]/10000.0).
The 'run_ID' is the 2nd of two parts ('event_ID' is first part, see above)
that uniquely identifies this event.
The "event_error50" is the radius of the circle that will contain on average
50% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized).
It contains only the statistical error component. There is no systematic error component.
F) AMON_NU_EM_COINC Field Descriptions:
The AMON_NU_EM_COINC Event packets consist of 40 four-byte quantities.
The order and contents are listed in the table below:
For Type = 172
Declaration Index Item Units Comments
Type Name
----------- ----- --------- ---------- ----------------
long 0 pkt_type integer Packet type number (=172)
long 1 pkt_sernum integer 1 thru 4 billion
long 2 pkt_hop_cnt integer Incremented by each node
long 3 pkt_sod [centi-sec] (int)(sssss.sss *100)
long 4 event_num integer Event Trigger/ID number
long 5 event_tjd [days] Truncated Julian Day
long 6 event_sod [centi-sec] (int)(sssss.sss *100)
long 7 event_ra [0.0001-deg] (int)(0.0 to 359.9999 *10000)
long 8 event_dec [0.0001-deg] (int)(-90.0 to +90.0 *10000)
long 9 n_events integer CONFIRM THIS
long 10 spare integer 4 bytes for the future
long 11 evt_error90 [0.0001-deg] (int)(0.0 to 180.0 *10000) 90% Conf
long 12 FAR [# per yr] pow(10.0,slot[12]/10000.0)
long 13 deltaT [centi-sec] (int)(0.0 to 0.999999 *100)
long 14-15 spare[2] integer 8 bytes for the future
long 16 stream integer Which instrument/data source
long 17 rev [dn] 0-N (revision/update serial number)
long 18 trig_id bits Trigger identification flags
long 19 misc bits Misc stuff packed in here
//long 20 pvalue [0.0-1.0] Probability that is real astrophysical // NOT USED
long 21-22 spare[2] integer 8 bytes for the future
long 23 run_num [dn] Run number in which the Event was found
long 24 evt_error50 [0.0001-deg] (int)(0.0 to 180.0 *10000) 50% Conf
long 25 sub_sec integer Subsec portion of the event_sod trigger time
long 26-35 spare[10] integer 40 bytes for the future
quad_char 36-38 evt_date[3] chars The Event_Date Name for this event
long 39 pkt_term integer Pkt Termination (always = \n)
PACKET ITEM DESCRIPTIONS:
The "pkt_type" is an integer with a value of 172, which tells that this packet
is of type AMON_NU_EM_COINC and therefore indicates the contents and format
for the other 39 fields.
The "pkt_sernum" is the serial number for that packet type. Each packet type
has its own sequential serial numbering. They all start at 1
when the GCN program starts up.
The "pkt_hop_cnt" is a sequential numbering scheme that is incremented by 1
for each machine that the packet passes through (starting from 0 on the
machine of origin -- sometimes PK and sometimes capella2). It is used
in checking the hand-shake processing through the PK, CC, and capella2 machines
within the GCN system. Since the loss of GRO (May 2000), and therefore
the elimination of the PK and CC front-end processors, this hopcount item
is defunct -- all packets start on capella2 with a hopcount value of 0.
The "pkt_sod" is UT seconds-of-day when the packet was created/sent from
the GCN computer. Do not confuse this with the trig_sod (see below).
The value is multiplied by 100 and integerized (i.e. the units are centi-sec; 10 msec).
The "event_num" is a uniquely identifying number for each event/trigger.
(See also 'run_num' below.)
The "trig_tjd" is the Truncated Julian Day of the AMON event,
eg. TJD=14466 is 01 Jan 2008.
The "trig_sod" is the UT seconds-of-day (SOD) of the AMON event.
The units are in centi-seconds (ie the fl.pt. seconds were multiplied by 100
and then integerized). The trigger time can be off by TBD msec.
[7-8] The "ra" and "dec" fields specify the RA,Dec location of the multiply detected
event (in J2000 epoch). These intrinsically floating point quantities
have been multiplied by 10,000 and then integerized to make
an integer quantity with units of 10^-4-degrees.
[9] "n_events" ....
[11] The "event_error90" is the radius of the circle that will contain on average
90% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized).
It contains the statistical error and the systematic error(TBD).
[12] The "FAR" (False Alarm Rate) is the occurance rate of non-astrophysical events
that are of the same intensity (significance) as the current event.
The quantity stored in slot 12 is the log10() of the rate
multiplied by 10,000 and then integerized. To retrieve the "FAR" value at the
receiving end, call FAR=pow(10.0,slot[12]/10000.0).
[13] The "deltaT" field contains the Time window of the burst.
The units are centi-sec (ie the deltaT was multiplied by 100 and then integerized).
[16] The "stream" field contains the index number identifying
which analysis stream produced this trigger. It ranges from 1 - NN.
The list of streams are: 0=undefined, 1=ICECUBE_HESE, 2=abc, 3=def, ...
[17] The "rev" field contains the number of times this notice was revised (ie updated).
rev=0 means the first notice, 1 is the 1st revision, 2 is 2nd revision, etc.
For AMON_NU_EM_COINC type notices, the changes are most likely due to the ?????
values changing.
[18] The "trig_id" field contains (a) flag bits on the type of solution YET TO CHECK/REVISE!!!
that was found by the AMON processing and
(b) flag bits that are assigned in the GCN ground-processing.
The bit packing of the "trig_id" entry in the packet is:
BitNum F-v-G Item_name Description
------ ---- --------- -----------
//0 G private This is a private event (only to AMON Team) //NOT USED
1 G role=test Received with role="test"
2-4 - spare spare for future use
5 G retraction 0=No or 1=Yes, it is definitely not real, a Retraction. Not now, but eventually.
6-11 G coinc_pairs The instrument coinc pairs ID index (6 bits, 0-63) (See table below)
12-27 - spare spare for future use
//28 G spatial_coinc 0=No or 1=Yes, there was a spatial coincidence with another event ?????
29 G temporal_coinc 0=No or 1=Yes, there was a temporal coincidence with another event ?????
30-31 - spare spare for future use
The columns are: "BitNum" is the 2^N location within the 4-byte word;
"Item_name" is the short-description name of the quantity; and
"Description" is the longer description of the quantity.
Table of Coinc_Pair_Index values and the Instrument_Pair_Names:
0 "illegal value"
1 "IC-HAWC"
2 "IC-Swift"
3 "IC-HESE-EHE"
4 "IC-Fermi"
5 "OFU-Alerts"
6 "GFU-Alerts"
7 "HAWC-GRBlike-Alert"
8 "Antares-Fermi"
9 "IC-Gold-Bronze"
10 "Inst1-Inst2" // future
11 "Inst3-Inst4" // future
[19] The "misc" field contains various bit_flags. YET TO CHECK/REVISE!!!
The bit packing is:
Bit_Number Item_name Description
---------- --------- -----------
0-7 spare Spare bits within 'misc'.
//8-9 cite_type Citation type (0=undef,1=followup,2=supersedes,3=retraction)
10-31 spare Spare bits within 'misc'.
[20] The "pvalue" proability that this event is astrophysical real.
It has a dynamic range of 0.0 to 1.0. Currently is is not used.
The AMON team fills this slot with a value which is always 1.0.
The quantity stored in slot 15 is the log10() of the pvalue value (in ???)
multiplied by 10,000(TBC) and then integerized. To retrieve the pvalue value at the
receiving end, call pvalue=pow(10.0,slot[20]/10000.0(TBC)).
[23] The "run_num" is ... (vs "run_ID" as in Type 171)(TBD)
[24] The "event_error50" is the radius of the circle that will contain on average
50% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized).
It contains the statistical error and the systematic error(TBD).
[25] The "sub_sec" is the subseconds portion of the trigger time.
Take the 4 bytes (unsigned integer) and divide by 1,000,000.0
and add to the Trigger_SOD[6] to get the full Trigger_SOD value.
[36-38] The "evt_date" is date-based name for this event: YYYYMMDDa.
There are a total of 15 "spare" items in the packet (usually filled
with zeros). They are located at items 10, 14-15, 21-22, and 26-33.
G) AMON_ICECUBE_CASCADE Field Descriptions:
The AMON_ICECUBE_CASCADE Event packets consist of 40 four-byte quantities.
The order and contents are listed in the table below:
For Type = 176:
Declaration Index Item Units Comments
Type Name
----------- ----- --------- ---------- ----------------
long 0 pkt_type integer Packet type number (=176)
long 1 pkt_sernum integer 1 thru infinity
long 2 pkt_hop_cnt integer Incremented by each node
long 3 pkt_sod [centi-sec] (int)(sssss.sss *100)
long 4 trig_num integer Trigger num
long 5 event_tjd [days] Truncated Julian Day
long 6 event_sod [centi-sec] (int)(sssss.sss *100)
long 7 ra [0.0001-deg] (int)(0.0 to 359.9999 *10000)
long 8 dec [0.0001-deg] (int)(-90.0 to +90.0 *10000)
long 9 energy [centi-TeV] (int)(lowest_energy *100)
long 10 pos_error_50 [0.0001-deg] (int)(0 to 180.0 *10000) 50% Conf
long 11 pos_error_90 [0.0001-deg] (int)(0 to 180.0 *10000) 90% Conf
long 12 far [yr^-1] (int)(log10(far)*10000)
long 13-14 spare[2] integer 8 bytes for the future
long 15 event_id integer AMON Event_ID number
long 16 stream integer AMON Stream number
long 17 rev integer AMON version number
long 18 trig_id bits Trigger identification flags
long 19 misc bits Misc stuff packed in here
long 20-21 spare[2] integer 8 bytes for the future
long 22 signalness [0.01-1.0] (int)(log10(signalness)*10000)
long 23 run_num integer AMON Run Number (in the millions)
long 24-25 spare[2] chars 8 bytes for the future
quad_char 26-28 name[3] chars The common_name string for the event
quad_char 29-38 url[10] chars The URL for the skywatch_url
long 39 pkt_term integer Pkt Termination (always = \n)
PACKET ITEM DESCRIPTIONS (for 176):
[0] The "pkt_type" is an integer with a value of 176 for the AMON_ICECUBE_CASCADE type.
It tells which type of packet this is and therefore what the contents are
(the contents change somewhat between the various types).
[1] The "pkt_sernum" is the serial number for that packet type. Each packet type
has its own sequential serial numbering. They all start at 1
when the GCN program starts up.
[2] The "pkt_hop_cnt" is a sequential numbering scheme that is incremented by 1
for each machine that the packet passes through (starting from 0 on the
machine of origin -- sometimes PK and sometimes capella2). It is used
in checking the hand-shake processing through the PK, CC, and capella2 machines
within the GCN system. Since the loss of GRO (May 2000), and therefore
the elimination of the PK and CC front-end processors, this hopcount item
is defunct -- all packets start on capella2 with a hopcount value of 0.
[3] The "pkt_sod" is UT seconds-of-day when the packet was created/sent from
the GCN computer. Do not confuse this with the trig_sod (see below).
The value is multiplied by 100 and integerized (i.e. the units are centi-sec; 10 msec).
[4] The "trig_num???" is a uniquely identifying number for each trigger.
[5] The "trig_tjd" is the Truncated Julian Day of the LVC event,
eg. TJD=14466 is 01 Jan 2008.
[6] The "trig_sod" is the UT seconds-of-day (SOD) of the LVC event.
The units are in centi-seconds (ie the fl.pt. seconds were multiplied by 100
and then integerized). The trigger time can be off by TBD msec.
LVC has higher precission for the actual trigger SOD, but this field is kept
for LVC to be uniform with all the other GCN Notice types. See slot 13
for the full 6 digits of precision (ie micro-sec) for the LVC Trigger SOD.
[7-8] The "ra" and "dec" specifies the RA,Dec location where the neutrino came from
(in J2000 epoch). These intrinsically floating point quantities
have been multiplied by 10,000 and then integerized to make
an 32-bit integer quantity with units of 10^-4-degrees.
[9] The "energy" is the emergy of the neutrino in units of TeV. It is accurate
to 5-10%. The units are 0.01-TeV (ie the fl.pt. energy was multiplied
by 100 and then integerized).
[10] The "pos_error_50" is the radius of the circle that will contain on average
50% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized). It contains both the statistical error component and
the systematic error component combined.
[11] The "pos_error_90" is the radius of the circle that will contain on average
90% of the sources. The units are 0.0001-degrees (ie the fl.pt. error was multiplied
by 10000 and then integerized). It contains both the statistical error component and
the systematic error component combined.
[12] The "far" is the false alarm rate. The units are [1/yr].
The quantity stored in slot 12 is the log10() of the FAR value multiplied by 10,000
and then integerized. To retrieve the FAR value at the receiving end,
call far=pow(10.0,slot[12]/10000.0).
[15] The "event_id" is the Event_ID number assigned by AMON during the processing.
[16] The "stream" is the Stream number assigned by AMON during the processing.
[17] The "rev" is the version number assigned by AMON during the processing.
[18] The "trig_id" field contains (a) flag bits on the type of solution
that was found by the IceCube pipeline processing and
(b) flag bits that are assigned in the GCN ground-processing.
The bit packing of the "trig_id" entry in the packet is:
BitNum F-v-G Item_name Description
------ ---- --------- -----------
0 G internal_flag LCV_internal distribution(=1), Full distribution(=0)
1 G test_flag Test-type: 0=Real, 1=Test
2-4 - spare spare for future use
5 G retraction 0=No or 1=Yes, it is definitely not real, a Retraction
6-28 - spare spare for future use
29 G temporal_coinc 0=No or 1=Yes, there was a temporal coincidence with another event
30 test_submit 0=No or 1=Yes, this is a test submission (internal use only)
31 spare spare for furture use
The columns are: "BitNum" is the 2^N location within the 4-byte word;
"Item_name" is the short-description name of the quantity; and
"Description" is the longer description of the quantity.
[19] The "misc" field contains various bit_flags.
The bit packing is:
Bit_Number Item_name Description
---------- --------- -----------
0-18 spare Spare bits within 'misc'.
19 Gnd_gen When this bit is a 1, then this Notice was ground-generated; else flight-generated.
Always 1 for Test Notices.
20-31 spare Spare bits within 'misc'.
[22] The "signalness" field contains the probability that the neutrino event was signal and track-like.
The range is 0.00001 to 1.0.
The quantity stored in slot 22 is the log10() of the Signalness value from AMON
multiplied by 10,000 and then integerized. To retrieve the Prob_value value at the
receiving end, call signalness=pow(10.0,slot[22]/10000.0).
[23] The 'run_num' is the 2nd of two parts ('event_ID' is first part, see above)
that uniquely identifies this event.
[26-28] The common "name" for this event. Sorted in these 3 slots is the "YYMMDDa" part
of the "IceCubeCascade-YYMMDDa" name string.
[29-38] The "url_c0-3" is the start of slot ?? for ....
???It is not defined for the Preliminary or Counterpart Notice types.
It is a string that looks like: M131119/files/lalinference_nest.fits.gz
It needs to be combined with:
???https://gracedb.ligo.org/apibasic/events
???[Note that prior to 24jul15, it was recommended that https://gracedb.ligo.org/events/
???be used as the prefix string. But this is the x509-based url string, and x509
???requires that the recipient have an x509 certificate, and be able to launch a java script,
???and this was just too complicated. So LVC created a simplier web-based interface.]
???to make the full URL:
???https://gracedb.ligo.org/apibasic/events/M131119/files/lalinference_nest.fits.gz
For AMON_ICECUBE_CASCADE there are a total of ?? "spare" items in the packet (usually filled
with zeros). They are located at items ?-? and ??-??.