iraf.net

A strange problem just popped up. A user has the following in her IRAF login.cl:imred
mscred
crutil
onedspec
twodspec
apextract
ccdredand when she types:ccdred> cosmicrays
ERROR: Cannot open connected subprocess (./xx_ccdred.e)and similarly for many other related tasks.If the ccdred is put after the imred then all is well. This seems to be true on all IRAF installations I found quickly.What is the right order, and why?Thanks! Richard

Hi Richard, The problem appears to be in MSCRED: This package also defines a 'ccdred' package that declares the COSMICRAYS task to be in the x_ccdred.e binary, but in fact it is no longer in there. So, in the list you give, the 'ccdred' loaded in the last step is the one from mscred and the task definition for cosmicrays overwrites the one from the CRUTIL package. Frank is out this week but can fix the package when he returns. Until then, you can either just load MSCRED first (and the CRUTIL load will declare the correct COSMICRAYS, and the CCDRED will be the one from IMRED), or else prefix the task name with the package to force it, e.g.[code:1:5c55580e42]cl> crutil.cosmicrays[/code:1:5c55580e42]Cheers,
-Mike

Hi Richard,I see the problem and a fix has been made; though the mscred package is now rarely updated for a new version. The fix was modifying mscred.cl. The diff is below if you are interested.Yours,
Frank[code:1:263c0f2086]
31c31
< set ccdred = "mscsrc$ccdred/"
---
> set mccdred = "mscsrc$ccdred/"
57c57
< ccdgroups = ccdred$x_ccdred.e
---
> ccdgroups = mccdred$x_ccdred.e
65,66c65,66
< task darkcombine = ccdred$darkcombine.cl
< task flatcombine = ccdred$flatcombine.cl
---
> task darkcombine = mccdred$darkcombine.cl
> task flatcombine = mccdred$flatcombine.cl
68c68
< task zerocombine = ccdred$zerocombine.cl
---
> task zerocombine = mccdred$zerocombine.cl
[/code:1:263c0f2086]