[vsnet-grb 104983] GCN/SWIFT_FOM_OBSERVE

[Bacodine]

TITLE:           GCN/SWIFT NOTICE
NOTICE_DATE:     Wed 12 Aug 09 08:41:27 UT
NOTICE_TYPE:     Swift-FOM Will_Observe
TRIGGER_NUM:     359711,   Seg_Num: 1
GRB_RA:          353.201d {+23h 32m 48s} (J2000),
                 353.325d {+23h 33m 18s} (current),
                 352.554d {+23h 30m 13s} (1950)
GRB_DEC:         -10.604d {-10d 36' 12"} (J2000),
                 -10.551d {-10d 33' 01"} (current),
                 -10.880d {-10d 52' 47"} (1950)
GRB_DATE:        15055 TJD;   224 DOY;   09/08/12
GRB_TIME:        21723.00 SOD {06:02:03.00} UT
TRIGGER_INDEX:   0
RATE_SIGNIF:     0.00 [sigma]
IMAGE_SIGNIF:    0.00 [sigma]
FLAGS:           0x3
MERIT:           76.00
SUN_POSTN:       142.19d {+09h 28m 46s}  +14.88d {+14d 53' 01"}
SUN_DIST:        149.35 [deg]   Sun_angle= 9.9 [hr] (West of Sun)
MOON_POSTN:       27.98d {+01h 51m 56s}  +17.15d {+17d 08' 55"}
MOON_DIST:        44.05 [deg]
MOON_ILLUM:      65 [%]
GAL_COORDS:       70.93,-65.19 [deg] galactic lon,lat of the burst (or transient)
ECL_COORDS:      349.55, -7.04 [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.