Daofind - error message
Lientjie wrote on Aug 28, 2008
Hi there!
I am working on diffuse images of star-forming regions and previously used the Daofind task to extract a catalog of my sources. I repeated everything the way I previously did it but suddenly keep getting the error message
"ERROR: CLGWRD: No match, or ambiguous abbreviation".
I searched through all my parameter lists for the word "CLGWRD" but cannot find it. I also made sure that the image I'm using does exist and that I am in the right directory (in case the "no match" message could have something to do with that).
Does anybody know what on earth this message mean? Please help!
Thanks!
Lientjie
I am working on diffuse images of star-forming regions and previously used the Daofind task to extract a catalog of my sources. I repeated everything the way I previously did it but suddenly keep getting the error message
"ERROR: CLGWRD: No match, or ambiguous abbreviation".
I searched through all my parameter lists for the word "CLGWRD" but cannot find it. I also made sure that the image I'm using does exist and that I am in the right directory (in case the "no match" message could have something to do with that).
Does anybody know what on earth this message mean? Please help!
Thanks!
Lientjie
Mike Fitzpatrick wrote on Aug 28, 2008
CLGWRD is an SPP procedure that gets a keyword parameter, i.e. one that can have multiple values and is checked against a dictionary of legal values. In the case of DAOFIND it is used for the 'boundary' and 'wcsout' parameters specifically.
Chances are this is a typo of some kind and simply unlearning the task and starting from fresh parameter will fix it, you might also want to unlearn the package itself or any psets you might have changed.
Cheers,
-Mike
Chances are this is a typo of some kind and simply unlearning the task and starting from fresh parameter will fix it, you might also want to unlearn the package itself or any psets you might have changed.
Cheers,
-Mike
Lientjie wrote on Aug 28, 2008
thanks a lot! it worked :lol:
sbursic wrote on Aug 28, 2008
Hi,
I have the exact same error when I try to run a script in IRAF.
I had just moments before had no problems with previous scripts in IRAF, but for some reason now when I type cl < scriptname.cl I get this error:
ERROR: CLGWRD: No match, or ambiguous abbreviation (chebychev)
called as: `cl (gcur=hedit2.cl)'
I'm trying to do multiple overscan/bias reductions on several images in noao/imred/ccdred/ccdproc.
I've tried to unlearn mkscript, cl, noao,imred,ccdred,ccdproc,hedit. (Any previous task I was using before.) Any clues on why this is happening?
Also, I tried recreating the script and still same error.
Additionally, I just tried to run CCDPROC without using any scripts and I got the same error. I tried to unlearn it again without any success.
Thanks,
Shelly
I have the exact same error when I try to run a script in IRAF.
I had just moments before had no problems with previous scripts in IRAF, but for some reason now when I type cl < scriptname.cl I get this error:
ERROR: CLGWRD: No match, or ambiguous abbreviation (chebychev)
called as: `cl (gcur=hedit2.cl)'
I'm trying to do multiple overscan/bias reductions on several images in noao/imred/ccdred/ccdproc.
I've tried to unlearn mkscript, cl, noao,imred,ccdred,ccdproc,hedit. (Any previous task I was using before.) Any clues on why this is happening?
Also, I tried recreating the script and still same error.
Additionally, I just tried to run CCDPROC without using any scripts and I got the same error. I tried to unlearn it again without any success.
Thanks,
Shelly
Mike Fitzpatrick wrote on Aug 28, 2008
If you do a new MKIRAF in say /tmp and login from there, you won't have any saved parameters that may be corrupting the values. The error basically means a parameter query can't be resolved because of an ambiguity, this might be coming from a script task calling some other task you haven't explicitly unlearned.
Otherwise, type 'd_trace' before running your script and you'll be able to determine which command is causing the error. Without seeing the hedit2.cl script I can't comment on what might be querying for the param.
-Mike
Otherwise, type 'd_trace' before running your script and you'll be able to determine which command is causing the error. Without seeing the hedit2.cl script I can't comment on what might be querying for the param.
-Mike
sbursic wrote on Aug 28, 2008
Mike,
Thank you for your reply. I'm a bit leery to make a whole new iraf. Wouldn't this cause problems with my path?
I tried typing trace_d and IRAF doesn't recognize that as a task.
Here is what my hedit2.cl script looks like:
hedit ("iSDSS537trim.fits[2]",
"DATASEC", "[1:2039,1:4073]", add=no, addonly=no, delete=no, verify=no,
show=yes, update=yes)
hedit ("iSDSS537trim.fits[3]",
"DATASEC", "[1:2039,1:4073]", add=no, addonly=no, delete=no, verify=no,
show=yes, update=yes)
ect... It's just changing the header of the star files. This script is not one I am trying to use now. Also, when I did unlearn on ccdproc it changed the error message slightly in that it got ride of the (hedit2.cl) completely.
The script I'm trying to use now is:
ccdproc ("@izero",
output="@itzero", ccdtype=" ", max_cache=0, noproc=no, fixpix=no,
overscan=yes, trim=yes, zerocor=no, darkcor=no, flatcor=no, illumcor=no,
fringecor=no, readcor=no, scancor=no, readaxis="line", fixfile="",
biassec="[2058:2071,100:4000]", trimsec="[6:2044,18:4090]", zero="", dark="",
flat="", illum="", fringe="", minreplace=1., scantype="shortscan", nscan=1,
interactive=no, function="chebychev", order=1, sample="*", naverage=1,
niterate=1, low_reject=3., high_reject=3., grow=0.)
Which is just ccdproc called several times for various files.
Here is the error when I try to run ccdproc with or without the script:
ERROR: CLGWRD: No match, or ambiguous abbreviation (chebychev)
called as: `cl ()'
One last thing that may be helpful. Because the error messages says ambiguous abbreviation (chebychev) I decided to change the Fitting function (function = legendre instead of chebychev. When I did this ccdproc ran with no errors. Do you know what could be calling this or why the error would be a result of the fitting function being chebychev?
Thanks,
Shelly
Thank you for your reply. I'm a bit leery to make a whole new iraf. Wouldn't this cause problems with my path?
I tried typing trace_d and IRAF doesn't recognize that as a task.
Here is what my hedit2.cl script looks like:
hedit ("iSDSS537trim.fits[2]",
"DATASEC", "[1:2039,1:4073]", add=no, addonly=no, delete=no, verify=no,
show=yes, update=yes)
hedit ("iSDSS537trim.fits[3]",
"DATASEC", "[1:2039,1:4073]", add=no, addonly=no, delete=no, verify=no,
show=yes, update=yes)
ect... It's just changing the header of the star files. This script is not one I am trying to use now. Also, when I did unlearn on ccdproc it changed the error message slightly in that it got ride of the (hedit2.cl) completely.
The script I'm trying to use now is:
ccdproc ("@izero",
output="@itzero", ccdtype=" ", max_cache=0, noproc=no, fixpix=no,
overscan=yes, trim=yes, zerocor=no, darkcor=no, flatcor=no, illumcor=no,
fringecor=no, readcor=no, scancor=no, readaxis="line", fixfile="",
biassec="[2058:2071,100:4000]", trimsec="[6:2044,18:4090]", zero="", dark="",
flat="", illum="", fringe="", minreplace=1., scantype="shortscan", nscan=1,
interactive=no, function="chebychev", order=1, sample="*", naverage=1,
niterate=1, low_reject=3., high_reject=3., grow=0.)
Which is just ccdproc called several times for various files.
Here is the error when I try to run ccdproc with or without the script:
ERROR: CLGWRD: No match, or ambiguous abbreviation (chebychev)
called as: `cl ()'
One last thing that may be helpful. Because the error messages says ambiguous abbreviation (chebychev) I decided to change the Fitting function (function = legendre instead of chebychev. When I did this ccdproc ran with no errors. Do you know what could be calling this or why the error would be a result of the fitting function being chebychev?
Thanks,
Shelly
Mike Fitzpatrick wrote on Aug 28, 2008
I tried typing trace_d and IRAF doesn't recognize that as a task.
The command is 'd_trace', not 'trace_d". A MKIRAF simply recreates your login.cl file, won't touch your loginuser.cl file, and gives you the option of initializing the uparm directory.
Anyway, I just noticed that the real problem is that you spelled the function "chebychev", it should be "chebyshev" (i.e. with a 'sh' instead of 'ch').
-Mike
sbursic wrote on Aug 28, 2008
Mike,
OK that is a little embarrassing. Sorry to have asked all of that just for a spelling problem.
I really appreciate your help! At least now if I have a "real" problem with this I'll now how to fix it. :D
Thanks again,
Shelly
OK that is a little embarrassing. Sorry to have asked all of that just for a spelling problem.
I really appreciate your help! At least now if I have a "real" problem with this I'll now how to fix it. :D
Thanks again,
Shelly
Last post on Aug 28, 2008