TO:  All GCN Notice recipient sites                    29 Jun 06
RE:  XRT_POS and UVOT_POS now correlated with BAT_POS

INTRO / SUMMARY
The XRT_POSITION and UVOT_POSITION Notices are now identified
if they are associated with a BAT_POSITION Notice
that was in the BAT Ground Catalog of known sources.

IN THE PAST:
In the past if BAT detected an outburst from a known
and otherwise steady-state source, then the BAT_POSITION Notice
was properly identified as such (ie it went out with a
Transient designation instead of a GRB designation).
However, the XRT_POSITION and UVOT_POSITION Notices went out
to the world without any such non-burst designation.
This lack of a non-burst designation could have been (was) a problem
for sites only receiving (or otherwise only paying attention to)
the XRT & UVOT Position Notices.  They did not know that the
XRT_Position notice was for a follow-up on a source that BAT determined
was not a GRB.  Now, this information is carried over from the
BAT Notices into the XRT and UVOT Position Notices.

HOW INDICATED:
In the socket packets, there is a flag bit set in the TRIGGER_ID field.
See   http://gcn.gsfc.nasa.gov/gcn/sock_pkt_def_doc.html .
In the full-format email Notices, there is a COMMENT line
which says, to the effect, "this is a source in the BAT catalog".

Sincerely,
Scott