Welcome to iraf.net Friday, May 17 2024 @ 10:23 AM GMT
| tiraf |
05/28/2009 02:38PM (Read 1656 times)
|
|
|
Status: offline
Registered: 05/28/2009
Posts: 2
|
I am reducing CTIO Mosaic data with the most recent WCS solution files (from 2007).
When I "MSCCMATCH" the individual frames I am left with significant residuals (up to 1 pixel in a wave-like pattern) in the y direction (delta_y vs. y, or the "s" key).
All other fits are good with low RMS ("x","y","r").Is there a way to create my own WCS solution? I have a couple fairly crowded fields that might be used as reference frames.Thanks!
|
| |
|
|
| fitz |
|
05/28/2009 02:38PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
Frank may also reply, but you might also have a look at his doc on doing this: https://iraf.net/irafdocs/astrom.php
|
| |
|
|
| tiraf |
|
05/28/2009 02:38PM
|
|
|
Status: offline
Registered: 05/28/2009
Posts: 2
|
Thanks, this is very helpful. However, I can't seem to find msctpeak in my v2.12.2a installation. mscfinder is a task (with no parameter file) rather than a sub-package.Do you know what these tasks evolved to in newer versions of IRAF? Are they available again in 2.13, 2.14?EDIT:
both the mscfinder package and the msctpeak task work just fine under v2.12, I just apparently had a conflict with the ctio package.Thanks!
|
| |
|
|
| |
|
| Content generated in: 0.09 seconds |
|
New Topic
Post Reply
Creating a new WCS solution for Mosaic
Quote
