Brian,
In the past we would just delete Teleseisms, but there is a use for good impulsive teleseisms to do polarity checks on our network stations, in the past 4 years we began saving them for that purpose.
We do not have another procedure to save or look at teleseisms.
And yes Paul is correct that telestifle only quiets the alarm response but take no action on the misslocated event itself. The Duty seismologist will either "cancel" through the DRP ( which will delete it off the web" or leave it to the Jiggle timers to deal with if it did not make it to the "recent event webpage" as a misslocated event.
So here are the two ways we take care of teleseisms with the Jiggle staff...
- If we have a teleseism as a result of a network trigger then we just set the GTYPE to "T" which sets the ETPYE automatically to "earthquake" , the location has no LAT/LON or depth to begin with and the "bogus flag" is automatically set because it is a network trigger. So after that we just "finalize" with a remark stating the NEIC location/mag and if it a good candidate for polarity checks.
- If we have a teleseism that was misslocated with "binder" as a local event, then we manually set by hitting the "clear" button. This clears the LAT/LON and Depth which sets the "bogus location flag". Again we set the GTYPE to "T" and finalize. We don't even bother to clear the binder picks as a time saver.
If that does not clear the event off of the recent events webpage...
- Delete the event in Jiggle
- wait for the event to be deleted off the web.
- then "undelete" the same event in Jiggle and check to see that the GTYPE and ETYPE are "earthquake" and "T" respectively and that the LAT/LON are cleared.
- re- finalize the same event. It will be set back to COMCAT but be off the
recent events webpage.