03 Nov 16    AMON_ICECUBE_EHE HAS TWO NEW FIELDS
The IceCube Team has added the 'charge' and 'energy' fields to the AMON_ICECUBE_EHE notice.

GCN/AMON Notices

TABLE OF CONTENTS:

  1. Introduction
  2. Notice types, Content, and Purpose
  3. Positions, Errors and Time_delays
  4. Occurrence Rates
  5. Sequence of Activities
  6. Retractions
  7. Formats
  8. Filtering
  9. Observing Strategy
  10. Recognition
  11. Further Help
  12. Archiving
  13. Misc
  14. E-mail Examples
  15. Cell/Pager Examples

Introduction

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.
Currently, only HESE notices (High Energy Starting Event) and the EHE notices (Extremely High Energy)
from the IceCube instrument are being produced.
This will expand to other instruments and inter-instrument coincidences as time goes on.

For the HESE notice type, the occurrence rate will be about 3.5/yr. PUBLIC
For the EHE notice type, the occurrence rate will be about 4-6/yr. PUBLIC
For the COINC notice type, the occurence rate will be about 10/yr. PRIVATE

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.

Notice Types, Content, and Purpose

There are 3 GCN/AMON Notice types. (Of these, only the HESE and EHE is currently publically distributed.)
They are:

   1) AMON_ICECUBE_HESE Notice: a single high-energy IceCube neutrino. ACTIVE

   2) AMON_ICECUBE_EHE Notice: an extremely high-energy IceCube neutrino. ACTIVE

   3) AMON_ICECUBE_COINC Notice: a coincidence between 2 or more low-energy IceCube neutrinos. NOT YET PUBLIC

Positions, Error and Time_delays

The AMON automated pipeline will ingest the data from all the 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            ACTIVE
AMON_ICECUBE_EHE     0.2-0.8deg   0.5-3 min     Direction of a single extremely hi-energy neutrino  ACTIVE
AMON_ICECUBE_COINC   1-3deg       0.5-3 min     Temporal/spatial coinc between IceCube neutrinos    NOT YET PUBLIC
==================   =========    ===========   ================================================

ERROR CIRCLES:

HESE:
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:
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.

COINC:
The uncertainty in the location is computed from a weighted sum of uncertainties of
individual neutrinos contributed to a given alert. The positional uncertainties of single neutrinos represent
quality of the online position reconstruction (stat+syst), and they are computed in real-time.
The typical error is:
      1 to 3 [deg], radius, statistical plus systematic, 90% containment.
      0.5 to 1 [deg], radius, statistical plus systematic, 50% containment.

Occurrence rates

The rates from the various notice types are:

TYPE                 RATE       COMMENTS
==================   ========   ================================================
AMON_ICECUBE_HESE    0.4/month  Direction of a single hi-energy neutrino             ACTIVE
AMON_ICECUBE_EHE     0.5/month  Direction of a single extremely hi-energy neutrino   ACTIVE
AMON_ICECUBE_COINC   1/month    Temporal/spatial coinc between IceCube neutrinos     NOT YET PUBLIC
==================   ========   ================================================

Sequence of Activities

The sequence of activities for a typical event follows:
ICECUBE_HESE, ICECUBE_EHE, and ICECUBE_COINC

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.

Retractions

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.

Formats

EMAIL-BASED: Samples of the E-mail, Cell/Pager, Short-form Cell/Pager, & Subject-only
distribution methods of the 3 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
169  ICECUBE_EHE          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)

Filtering

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.
See filtering to see which filter functions are applicable.
These filters apply to all the existing distribution methods/media.

Observing Strategy

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, HESE and EHE streams has all-sky coverage.

Recognition

Sites are encouraged to acknowledge IceCube, AMON, and GCN in their publications
based on follow-up observations using these GCN/AMON_ICECUBE_HESE and GCN/AMON_ICECUBE_EHE locations.

Further Help

For further information on this, please contact
Scott Barthelmy (for GCN issues),
or see the
and
ICECUBE_HESE document, and
ICECUBE_EHE document, and
these GCN web pages, and

Archiving

All past notices and lightcurves are archived at:
GCN/AMON_ICECUBE_HESE Triggers table.
GCN/AMON_ICECUBE_EHE Triggers table.

Misc

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.

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(???)

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(???)

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              ????
3              ????
4              ????

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.

E-mail Examples

Examples of the 3 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
GCN/AMON_ICECUBE_EHE
GCN/AMON_ICECUBE_COINC

//////////////////////// 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.
//////////////////////// COINC e-mail format //////////////////////////////////////

Cell/Pager Examples

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!!!]
///////////////////////////////////////////////////////////////////////////////////

Short-form Cell/Pager Examples

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!!!]
///////////////////////////////////////////////////////////////////////////////////


Subject-only 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 examples!!!]
///////////////////////////////////////////////////////////////////////////////////


Return to GCN/TAN homepage.
This file was last modified on 02-Nov-16.