From hlm Wed Apr 26 11:53 PDT 2000
Received: from castor.ipac.caltech.edu (castor [134.4.10.10]) 
	  by bigbang.ipac.caltech.edu (8.8.8/8.6.4)
	  with ESMTP id LAA00499; Wed, 26 Apr 2000 11:53:00 -0700 (PDT)
From: Howard McCallon <hlm>

Gene-

Attached is a brief description of how the solos are generated. This is
from the portion of PFPrep originally written by John and I can't recall
whether magnitudes are compared when generating merge groups.  I don't
see anything in the namelist specifying dmag tolerances, so I'm assuming
they're not. John, any corrections or additions you may have are welcome.

Regards,

Howard

%%%%%%%%%%%%%%

The "solo" file (pos10) is generated by PFPrep and contains one entry
for each single frame detection found to be part of a single-frame event.
The primary task of PFPrep is to identify frame detections belonging
to a common real source and tag these detections with a "merge group"
number for later use by PosFrm. This is accomplished by first placing all frames
from all three bands into their respective relative positions using apriori
knowledge and then doing position (and magnitude?) matching. Single-frame
detections not found to have matching detections in the same band on different
frames are written to the "solo" file.

From: Howard McCallon <hlm>

Gene-

Window size is 3.0 asec.

Regards,

Howard

%%%%%%%%%%%%%%%%
> 
> Looks like no mag threshold in PFPrep, but how about the confirmation criteria?
> Window size, etc.
> 
> thanks, gene