[vsnet-grb 41156] GCN/SWIFT_FOM_OBSERVE

[Bacodine]

TITLE:           GCN/SWIFT NOTICE
NOTICE_DATE:     Tue 20 Feb 07 18:15:56 UT
NOTICE_TYPE:     Swift-FOM Will_Observe
TRIGGER_NUM:     261299,   Seg_Num: 1
GRB_RA:           34.776d {+02h 19m 06s} (J2000),
                  34.926d {+02h 19m 42s} (current),
                  33.734d {+02h 14m 56s} (1950)
GRB_DEC:         +68.805d {+68d 48' 18"} (J2000),
                 +68.838d {+68d 50' 16"} (current),
                 +68.575d {+68d 34' 30"} (1950)
GRB_DATE:        14151 TJD;    51 DOY;   07/02/20
GRB_TIME:        17038.22 SOD {04:43:58.22} UT
TRIGGER_INDEX:   0
RATE_SIGNIF:     0.00 [sigma]
IMAGE_SIGNIF:    0.00 [sigma]
FLAGS:           0x3
MERIT:           99.00
SUN_POSTN:       333.73d {+22h 14m 56s}  -10.86d {-10d 51' 35"}
SUN_DIST:         90.28 [deg]   Sun_angle= -4.1 [hr] (East of Sun)
MOON_POSTN:       12.13d {+00h 48m 31s}   +7.76d {+07d 45' 50"}
MOON_DIST:        62.89 [deg]
MOON_ILLUM:      13 [%]
GAL_COORDS:      130.75,  7.27 [deg] galactic lon,lat of the burst (or transient)
ECL_COORDS:       62.07, 50.66 [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.