nhedit
cosmologist wrote on Dec 23, 2010
Hi,
I am looking in images.imutil and I can't find the nhedit task...
when I type help nhedit, I get the error message that no help for nhedit is available. Is there a way to just get that specific task (although everything else in the imutil package is available)?
Thanks
I am looking in images.imutil and I can't find the nhedit task...
when I type help nhedit, I get the error message that no help for nhedit is available. Is there a way to just get that specific task (although everything else in the imutil package is available)?
Thanks
cosmologist wrote on Dec 23, 2010
I looked in the help page, but it doesn't say anything about downloading it separately. :( :(
Mike Fitzpatrick wrote on Dec 23, 2010
If NHEDIT isn't in your IMUTIL package then you're running a version of IRAF earlier than v2.14 and will need to get the FITSUTIL external package from ftp://iraf.noao.edu/iraf/extern or else upgrade your IRAF system. If you need this for GEMINI reductions, you'll need to update your IRAF anyway. There is no distribution of just the one task.
cosmologist wrote on Dec 23, 2010
Thanks a lot for your reply.
I re-downloaded the package from the link you provided:
File:fitsutil.tar.gz
106 KB
12/5/05
12:00:00 AM
But that one doesn't have the nhedit either. Is that the one you meant?
Thank you!
I re-downloaded the package from the link you provided:
File:fitsutil.tar.gz
106 KB
12/5/05
12:00:00 AM
But that one doesn't have the nhedit either. Is that the one you meant?
Thank you!
Mike Fitzpatrick wrote on Dec 23, 2010
That's the correct file, and the task in definitely in there (just checked). Note that this is only a source distribution of the package, you would need to either build that from source to update the binaries, or depending on your platform (you didn't say what it was) install the pre-built binaries.
If you tried to build from source, be sure you also reconfigured the package for the proper arch before building (e.g. "mkpkg -p fitsutil redhat"), otherwise the binary may have been put in the 'bin.generic' directory (which should be empty, but if you did this just move the x_fitsutil.e binary).
If you tried to build from source, be sure you also reconfigured the package for the proper arch before building (e.g. "mkpkg -p fitsutil redhat"), otherwise the binary may have been put in the 'bin.generic' directory (which should be empty, but if you did this just move the x_fitsutil.e binary).
cosmologist wrote on Dec 23, 2010
fitz
That's the correct file, and the task in definitely in there (just checked). Note that this is only a source distribution of the package, you would need to either build that from source to update the binaries, or depending on your platform (you didn't say what it was) install the pre-built binaries.
If you tried to build from source, be sure you also reconfigured the package for the proper arch before building (e.g. "mkpkg -p fitsutil redhat"), otherwise the binary may have been put in the 'bin.generic' directory (which should be empty, but if you did this just move the x_fitsutil.e binary).
Thank you for your reply.
I am using a mac, after downloading the package I specified the path in the hlib/extern.pkg. Is there anything else I need to do?
[ This is what I have so far:
NOAO/IRAFNET PC-IRAF Revision 2.14 Fri Nov 30 15:27:05 MST 2007
This is the RELEASED version of IRAF V2.14 supporting PC systems.
Welcome to IRAF. To list the available commands, type ? or ??. To get
detailed information about a command, type `help <command>'. To run a
command or load a package, type its name. Type `bye' to exit a
package, or `logout' to get out of the CL. Type `news' to find out
what is new in the version of the system you are using.
Visit http://iraf.net if you have questions or to report problems.
The following commands or packages are currently defined:
dataio. gemini. lists. plot. system. wifes.
dbms. gmisc. nmisc. proto. tables.
expand images. noao. softools. tr
fitsutil. language. obsolete. stsdas. utilities.
ecl> imag
imcoords. imfit. immatch. tv.
imfilter. imgeom. imutil.
images> imut
chpixtype imdelete imheader imslice listpixels
hedit imdivide imhistogram imstack minmax
hselect imexpr imjoin imstatistics sections
imarith imfunction imrename imsum
imcopy imgets imreplace imtile ]
Mike Fitzpatrick wrote on Dec 23, 2010
By installing the FITSUTIL package as a means to get the NHEDIT task, the task will be in the FITSUTIL package. It does not install the task in the IMUTIL package, you need to update IRAF to do that.
Type 'fitsutil' to load the package.
Type 'fitsutil' to load the package.
cosmologist wrote on Dec 23, 2010
:cry: :cry: :cry:
I don't know what I did wrong, but you know when you install iraf on a mac it is installed as a different user (called iraf usually).
After changing the fitsutil package, I ran it for the "iraf" user, and it worked, but now when I do the same from for another user (other than iraf) I get this error message:
(This message doesn't appear for iraf user)
Does my question make sense? Do you know what the problem might be?
I don't know what I did wrong, but you know when you install iraf on a mac it is installed as a different user (called iraf usually).
After changing the fitsutil package, I ran it for the "iraf" user, and it worked, but now when I do the same from for another user (other than iraf) I get this error message:
ecl> fitsutil
ERROR: task `fitsutil' has no param file(This message doesn't appear for iraf user)
Does my question make sense? Do you know what the problem might be?
Mike Fitzpatrick wrote on Dec 23, 2010
The error message means the path to the fitsutil directory is improperly specified (e.g. no trailing '/', it's done after the 'keep' statement in the hlib$extern.pkg file, etc) or isn't specified at all. This path can either be specified in the user's shell environment or the extern.pkg file, in the latter case the error should be seen by all users. Do a 'show fitsutil' to see if it's different between users and have another look at the extern.pkg file.
Note that even if you don't build from sources, you still need to install the source distribution (this is what has the parameter file).
Note that even if you don't build from sources, you still need to install the source distribution (this is what has the parameter file).
cosmologist wrote on Dec 23, 2010
I am not sure I understand the details you mentioned.
Does it help if I share what I have extern.pkg:
Note that when I was using the other fitsutil package, I was able to run it from all users, but it didn't have nhedit, now the new package has nhedit but it doesn't run for all users.
Any suggestion?
Thank you
Does it help if I share what I have extern.pkg:
vi extern.pkg
reset fitsutil = /iraf/extern/fitsutil/
task fitsutil.pkg = fitsutil$fitsutil.cl
#reset fitsutil = /iraf/extern/fitsutil-src/
#task fitsutil.pkg = fitsutil$fitsutil.cl
reset gmisc = /iraf/extern/gmisc-src/
task gmisc.pkg = gmisc$gmisc.cl
reset nmisc = /iraf/extern/nmisc-src/
task nmisc.pkg = nmisc$nmisc.cl
reset helpdb = "lib$helpdb.mip\
,noao$lib/helpdb.mip\
,tables$lib/helpdb.mip\
,stsdas$lib/helpdb.mip\
,wifes$helpdb.mip\
"
keep
-- INSERT -- Note that when I was using the other fitsutil package, I was able to run it from all users, but it didn't have nhedit, now the new package has nhedit but it doesn't run for all users.
Any suggestion?
Thank you
Mike Fitzpatrick wrote on Dec 23, 2010
As the 'iraf' user and the 'other' user, login to the CL and type "show fitsutil" and "=osfn('hlib$')" ..... do this to make sure the paths are the same for each user and you're indeed using the same extern.pkg file. If these are the same, then check the file permissions on /iraf/extern/fitsutil to be sure all users can read the directory.
If you're sure the /iraf/extern/fitsutil/fitsutil.cl file exists on the machine, also make sure each user is able to read that as well.
If you're sure the /iraf/extern/fitsutil/fitsutil.cl file exists on the machine, also make sure each user is able to read that as well.
cosmologist wrote on Dec 23, 2010
This is what I get as the iraf user:
And this is what I get as other user:
And this is the permission for the directory and the specific file:
ecl> show fitsutil
/iraf/extern/fitsutil/
ecl> =osfn('hlib$')
/Users/IRAF/iraf/iraf/unix/hlib/And this is what I get as other user:
ecl> fitsutil
ERROR: task `fitsutil' has no param file
ecl> show fitsutil
/iraf/extern/fitsutil/
ecl> =osfn('hlib$')
/Users/IRAF/iraf/iraf/unix/hlib/
And this is the permission for the directory and the specific file:
:extern IRAF$ ls -ld fitsutil/
drwxrw-rw-@ 26 IRAF staff 884 Dec 25 09:39 fitsutil/
:extern IRAF$ ls -l fitsutil/fitsutil.cl
-rw-rw-rw-@ 1 IRAF staff 541 Dec 21 2004 fitsutil/fitsutil.cl
Mike Fitzpatrick wrote on Dec 23, 2010
Try "unlearn fitsutil" as the non-iraf user ......
cosmologist wrote on Dec 23, 2010
ecl> unlearn fitsutil
ecl> fitsutil
ERROR: task `fitsutil' has no param file
Mike Fitzpatrick wrote on Dec 23, 2010
Before loading the package, type 'd_trace' and post the output. Also, please post the output of a "!env" command.
cosmologist wrote on Dec 23, 2010
ecl> d_trace
0 8+3: end
ecl> fitsutil
----- task cl - line 0 (CALL) -----
0 0+6: call fitsutil
ERROR: task `fitsutil' has no param file
cl_error: abort=1 trace=1 flpr=1
cl_error: code=0 do_err=1 errtype=1/1 task='cl'
ecl> !env
----- task cl - line 0 (OSESC) -----
0 0+4: os_escape env
REMOTEHOST=
TERM_PROGRAM=Apple_Terminal
HOST=...-MacBook-Pro.local
TERM=xterm
SHELL=/bin/bash
iraf=/Users/IRAF/iraf/iraf/
TMPDIR=/var/folders/gP/gPlxrltyFBidtDjaYrTweU+++TI/-Tmp-/
Apple_PubSub_Socket_Render=/tmp/launch-X1PsMV/Render
TERM_PROGRAM_VERSION=273
WINDOWID=6291465
GROUP=staff
USER=randa
COMMAND_MODE=unix2003
HOSTTYPE=intel-mac
SSH_AUTH_SOCK=/tmp/launch-uDjrlu/Listeners
__CF_USER_TEXT_ENCODING=0x1F5:0:0
COLUMNS=80
mach=macintel
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/texbin:/usr/X11/bin
_=/usr/bin/env
PWD=/Users/randa
LANG=en_US.UTF-8
LINES=24
IRAFBIN=/Users/IRAF/iraf/iraf/bin.macintel/
SHLVL=3
HOME=/Users/randa
OSTYPE=darwin
IRAFARCH=macintel
VENDOR=apple
MACHTYPE=x86_64
LOGNAME=randa
arch=.macintel
DISPLAY=/tmp/launch-kcntYm/org.x:0
0 4+3: end
Mike Fitzpatrick wrote on Dec 23, 2010
The only thing left I can imagine is that the non-iraf user might either redefine the 'fitsutil' variable (you say it doesn't) or re-declare the task in a login.cl or loginuser.cl file.
As the problem user, try doing a new MKIRAF in /tmp to create a vanilla login.cl and clean uparm directory. If the problem goes away there's something defined in the user's login(user).cl file or environment screwing things up. Is there actually a 'fitsutil.par' file in the '/iraf/extern/fitsutil directory? What version of IRAF is this (i.e. look at the hlib$motd file or do a "show version")? Any chance there is a SciSoft installation on the machine that's getting confused with some other iraf installation?
As the problem user, try doing a new MKIRAF in /tmp to create a vanilla login.cl and clean uparm directory. If the problem goes away there's something defined in the user's login(user).cl file or environment screwing things up. Is there actually a 'fitsutil.par' file in the '/iraf/extern/fitsutil directory? What version of IRAF is this (i.e. look at the hlib$motd file or do a "show version")? Any chance there is a SciSoft installation on the machine that's getting confused with some other iraf installation?
cosmologist wrote on Dec 23, 2010
1) mkiraf didn't help...
2)There is a fitsutil.par file
3) version:
4) I don't think I have a SciSoft installation on my machine.
:cry:
Any other thoughts?
2)There is a fitsutil.par file
ls -l *.par
-rw-rw-rw-@ 1 IRAF staff 56 Jul 31 1997 fitsutil.par3) version:
ecl> show version
NOAO/IRAF V2.14EXPORT
4) I don't think I have a SciSoft installation on my machine.
:cry:
Any other thoughts?
Mike Fitzpatrick wrote on Dec 23, 2010
If you want to email me login information I'll be lad to have a look, otherwise all we know for sure is there's a difference between the two users.
Have the 'iraf' user login to the other user's login.cl directory and vice-versa, and/or source the respective .cshrc/.login files to pickup environment defs, etc. As the troubled user declare the package on the CL commandline to see if it works, e.g.
If it works, the problem is in the startup files, if not it may still be a permissions problem, e.g. can you "cl> type fitsutil$fitsutil.par" from both accounts? If you have symlinks created for /iraf, do they point through directories like /Users/IRAF that might be restrictive? What about /iraf/extern? Outside of iraf, is there a $iraf or $fitsutil environment variable defined?
Have the 'iraf' user login to the other user's login.cl directory and vice-versa, and/or source the respective .cshrc/.login files to pickup environment defs, etc. As the troubled user declare the package on the CL commandline to see if it works, e.g.
cl> reset fitsutil = /iraf/extern/fitsutil/ <-- trailing '/' !!!!!
cl> task fitsutil = fitsutil$fitsutil.cl
cl> fitsutil
If it works, the problem is in the startup files, if not it may still be a permissions problem, e.g. can you "cl> type fitsutil$fitsutil.par" from both accounts? If you have symlinks created for /iraf, do they point through directories like /Users/IRAF that might be restrictive? What about /iraf/extern? Outside of iraf, is there a $iraf or $fitsutil environment variable defined?
Last post on Dec 23, 2010