Thanks ! That indeed seems to have been the problem. I think I knew that fact at
Quote by: valdesHi Nelson,
Your confusion happens occasionally. It looks like you copied apDOME to apapref_DOME_2x3 and there is not actually a parent image apref_DOME_2x3. You can do what you want to do but you need to edit apapref_DOME_2x3 and then replace all the instances of DOME with apref_DOME_2x3. When you say you want the reference it not only is used to find the database file with that name (with the extra "ap" prefix) but also to select the "records" in the database for that name.
I don't know about too much heat since I personally don't mind the summers and right now we are really comfortable! But it does seem like your winter is being rather brutal.
Best wishes,
Frank
On Feb 18, 2014, at 3:24 PM, Nelson Caldwell wrote:
Hi Frank,
thanks for taking my question, as they say in the call-in shows.
iraf version is:
NOAO/IRAFNET PC-IRAF Revision 2.14.1 Mon Sep 15 10:12:05 MST 2008
And, I include the two aperture files. Here again is the command
aprecenter DOME apertur=1-240 referen=apref_DOME_2x3
interac- find- recente+ resize- edit- line=INDEF nsum=50
aprecen='""' npeaks=INDEF shift=no
Jessica Mink has suggested that the problem is the apref_DOME_2x3 file
has a different number of apertures (240) than the apDOME file (244).
I haven't had a chance to verify that since I wrote the iraf.net query, so
if you want to hold off on looking at this question till I do have some time,
that's ok with me!
Hope you are doing well - you all in Tucson have too much heat, and we here in Boston
have too much snow!
thanks a bunch,
Nelson