[vsnet-grb 93494] GCN/SWIFT_FOM_OBSERVE

[Bacodine]

TITLE:           GCN/SWIFT NOTICE
NOTICE_DATE:     Sat 07 Mar 09 21:49:28 UT
NOTICE_TYPE:     Swift-FOM Will_Observe
TRIGGER_NUM:     345551,   Seg_Num: 1
GRB_RA:          244.994d {+16h 19m 58s} (J2000),
                 245.137d {+16h 20m 33s} (current),
                 244.216d {+16h 16m 52s} (1950)
GRB_DEC:         -28.634d {-28d 38' 01"} (J2000),
                 -28.655d {-28d 39' 18"} (current),
                 -28.514d {-28d 30' 51"} (1950)
GRB_DATE:        14897 TJD;    66 DOY;   09/03/07
GRB_TIME:        13592.44 SOD {03:46:32.44} UT
TRIGGER_INDEX:   0
RATE_SIGNIF:     0.00 [sigma]
IMAGE_SIGNIF:    0.00 [sigma]
FLAGS:           0x3
MERIT:           98.00
SUN_POSTN:       348.46d {+23h 13m 51s}   -4.96d {-04d 57' 19"}
SUN_DIST:         99.21 [deg]   Sun_angle= 6.9 [hr] (West of Sun)
MOON_POSTN:      127.62d {+08h 30m 29s}  +19.16d {+19d 09' 53"}
MOON_DIST:       122.71 [deg]
MOON_ILLUM:      87 [%]
GAL_COORDS:      348.80, 15.13 [deg] galactic lon,lat of the burst (or transient)
ECL_COORDS:      248.05, -7.08 [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.