Welcome to iraf.net Wednesday, May 01 2024 @ 06:24 PM GMT
| rij |
01/18/2007 09:27PM (Read 3513 times)
|
|
|
Status: offline
Registered: 03/07/2006
Posts: 1
|
Hi, The task irlincor is declared like this in noao$imred/irred/irred.cl:task irlincor = "irred$x_irred.x" While this works OK under the cl, it fails under PyRAF. As far as I can see, this is the only example in the whole IRAF tree of a task being declared by naming its source file rather than its executable, so I suspect the .x extension was inadvertent. Regards, Robert Jedrzejewski
|
| |
|
|
| fitz |
|
01/18/2007 09:27PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
Hi Robert,Thanks for the notice. It appears to be a typo from way back in 94 when the task was first imported from the CTIO package. It's a quirk of the CL that the extension actually gets deleted when the task in created, the CL knows it isn't script task and so when it constructs a path to the executable the .e becomes part of the path again. I've fixed it for the next release.Thanks,
-Mike
|
| |
|
|
| |
|
| Content generated in: 0.07 seconds |
|
New Topic
Post Reply
task irlincor incorrectly(?) declared in irred.cl
Quote
