[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: email@example.com
- Subject: Re: idea
- From: Glenn Gombert <firstname.lastname@example.org>
- Date: Tue, 26 Aug 1997 20:52:52 -0400
- Old-Return-Path: <email@example.com>
- Resent-Date: Tue, 26 Aug 1997 20:58:31 -0400 (EDT)
- Resent-From: firstname.lastname@example.org
- Resent-Message-ID: <"msJGOD.A.ESG.5k3A0"@kani.wwa.com>
- Resent-Sender: email@example.com
SExtractor will work with just about *any* FITS format image. If you
want to use the FITS header parameters to compute astrometric (RA and DEC)
parameters the key words in the FITS header must be setup & caculated
accordingly. The Univeristy of IOWA's ATFTools kit program "wcs.exe" can be
used to compute the WCS parameters for a particular image based on a
"pattern match" with the HGSC catalog.
I have generated several TASS Techical Notes on the subject....
At 05:10 PM 8/26/97 -0700, you wrote:
>> Benoit suggested that others outside of the mark III sites might be able
>> to contribute to the TASS survey. Tom and others agreed, and I concur
>> as well. Nice idea!
>> Like Mike G. said, the software has been geared toward the mark III
>> drift scan cameras, and would require some modification for other types.
>Yes, "other types" including the MkIV.
>With the MkIV on its way maybe now is the time to make sure our
>software looks inside the FITS headers for required data. With
>the MkIV there is conciderable operational flexability. Exposure
>lenght need not be constant frame to frame, The focal lenght
>will not be a constant from camera to camera. Software that
>can handle a generalized MkIV should also handle an ST-7.
>So it is clear the software will need to become smarter just
>to handle the MkIV. While we are making it so why not look
>down the road a little farther and think about ST-7s and the like?
> firstname.lastname@example.org Voice: 818-351-0089 X127
> Logicon RDA, Pasadena California Fax: 818-351-0699
Glenn Gombert <email@example.com>