iraf.net

If you need to respond to this message please do so by replying to this message or create a new message with call number CNSHD549231 included in the subject line.Request Log :
12/05/05 14:45:22 mcleskey

Request from mreed@sdbv.missouristate.edu

To: <Help@stsci.edu>
Cc:

Hi,
My postdoc has written an iraf task that only I seem unable to run. Here
is the problem: on the very same computer, my postdoc can log in, start
iraf, and type:
task sapp_AAU47x = /path/sapp_AAU47x.cl
and then epar sapp_AAU47x and edit the parameters as usual.

When I do the very same thing, on the very same computer, I get
cl> task sapp_AAU47x = /home/mreed/sapp_AAU47x.cl
cl> epar sapp_AAU47x
ERROR: task `sapp_AAU47x' has no param file
eparam ()


I have moved my parameter files, re-ran mkiraf and tried it again with the
same results. We are both running the same version of the task, on the
same computer, both in a xgterm. How can this be? Any ideas would be
appreciated.
Thanks,
Mike

12/05/05 14:50:46 jkim
Hi Mike,

I'm forwarding your call to NOAO, iraf@noao.edu, as STScI does not provide IRAF assistance.

Regards,
STScI Helpdesk

jkim changed status to Resolved

jkim mailed the current call log entry to mreed@sdbv.missouristate.edu

jkim assigned call to jkim

jkim mailed the entire call log to iraf@noao.edu

Hi Mike.> My postdoc has written an iraf task that only I seem unable to run. Here
> is the problem: on the very same computer, my postdoc can log in, start
> iraf, and type:
> task sapp_AAU47x = /path/sapp_AAU47x.cl
> and then epar sapp_AAU47x and edit the parameters as usual.
>
> When I do the very same thing, on the very same computer, I get
> cl> task sapp_AAU47x = /home/mreed/sapp_AAU47x.cl
> cl> epar sapp_AAU47x
> ERROR: task `sapp_AAU47x' has no param file
> eparam () A quick explanation would be that /home/mreed is not readable by
you on the machine (as is the default case for some linux systems) and
so when you declare the task the CL simply can't read the file. Check
and perhaps reset the permissions on the directory or else move the script
to a public directory where you have access, a quick check of this is that
you should be able to PAGE or TYPE the script file, if not it's either a
permissions problem or something wrong with the path (e.g. an nfs mount
point).
Hope this helps.Regards,
Mike Fitzpatrick
--------------------------NOTE: As of Jan 1, 2006 NOAO will no longer be operating a HelpDesk for
IRAF at iraf@noao.edu. Support is being moved to a forum-based system
at https://iraf.net, please post future questions to that site. Thanks.