ctio.immatch
kanaan wrote on Apr 04, 2008
Hi folks,
I am getting:
"Bad file name template descriptor "
when I leave ctio.immatch
immatch seems to run fine, I am running it interactively and it is all fine.
I R A F
Image Reduction and Analysis Facility
PACKAGE = ctio
TASK = immatch
images = hawa0001.fits Input images
referenc= hawa0002.fits Reference images
output = lixo987 Output file
(section= [1:512,150:500]) Image section
(xmax = INDEF) Maximum shift in column direction
(ymax = INDEF) Maximum shift in line direction
(width = 5.) Centering width
(interac= yes) Run interactively ?
(imshift= no) Generate script that runs IMSHIFT ?
(graphic= stdgraph) Graphics output device
(cursor = ) Graphics cursor input
(mode = al)
and this is my iraf:
NOAO PC-IRAF Revision 2.12.2a-EXPORT Wed Jul 14 20:45:34 MST 2004
This is the EXPORT version of PC-IRAF V2.12 supporting most PC systems.
any thoughts?
Antonio
I am getting:
"Bad file name template descriptor "
when I leave ctio.immatch
immatch seems to run fine, I am running it interactively and it is all fine.
I R A F
Image Reduction and Analysis Facility
PACKAGE = ctio
TASK = immatch
images = hawa0001.fits Input images
referenc= hawa0002.fits Reference images
output = lixo987 Output file
(section= [1:512,150:500]) Image section
(xmax = INDEF) Maximum shift in column direction
(ymax = INDEF) Maximum shift in line direction
(width = 5.) Centering width
(interac= yes) Run interactively ?
(imshift= no) Generate script that runs IMSHIFT ?
(graphic= stdgraph) Graphics output device
(cursor = ) Graphics cursor input
(mode = al)
and this is my iraf:
NOAO PC-IRAF Revision 2.12.2a-EXPORT Wed Jul 14 20:45:34 MST 2004
This is the EXPORT version of PC-IRAF V2.12 supporting most PC systems.
any thoughts?
Antonio
Mike Fitzpatrick wrote on Apr 04, 2008
Antonio,
That message is coming from the part of the system that handles file lists, since it happening at the end the I suspect somehow the list pointer was corrupted. I looked at the code and it doesn't appear to be being freed twice and I couldn't reproduce the problem quickly here.
As an alternative you might look at tasks in the IMAGES.IMMATCH package that serve the same purpose, e.g. WREGISTER, XREGISTER, etc.
Cheers,
-Mike
That message is coming from the part of the system that handles file lists, since it happening at the end the I suspect somehow the list pointer was corrupted. I looked at the code and it doesn't appear to be being freed twice and I couldn't reproduce the problem quickly here.
As an alternative you might look at tasks in the IMAGES.IMMATCH package that serve the same purpose, e.g. WREGISTER, XREGISTER, etc.
Cheers,
-Mike
kanaan wrote on Apr 04, 2008
Hey Mike,
weird, I changed the section and it started working again. Somehow it doesn't like to get close to the edge. I was not off the image or anything ([1:512,150:500]):
ecl> imhead hawa20080324ec14-1414
hawa20080324ec14-1414[512,512][real]: EC14012
now I am doing: [100:500,150:500] and it runs fine.
the weird thing is the error message which leads one to think there is some problem with filenames, not with the image section.
well, problem has been sent away, not really solved though :-)
thanks for the help
Antonio
weird, I changed the section and it started working again. Somehow it doesn't like to get close to the edge. I was not off the image or anything ([1:512,150:500]):
ecl> imhead hawa20080324ec14-1414
hawa20080324ec14-1414[512,512][real]: EC14012
now I am doing: [100:500,150:500] and it runs fine.
the weird thing is the error message which leads one to think there is some problem with filenames, not with the image section.
well, problem has been sent away, not really solved though :-)
thanks for the help
Antonio
Last post on Apr 04, 2008