[vsnet-grb 69092] GCN/SWIFT_FOM_OBSERVE

[Bacodine]

TITLE:           GCN/SWIFT NOTICE
NOTICE_DATE:     Wed 19 Mar 08 21:06:04 UT
NOTICE_TYPE:     Swift-FOM Will_Observe
TRIGGER_NUM:     306793,   Seg_Num: 1
GRB_RA:           99.473d {+06h 37m 53s} (J2000),
                  99.598d {+06h 38m 24s} (current),
                  98.710d {+06h 34m 50s} (1950)
GRB_DEC:         +23.960d {+23d 57' 36"} (J2000),
                 +23.952d {+23d 57' 09"} (current),
                 +24.004d {+24d 00' 14"} (1950)
GRB_DATE:        14544 TJD;    79 DOY;   08/03/19
GRB_TIME:        61506.34 SOD {17:05:06.34} UT
TRIGGER_INDEX:   0
RATE_SIGNIF:     0.00 [sigma]
IMAGE_SIGNIF:    0.00 [sigma]
FLAGS:           0x3
MERIT:           90.00
SUN_POSTN:       359.66d {+23h 58m 39s}   -0.15d {-00d 08' 44"}
SUN_DIST:         99.13 [deg]   Sun_angle= -6.7 [hr] (East of Sun)
MOON_POSTN:      158.64d {+10h 34m 32s}   +7.92d {+07d 55' 10"}
MOON_DIST:        58.56 [deg]
MOON_ILLUM:      96 [%]
GAL_COORDS:      189.99,  7.88 [deg] galactic lon,lat of the burst (or transient)
ECL_COORDS:       98.65,  0.80 [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.