Late News:
This mission is over.
No burst triggers have been received since Aug 2006.
The HETE Notices (emails and socket packets) now have several additions: the WXM Image X&Y Signal/Noise, the WXM Lightcurve X&Y Signal/Noise, the S/C Longitude, and the Ecliptic Lon,Lat of the burst location. See the details. (08 Apr 02)
The HETE Ops team is no longer distributing trigger Notices which are due to x-ray burst sources (since several days ago). This explains the dramatic decrease in the number of GCN/HETE Notices. However, if HETE triggers on a GRB, it will still be distributed to GCN (and therefore to the world). [GCN OPS 06 Aug 01]
GndAna Filtering: The blocking filter for GndAna Notices with no positions has been removed. See the details. (01 Aug 01)
Recent status of HETE and the various GCN/HETE Notices. From the HETE perspective: Circular #1084. From the GCN perspective: Circular #1085.
The Multiple Messages Episode for Triggers 1554 & 1554 (16 Jun 01) See here for an explanation of the difficulties with processing HETE triggers 1554 and 1555.
Label Changes for Notice Types(18 Jun 01) See the announcement of the label changes for the HETE email and pager formats.
Distribution of HETE Positions:
As of 31 May 2001,
The GCN system is distributing HETE Notices (all 4 types: S/C_Alert, S/C_Update,
S/C_Last, and GroundAnalysis).
This is the fully automated procedure: HETE to ground to GCN to the world.
See announcement Circular #1064
TABLE OF CONTENTS:
The GCN system has been modified to incorporate the distribution of locations of GRBs detected by the 3 instruments on the HETE2 spacecraft: the Fregate GRB monitor, the Wide-field X-ray Monitor (WXM), and the Soft X-ray Camera (SXC).
About 30 times a year, there will be a GRB in the FOV of the WXM and/or SXC instruments that is bright enough to be localized. Positons will be calculated on-board, transmitted to the ground to the HETE Secondary Ground Stations network, collected by the HETE Mission Operations center, and forwarded to the GCN system for distribution to those sites wishing to receive these Notice types.
Like all the other sources of GRB locations within the GCN system, users can elect to receive (or not) these HETE Notices.
The GCN/HETE Notices are archived within the GCN website in the Table of HETE GRBs.
Schedule: Even though the HETE2 launch was 09 Oct 2000, the positions will not be immediately available. The HETE team will be performing an on-orbit check-out, during which the positions will not be made available to the public. There are numerous cross-checks and calibrations that must be performed to guarantee the safety of the s/c & instruments and the accuracy of the burst positions. After this check-out period, the positions will be available and distributed through GCN, and even then they will not be available in real-time -- the positions will be generated and/or checked on the ground (not on-board). And after this ground-in-the-loop phase, HETE & GCN will switch to the fully automated mode of on-board position calculation and rapid transmission to GCN (and on to the world).
Notice Types, Content, and Purpose
There are 4 GCN/HETE Notice types. They are:
1) HETE_S/C_ALERT packets just notifies that HETE has detected a burst,
but does not guarantee that the trigger was due to a valid burst,
or that a localization will be forthcoming.
Strength of burst and timescale are supplied.
This is the first Notice for a given trigger; it appears only once
for each trigger.
On rare occasions when the s/c is out of contact
with the Secondary Ground Stations, the S/C will create the S/C_Alert
before contact is re-established. This S/C_Alert will have the position determination
and so it is possible to have an S/C_Alert with a position. This will happen <10%
of the time.
2) HETE_S/C_UPDATE packets contain any new burst information
and, most importantly, the best localizations to date
from the WXM and/or SXC, along with "goodness" indicators for each.
Zero to N messages of this type are possible (the 0 case is possible
if the burst is over before a Secondary Ground Station comes into view
and so only the S/C_Last would be transmitted -- this is rare).
It is also possible to have these Updates without any position information.
The operations team can (and has) commanded off the position content;
this is happening while the s/c is looking at the very active Galactic Center
which is producing a high rate of X-ray Burster triggers of very low
detection significance (and therefore large position error).
3) HETE_S/C_LAST packets give a summary of the on-board analyses of the burst.
This includes the timescale of the burst, peak brightness,
best (if any) localizations by the WXM and SXC, and, if appropriate
a "never mind" indicator and the reason for the burst's invalidation (ie a non-GRB trigger).
This is the last of the real-time Notices; it appears only once
for each trigger.
4) HETE_GROUND_ANALYSIS packets contain the best positions available
from ground post-processing at the time of the message.
Multiple messages of this type are possible, if the ground team
conducts even further analysis.
Please note that it is possible for a trigger to be classified
as "definite GBR" but contain no position. This happens when a burst
does not have a large enough signal-to-noise ratio to calculate
a reliable position, or when a burst is outside the FOV
of the two imaging instruments and is determined to be a burst
by looking at the FREGATE light curve or from some external information
e.g information from another mission.
Instruments, Positions, and Time_delays
The HETE spacecraft is equipped with a wide-field GRB detector and two wide-field X-ray imagers. The Wide-Field X-ray Monitor (WXM) can deliver positions as small as +/- 7' within minutes of the burst, while the Soft X-ray Camera (SXC) can deliver positions < 30" in real time. It is expected that the SXC will see roughly 1/3 of the bursts that the WXM sees, given their relative sensitivity.
But please note that the above error box sizes are applicable only after the initial check-out phase of the mission. Until then, the "fine tuning" of the on-board s/c attitude determination software will not be completed, and, therefore, there will be a sizable systematic error contribution to the total error circle size. This systematic will be typicaly be 2-4 degrees in diameter.
The HETE spacecraft will generate GRB notifications and positions in real time during flight. In addition, analyses of downlinked data will result in a revised position in the hours after the burst. The timescales and localization precisions at the various Notice types are as follows:
Subtype Time since burst WXM precision SXC precision Comments ======= ================ ============= ============= ======== S/C_Alert 10-20s none none No localization yet S/C_Update 10-30s +/- 14' +/- 30" Assuming the burst is seen S/C_Last 30-300s +/- 7' +/- 30" Last in the s/c sequence GndAna 1-5 hr +/- 2-5' +/- 10" Ground post-processing
The sequence of activities for a typical burst follows:
1) The Fregate and/or WXM instruments detects a rate increase (a "trigger").
This trigger detection is within 1-5 sec of the actual onset of the burst.
2) An "alert" message is transmitted to the ground (10-20 sec).
3) The S/C_Alert message from any of the Secondary Ground Stations goes
to MIT's HETE_OPS central computer.
There it is forwarded to the GCN computer, where it is received, reformated,
and distributed to those sites wishing that Notice type.
4) The WXM and SXC can produce S/C_Update messages (10-30 sec).
There can be more
than one of these as newer, better positions are calculated on-board
using more data as the burst progresses.
5) A S/C_Last message is produced (within 30-300 sec). It is based on TBD.
6) At some later time (1-5 hrs), when the full data set has been transmitted
to the ground (MIT) through the Primary Ground Stations,
then ground processing may yield an improvement
which is called the Ground_Analysis message.
THE HETE-to-GCN-to-World PROCEDURE:
Like the other missions that contribute GRB positions, GCN receives those
positions messages from the respective mission operations teams, reformats
them into the standard GCN formats, and distributes them to the sites
using the usual distribution methods and filtering. HETE is no different.
Roland Vanderspek (of MIT) has contributed significantly to the software
enabling this new connection to the GCN system.
Samples of the E-mail, Pager, Short-form Pager, & Subject-only distribution methods of the four GCN/HETE Notice types are included below. The format is very similar to the other spacecraft-instrument sources of GRB locations.
Unlike previous mission-specific email formats, the HETE-based email Notices will have a variable number of "TOKEN:value" lines in the messages. This is because the two position-producing instruments (WXM and SXC) may or may not produce and contribute positions to each trigger. The most common scenario will be that WXM detects and images the burst location, but that SCX does not. So there will be fields for the WXM position (the center of the box and the 4 corners of the box), but there will be no such similar set of fields for the SXC. Then next most common scenario will be that both instrument image the burst and so both sets of fields will be present in the email Notice. The next most common scenario will be an SXC-only based message.
Also note that if the intensity is not determined at the time of the Notice (particularly true for the initial Notices), so the intensity field will contain the string "unknown" instead of a numerical value.
The 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 manifested in the various email and pager formats. The S/C_Alert Notice is type=40; S/C_Update Notice is type=41; S/C_Last Notice is type=42; and Ground_Analysis Notice is type=43; (there is also a Test Notice of type=44).
Sites can elect to receive each of the HETE Notice types. There is a separate dis/enable bit for each type. This filtering applies to all the existing distribution methods/media.
The uncertainty in the location will depend on (a) the burst intensity,
(b) its position relative to the instrument's FOV, and
(c) the relative locations and intensities of other sources in the FOV.
The typical error for the S/C_Update Notice is ultimately ~10 arcmin (diameter),
and ~6 arcmin (diameter) for the S/C_Last Notices.
The systematic uncertainty depends on the satellite attitude knowledge
(whether startrackers or gyros or sunsensor are in use) and varies
from 0 arcmin to 4 deg (diameter) in the worst situations.
The errors quoted in the Position Notices includes both the statistical and
the systematic contributions.
In the initial phases of the mission, the position uncertainties will be larger (as large as 4 deg in diameter) because the on-board s/c aspect system will not be fully calibrated. A sizable systematic uncertainty will be added to the error specified in the Notice. There are also contributions to the systematic error from the calibration of the imaging properties of both instruments (WXM & SXC). As the mission progresses these systematic error contributions will decrease as the on-orbit calibrations progress.
Because of the large systematic contributions to the position uncertainty, the positions are listed as a center postion of a circular error "box". But as the systematic contribution decreases (due to on-going calibrations), the positions will be specified as true error rectangles. The four corners of the error box will be listed (along with the center position -- see the Test Notice example below).
To allow sites to "practice" on HETE Notices, there is a HETE_Test Notice. It is type=44. It contains all the same fields in a type=43 HETE_GNDANA Notice. Sites can elect to receive these HETE_Test Notices.
The GCN program generates one of the HETE_Test messages every 210 minutes, so typically only socket sites are interested in this Notice type (~7 times a day can be more than most people want in their e-mail in-boxes or pagers). The RA,Dec locations in these Test messages are selected from a predetermined grid pattern on the sky.
The HETE spacecraft is always looking opposite the Sun (to within 2 degrees), therefore the center of the WXM and SXC FOV is always known. [There are exceptions to this: HETE does offset pointing to avoid the Galactic Center when it would be in the FOV; it offsets when Sco X-1(?) is in the FOV.] It is therfore possible to minimize the slewing time of a telescope by having it looking at the RA,Dec opposite the Sun. Further, the telescope can continuously tile the FOV in a "patrol" mode all night long thereby obtaining images just prior to the burst.
Sites are encouraged to acknowledge HETE and GCN in their publications based on follow-up observations using these GCN/HETE locations.
For further information on this, please contact
George Ricker (for HETE issues),
Roland Vanderspek(for HETE issues), or
Scott Barthelmy (for GCN issues),
or see the
HETE (MIT) web page,
these GCN web pages, and
GCN/HETE GRB table.
Examples of the 3 of the 4 Notice types of the e-mail formats are shown below. The "/////" divider bars are NOT part of the messages. The RA,Dec listed for the POSITION Notices is the HETE-S/C_Update or -S/C_Last RA,Dec position.
Do not take the actual values shown in thee examples as true. While based on trial 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 daemons and/or incoming e-mail filters,
the "Subject" lines for the all notice types are fixed,
and the strings are:
GCN/HETE_POSITION
////////////////////////////S/C_Alert e-mail format//////////////////////////// TITLE: GCN/HETE BURST POSITION NOTICE NOTICE_DATE: Tue 29 May 01 14:38:36 UT NOTICE_TYPE: HETE S/C_Alert TRIGGER_NUM: 666, Seq_Num: 0 GRB_DATE: 12058 TJD; 149 DOY; 01/05/29 GRB_TIME: 52688.41 SOD {14:38:08.41} UT TRIGGER_SOURCE: Trigger on the 2-30 keV band GAMMA_RATE: 0 [cnts/s] on a 0.020 [sec] timescale WXM_SIG/NOISE: 5 sig/noise on a 3.600 [sec] timescale SC_-Z_RA: 246 [deg] SC_-Z_DEC: -21 [deg] SC_LONG: 230 [deg East] SUN_POSTN: 66.54d {+04h 26m 10s} +21.69d {+21d 41' 18"} SUN_DIST: 91.02 [deg] MOON_POSTN: 157.69d {+10h 30m 45s} +14.08d {+14d 05' 03"} MOON_DIST: 174.23 [deg] MOON_ILLUM: 46 [%] COMMENTS: Possible GRB.
/////////////////////////S/C_Update e-mail format////////////////////////////// TITLE: GCN/HETE BURST POSITION NOTICE NOTICE_DATE: Tue 29 May 01 14:40:08 UT NOTICE_TYPE: HETE S/C_Update TRIGGER_NUM: 666, Seq_Num: 1 GRB_DATE: 12058 TJD; 149 DOY; 01/05/29 GRB_TIME: 52688.41 SOD {14:38:08.41} UT TRIGGER_SOURCE: Trigger on the 2-30 keV band GAMMA_RATE: 0 [cnts/s] on a 0.020 [sec] timescale WXM_SIG/NOISE: 6 sig/noise on a 3.600 [sec] timescale SC_-Z_RA: 246 [deg] SC_-Z_DEC: -21 [deg] SC_LONG: 230 [deg East] WXM_CNTR_RA: 264.018d {+17h 36m 04s} (J2000), 264.041d {+17h 36m 10s} (current), 263.195d {+17h 32m 47s} (1950) WXM_CNTR_DEC: -33.426d {-33d 25' 34"} (J2000), -33.427d {-33d 25' 37"} (current), -33.395d {-33d 23' 42"} (1950) WXM_MAX_SIZE: 240.60 [arcmin] diameter WXM_LOC_SN: 5 sig/noise (pt src in image) WXM_IMAGE_SN: X= 4.0 Y= 3.5 [sig/noise] WXM_LC_SN: X= 3.2 Y= 3.7 [sig/noise] SUN_POSTN: 66.54d {+04h 26m 10s} +21.69d {+21d 41' 18"} SUN_DIST: 160.60 [deg] MOON_POSTN: 157.69d {+10h 30m 45s} +14.08d {+14d 05' 03"} MOON_DIST: 111.22 [deg] MOON_ILLUM: 46 [%] GAL_COORDS: 245.07,28.27 [deg] galactic lon,lat of the burst ECL_COORDS: 149.78,-24.67 [deg] ecliptic lon,lat of the burst COMMENTS: Possible GRB. COMMENTS: WXM error box is circular; not rectangular.
/////////////////////////S/C_Last e-mail format//////////////////////////////// TITLE: GCN/HETE BURST POSITION NOTICE NOTICE_DATE: Tue 29 May 01 14:48:25 UT NOTICE_TYPE: HETE S/C_Last TRIGGER_NUM: 666, Seq_Num: 2 GRB_DATE: 12058 TJD; 149 DOY; 01/05/29 GRB_TIME: 52688.41 SOD {14:38:08.41} UT TRIGGER_SOURCE: Trigger on the 2-30 keV band GAMMA_RATE: 0 [cnts/s] on a 0.020 [sec] timescale WXM_SIG/NOISE: 6 sig/noise on a 3.600 [sec] timescale SC_-Z_RA: 246 [deg] SC_-Z_DEC: -21 [deg] SC_LONG: 230 [deg East] WXM_CNTR_RA: 264.018d {+17h 36m 04s} (J2000), 264.041d {+17h 36m 10s} (current), 263.195d {+17h 32m 47s} (1950) WXM_CNTR_DEC: -33.426d {-33d 25' 34"} (J2000), -33.427d {-33d 25' 37"} (current), -33.395d {-33d 23' 42"} (1950) WXM_MAX_SIZE: 240.60 [arcmin] diameter WXM_LOC_SN: 5 sig/noise (pt src in image) WXM_IMAGE_SN: X= 4.0 Y= 3.5 [sig/noise] WXM_LC_SN: X= 3.2 Y= 3.7 [sig/noise] SUN_POSTN: 66.54d {+04h 26m 10s} +21.69d {+21d 41' 18"} SUN_DIST: 160.60 [deg] MOON_POSTN: 157.69d {+10h 30m 45s} +14.08d {+14d 05' 03"} MOON_DIST: 111.22 [deg] MOON_ILLUM: 46.57 [%] GAL_COORDS: 245.07,28.27 [deg] galactic lon,lat of the burst ECL_COORDS: 149.78,-24.67 [deg] ecliptic lon,lat of the burst COMMENTS: Possible GRB. COMMENTS: WXM error box is circular; not rectangular.
///////////////S/C_Update e-mail format that includes SXC data///////////////// TITLE: GCN/HETE BURST POSITION NOTICE NOTICE_DATE: Tue 29 May 01 14:40:08 UT NOTICE_TYPE: HETE S/C_Update TRIGGER_NUM: 666, Seq_Num: 1 GRB_DATE: 12058 TJD; 149 DOY; 01/05/29 GRB_TIME: 52688.41 SOD {14:38:08.41} UT TRIGGER_SOURCE: Trigger on the 2-30 keV band GAMMA_RATE: 0 [cnts/s] on a 0.020 [sec] timescale WXM_SIG/NOISE: 6 sig/noise on a 3.600 [sec] timescale SC_-Z_RA: 246 [deg] SC_-Z_DEC: -21 [deg] SC_LONG: 230 [deg East] WXM_CNTR_RA: 264.018d {+17h 36m 04s} (J2000), 264.041d {+17h 36m 10s} (current), 263.195d {+17h 32m 47s} (1950) WXM_CNTR_DEC: -33.426d {-33d 25' 34"} (J2000), -33.427d {-33d 25' 37"} (current), -33.395d {-33d 23' 42"} (1950) WXM_MAX_SIZE: 240.60 [arcmin] diameter WXM_LOC_SN: 5 sig/noise (pt src in image) WXM_IMAGE_SN: X= 4.0 Y= 3.5 [sig/noise] WXM_LC_SN: X= 3.2 Y= 3.7 [sig/noise] SXC_CNTR_RA: 263.018d {+17h 36m 04s} (J2000), 263.041d {+17h 36m 10s} (current), 262.195d {+17h 32m 47s} (1950) SXC_CNTR_DEC: -32.426d {-32d 25' 34"} (J2000), -32.427d {-32d 25' 37"} (current), -32.395d {-32d 23' 42"} (1950) SXC_MAX_SIZE: 240.00 [arcmin] diameter SXC_LOC_SN: 4 sig/noise (pt src in image) SUN_POSTN: 66.54d {+04h 26m 10s} +21.69d {+21d 41' 18"} SUN_DIST: 160.60 [deg] MOON_POSTN: 157.69d {+10h 30m 45s} +14.08d {+14d 05' 03"} MOON_DIST: 111.22 [deg] MOON_ILLUM: 46 [%] GAL_COORDS: 245.07,28.27 [deg] galactic lon,lat of the burst ECL_COORDS: 149.78,-24.67 [deg] ecliptic lon,lat of the burst COMMENTS: Possible GRB. COMMENTS: WXM error box is circular; not rectangular. COMMENTS: SXC error box is circular; not rectangular.
///////////////GndAna e-mail format/////////////////////////////////////////// TITLE: GCN/HETE BURST POSITION NOTICE NOTICE_DATE: Sun 24 Mar 02 21:18:22 UT NOTICE_TYPE: HETE Ground Analysis TRIGGER_NUM: 666, Seq_Num: 5 GRB_DATE: 12050 TJD; 141 DOY; 01/05/21 GRB_TIME: 65731.42 SOD {18:15:31.42} UT TRIGGER_SOURCE: Trigger on the 6-120 keV band. GAMMA_RATE: 428 [cnts/s] on a 1.300 [sec] timescale SC_-Z_RA: 175 [deg] SC_-Z_DEC: 1 [deg] SC_LONG: 230 [deg East] WXM_CNTR_RA: 143.283d {+09h 33m 08s} (J2000), 143.300d {+09h 33m 12s} (current), 142.677d {+09h 30m 42s} (1950) WXM_CNTR_DEC: -11.594d {-11d 35' 38"} (J2000), -11.600d {-11d 36' 01"} (current), -11.372d {-11d 22' 18"} (1950) WXM_CORNER1: 143.4740 -11.3180 [deg] WXM_CORNER2: 143.5230 -11.7680 [deg] WXM_CORNER3: 143.0430 -11.4200 [deg] WXM_CORNER4: 143.0930 -11.8710 [deg] WXM_MAX_SIZE: 36.00 [arcmin] diameter WXM_LOC_SN: 5 sig/noise (pt src in image) WXM_IMAGE_SN: X= 4.0 Y= 3.5 [sig/noise] WXM_LC_SN: X= 3.2 Y= 3.7 [sig/noise] SUN_POSTN: 58.60d {+03h 54m 25s} +20.31d {+20d 18' 28"} SUN_DIST: 89.13 [deg] MOON_POSTN: 42.48d {+02h 49m 56s} +11.96d {+11d 57' 38"} MOON_DIST: 102.80 [deg] MOON_ILLUM: 2 [%] GAL_COORDS: 245.07,28.27 [deg] galactic lon,lat of the burst ECL_COORDS: 149.78,-24.67 [deg] ecliptic lon,lat of the burst COMMENTS: Definite GRB. COMMENTS: Burst_Validity flag is true. COMMENTS: WXM error box is circular; not rectangular. COMMENTS: WXM data refined since S/C_Last Notice. /////////////////////////////////////////////////////////////////////////////// Variations on the above cases: The "TRIGGER_SOUCE" line can contain 4 different strings: a) Trigger on the 1.5-12 keV band b) Trigger on the 2-30 keV band c) Trigger on the 6-120 keV band d) Trigger on the 25-400 keV band ///////////////////////////////////////////////////////////////////////////////
Examples of the four types of the (regular) pager formats 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.
////////////////////////////////////////////////////////////////////////////// GCN/HETE S/C_Alert Trig=1531 Seq=0 Time: 14:38:08.41 ////////////////////////////////////////////////////////////////////////////// GCN/HETE S/C_Update Trig=1531 Seq=1 WXM: RA=264.041d DEC=-33.427d Time: 14:38:08.41 ////////////////////////////////////////////////////////////////////////////// GCN/HETE S/C_Last Trig=1531 Seq=2 WXM: RA=264.041d DEC=-33.427d Time: 14:38:08.41 ////////////////////////////////////////////////////////////////////////////// GCN/HETE GndAna Trig=1531 Seq=3 WXM: RA=264.053d DEC=-33.434d Time: 14:38:08.41 //////////////////////////////////////////////////////////////////////////////
Examples of the four types 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.
////////////////////////////////////////////////////////////////////////////// HETE S/C_Alert Trig=1531 Seq=0 Time: 14:38:08.41 ////////////////////////////////////////////////////////////////////////////// HETE S/C_Update RA=263.195 DEC=+79.310d ////////////////////////////////////////////////////////////////////////////// HETE S/C_Last RA=263.155 DEC=+79.330d ////////////////////////////////////////////////////////////////////////////// HETE GndAna RA=263.187 DEC=+79.304 //////////////////////////////////////////////////////////////////////////////
There are two variations of the Subject-only format: decimal degrees and RA=hh:mm:ss Dec=DDdMMmSSs format. The two variations are shown below:
////////////////////////////////////////////////////////////////////////////// HETE S/C_Alert Tr=1531 S=0 Tm=14:38:08.41 [same for both forms] ////////////////////////////////////////////////////////////////////////////// HETE S/C_Update RA=100.931 DEC=+79.310d [an example of dec deg] ////////////////////////////////////////////////////////////////////////////// HETE S/C_Last RA=06h43m28.1 DEC=79d20m13.2s [an example of hh:mm:ss] ////////////////////////////////////////////////////////////////////////////// HETE GndAna RA=06h43m28.1 DEC=79d20m13.2s [an example of hh:mm:ss] //////////////////////////////////////////////////////////////////////////////
Here is an example of the HETE_Test Notice (e_mail format). It also contains the "TOKEN:value" lines for the corners of both error boxes for those messages that have been localized to a rectangle rather than a circle.
////////////////////////////////////////////////////////////////////////////// TITLE: GCN/HETE BURST POSITION NOTICE NOTICE_DATE: Wed 30 May 01 16:48:43 UT NOTICE_TYPE: HETE Test TRIGGER_NUM: 5, Seq_Num: 1 GRB_DATE: 12059 TJD; 150 DOY; 01/05/30 GRB_TIME: 60521.00 SOD {16:48:41.00} UT TRIGGER_SOURCE: Trigger on the 2-30 keV band GAMMA_RATE: 1000 [cnts/s] on a 1.234 [sec] timescale WXM_SIG/NOISE: 1 sig/noise on a 4.234 [sec] timescale SXC_RATE: 101 [cnts/s] SC_-Z_RA: 257 [deg] SC_-Z_DEC: 2 [deg] WXM_CNTR_RA: 144.000d {+09h 35m 60s} (J2000), 144.021d {+09h 36m 05s} (current), 143.243d {+09h 32m 58s} (1950) WXM_CNTR_DEC: +35.000d {+35d 00' 00"} (J2000), +34.994d {+34d 59' 37"} (current), +35.224d {+35d 13' 27"} (1950) WXM_CORNER1: 144.0500 35.0500 [deg] WXM_CORNER2: 143.9500 35.0500 [deg] WXM_CORNER3: 143.9500 34.9500 [deg] WXM_CORNER4: 144.0500 34.9500 [deg] WXM_MAX_SIZE: 0.05 [arcmin] diameter WXM_LOC_SN: 5 sig/noise (pt src in image) WXM_IMAGE_SN: X= 4.0 Y= 3.5 [sig/noise] WXM_LC_SN: X= 3.2 Y= 3.7 [sig/noise] SXC_CNTR_RA: 144.000d {+09h 35m 60s} (J2000), 144.021d {+09h 36m 05s} (current), 143.243d {+09h 32m 58s} (1950) SXC_CNTR_DEC: +35.000d {+35d 00' 00"} (J2000), +34.994d {+34d 59' 37"} (current), +35.224d {+35d 13' 27"} (1950) SXC_CORNER1: 144.0100 35.0100 [deg] SXC_CORNER2: 143.9900 35.0100 [deg] SXC_CORNER3: 143.9900 34.9900 [deg] SXC_CORNER4: 144.0100 34.9900 [deg] SXC_MAX_SIZE: 0.12 [arcmin] diameter SXC_LOC_SN: 8 sig/noise (pt src in image) SUN_POSTN: 67.66d {+04h 30m 37s} +21.85d {+21d 51' 01"} SUN_DIST: 66.88 [deg] MOON_POSTN: 172.38d {+11h 29m 32s} +8.75d {+08d 44' 46"} MOON_DIST: 36.90 [deg] MOON_ILLUM: 59 [%] GAL_COORDS: 245.07,28.27 [deg] galactic lon,lat of the burst ECL_COORDS: 149.78,-24.67 [deg] ecliptic lon,lat of the burst COMMENTS: ARTIFICIAL BURST TRIGGER! COMMENTS: Definite GRB. COMMENTS: COMMENTS: This is a TEST Notice. COMMENTS: And for this TEST Notice, most of the flags COMMENTS: have been turned on to show most of the fields. //////////////////////////////////////////////////////////////////////////////