[vsnet-grb 89344] GCN/SWIFT_FOM_OBSERVE

[Bacodine]

TITLE:           GCN/SWIFT NOTICE
NOTICE_DATE:     Fri 02 Jan 09 21:06:41 UT
NOTICE_TYPE:     Swift-FOM Will_Observe
TRIGGER_NUM:     338895,   Seg_Num: 1
GRB_RA:          128.242d {+08h 32m 58s} (J2000),
                 128.383d {+08h 33m 32s} (current),
                 127.458d {+08h 29m 50s} (1950)
GRB_DEC:         +33.114d {+33d 06' 51"} (J2000),
                 +33.083d {+33d 04' 59"} (current),
                 +33.285d {+33d 17' 06"} (1950)
GRB_DATE:        14833 TJD;     2 DOY;   09/01/02
GRB_TIME:        10545.00 SOD {02:55:45.00} UT
TRIGGER_INDEX:   0
RATE_SIGNIF:     0.00 [sigma]
IMAGE_SIGNIF:    0.00 [sigma]
FLAGS:           0x3
MERIT:           86.00
SUN_POSTN:       283.70d {+18h 54m 49s}  -22.84d {-22d 50' 21"}
SUN_DIST:        156.00 [deg]   Sun_angle= 10.4 [hr] (West of Sun)
MOON_POSTN:      352.30d {+23h 29m 11s}   +0.71d {+00d 42' 45"}
MOON_DIST:       126.64 [deg]
MOON_ILLUM:      34 [%]
GAL_COORDS:      189.85, 34.66 [deg] galactic lon,lat of the burst (or transient)
ECL_COORDS:      122.28, 13.86 [deg] ecliptic lon,lat of the burst (or transient)
COMMENTS:        SWIFT Figure-of-Merit decision.  
COMMENTS:        This Notice is generated as a result of an uploaded TOO on an old GRB -- this is not a newly detected burst.  
COMMENTS:        As a result of this TOO, the TRIG_INDEX, and RATE/IMAGE_SIGNIF fields are not valid!  
COMMENTS:        And sometimes the GRB_DATE/TIME fields are not valid!  
COMMENTS:        This was of sufficient merit to become the new Automated Target;  
COMMENTS:        but if the Current PPT has a greater merit, then we will not request a slew.  
COMMENTS:        FOM will request the s/c to slew.  
COMMENTS:        The S/C has yet to make its decision about safe to slew or not.  
COMMENTS:        This does not match any source in the ground catalog.