RE: New Data Sets

["Creager, Robert S" <CreagRS@LOUISVILLE.STORTEK.COM>]

Hey folks,

At http://www.carolinecreager.com/tass are 5 files that could, with minor
work, be plugged into Michael's pipeline to solve problem #1 (he says boldly
without looking at Michael's pipeline).

The files, and their order of use and descriptsions are:

tassiv_reduce.cfg - A configuration file which maintains configuration
information for my reduction pipeline.  Would need changes to mirror the
columlar layour of the raw star lists.  It's designed to do this.  Of utmost
importance are the ra/dec, x/y and magnitude columns.  If these are not
available, trouble.  The x/y columns are used when I cannot get a match of
one frame to the catalog.

FITS.pm - A module which reads fits files and gives information required.  A
drop in replacement could be contructed which reads Michael's image
information file.

doRaw.pl - The control routine.  This script calls matchStars.pl on each
image, grouping matching pairs of them.  If both images match to the
catalog, no more work needs to be done.  If one frame matches to a catalog
but not the other, the frames are matched to each other using x/y as the
location, then a x/y transformation is applied to the unmatching star list,
then the ra/dec transformation is applied from the other frame.  Note that
the original x/y location are not modified in the star lists.  I
re-implemented Michael's apply_match program in perl as DAOPHOT produces 33
columns which I am currently keeping all of, and apply_match was limited to
something around 20.  It's built into doRaw.pl currently, but could/should
be moved into it's own script/module.  The only change needed here would be
to modify the extensions of the output files, which I'd been debating
putting into the config file anyway.  Column ordering/which to keep are
controlled by the config file.

matchStars.pl - Uses Michael's match program, and the script findStars.pl,
to search a range (configured in the config file) of ra/dec for matching.
Depending on the parameters, it will refine
that search to get the best center possible.

findStars.pl - A skanky perl script which uses my dB setup to find the stars
required to match the entire search range.  This script just put's out data
to stdout, which matchStars.pl grabs and then uses internally.  Could easily
be modified to read a flat file (or another dB) and return that data.

There you have it.  At least some ideas if no one wants to use these scripts
directly.  If anyone is interested in using them directly, I'd like to be
kept in the loop as I see no reason for there to be two sets of scripts, one
which works with Michael's pipeline and one that works with mine.  I've been
contemplating using my scripts around Michael's star reducing core, but have
not determined if that would be feasable/possible yet.  I don't feel these
scripts are in 'final' form, as the performance is OK, and some code is not
documented or scrungy.  I was going to get to that when I had something that
worked end to end (no, really)...

Can anyone answer the implicit question above?  Is there any functionality
in Michael's pipeline which will take in a dark/flat adjusted fits image and
spit out a list of stars?  One that would not depend on any other
info/config files/etc...?

Luck,
Rob

> -----Original Message-----
> 
> 1)  The star matching program fails.  This almost always 
> happens for the I 
> image so it is not due to a bad position in the fits header.  
> Sometimes 
> more frames will pass and generate .ast files if one fusses 
> with the RA and 
> Decl. position.  But it does not help very much.  A data set 
> will be made 
> available with good and bad runs from the set below.  Ask for 
> Data Set 21 
> if you want to work on this problem.  I am betting that this 
> has something 
> to do with the V focus being sharper than the I focus.
>