Iraf Error
Contents |
the core system (the ib.* files), and the NOAO package binaries (the nb.* files). Because the system is distributed with source, considerable disk space can be recovered by stripping the source files with the cl> mkpkg strip what is iraf # strip the core system cl> cd noao # move to NOAO directory cl> mkpkg -p
Error: Cannot Open Device (node!imtool,,512,512)
noao strip # strip the NOAO package utility, run as iraf from the iraf root. The source files are not required for a run-time cannot open device (node!imtool,,4096,4096) system. Software development, including IMFORT programming and building external packages, can still be accomplished on a stripped system. The "mkpkg strip" is normally done after unpacking the as and ib/nb files, after IRAF is fully installed. On systems where space iraf display is extremely tight, you can run "mkpkg strip" immediately after unpacking the as files and running the install script. This would free sufficient space to allow the binaries to be unpacked. We estimate about 1/2 the total diskspace consumed by IRAF is recovered by stripping the source. If this is still not sufficient, it is possible to delete individual binaries by hand. IRAF site support can advise you as to which binaries are least likely to be useful for
Iraf Stdimage
your particular applications. It is important to remember that IRAF doesn't necessarily have to be installed on a disk local to the machine, any available (e.g. NFS mounted) disk will do. External packages can similarly be stripped of source. What does the IRAF install script really do - what files are modified? In general terms the install script does the following: - edits the iraf pathname and imdir directory in the following files: hlib$cl.csh hlib$mkiraf.csh hlib$libc/iraf.h - creates fifo pipes for image display in the /dev directory - creates the /usr/include/iraf.h symbolic link defining the iraf root - sets root ownership for the tape allocation task 'alloc.e' - creates symbolic links for IRAF commands like 'cl' in the site dependent 'local bin directory'. Because the install script affects files in system directories, root permission is required to run it successfully. Workarounds for some things done by the install script can be found elsewhere in this FAQ. The install script must be run on each client machine to create the fifo pipes for that node. If nodes in the network will be sharing an iraf directory tree, the iraf root must appear to be the same on all nodes. This can be done with a symbolic link and is necessary so the definition of the iraf root in the shared hlib$cl.csh file is valid for all nodes. I'm not able to write in /usr - can I still
»Systems »Misc »Sources »Virtual Observatory »Python »Non-IRAF Software »Open Positions »Resumes »Sitemail Archives »Test Forum Index>Help Desk>General IRAF New Topic Post Reply graphics overlay not available for display device Cannot open image Houdebine 07/13/2008 06:25AM(Read 9156 times) splot iraf Newbie Status: offline Registered: 07/12/2008 Posts: 8 I have a problem with plotting a 1d spectrum.
Iraf Windows
All the files are in my directory, but when I try to plot I get:on> splot extra039 ERROR: Cannot open image (extra039)Can someone let me know why iraf http://iraf.noao.edu/faq/FAQsec09.html cannot find my files ? Profile Email Quote sukye 07/13/2008 06:25AM Newbie Status: offline Registered: 07/13/2008 Posts: 1 i met a similar problem when i use imcopy task. ERROR (741, "Cannot open file ....but more trick here is that some of other files produced together could be opened successfully. i have tried chmod u+w with http://iraf.net/forum/viewtopic.php?showtopic=139859 no luck...sujian Profile Email Quote valdes 07/13/2008 06:25AM Active Member Status: offline Registered: 11/11/2005 Posts: 714 Hello,To help you please send the output of the commands:[code:1:0bf124d331] cl> dir l+ cl> lpar splot [/code:1:0bf124d331]Yours, Frank Valdes Profile Email Quote Houdebine 07/13/2008 06:25AM Newbie Status: offline Registered: 07/12/2008 Posts: 8 I get this:I get many files -b-rwr-r- eric 15360 Dec 7 1992 smooth010.pix -b-rwr-r- eric 8860 Dec 7 1992 smooth013.imh -b-rwr-r- eric 28160 Dec 7 1992 smooth013.pix -b-rwr-r- eric 8860 Dec 7 1992 smooth015.imh -b-rwr-r- eric 19456 Dec 7 1992 smooth015.pix -b-rwr-r- eric 8860 Dec 4 1992 smooth016.imh -b-rwr-r- eric 19456 Dec 4 1992 smooth016.pix -b-rwr-r- eric 8860 Dec 4 1992 smooth032.imh -b-rwr-r- eric 19456 Dec 4 1992 smooth032.pix -b-rwr-r- eric 8860 Dec 7 1992 smooth034.imh -b-rwr-r- eric 28160 Dec 7 1992 smooth034.pix -b-rwr-r- eric 8860 Dec 18 1992 smooth043.imh -b-rwr-r- eric 8860 Dec 7 1992 smooth045.imh -b-rwr-r- eric 19456 Dec 7 1992 smooth045.pix -b-rwr-r- eric 8860 Dec 4 1992 smooth051.imh -b-rwr-r- eric 25088 D
errors using try http://stsdas.stsci.edu/pyraf/doc.old/pyraf_guide/node5.html and except. This works even when calling IRAF tasks; that is, an error in a CL script or a call error in an http://www.adamgginsburg.com/IRAF.htm SPP program can be caught using try in Python. For example, --> try: ... iraf.columns ("garbage", 37) ... except iraf.IrafError, e: ... cannot open print "error was caught" ... print e ... Killing IRAF task `columns' error was caught Error running IRAF task columns IRAF task terminated abnormally ERROR (741, "Cannot open file (garbage)") There's a catch, however. Many IRAF tasks can operate on a list of input cannot open device files, and these tasks usually convert some errors (such as file not found) into a warning, allowing the task to continue trying to process the other input files. But warnings are not caught by try and except. The imstat task used by nc.py in the ncounts example is a case in point; a try statement was not used there because it would not trap the most common problems, such as a mistake in the name of the input image. If you want to do robust error handling, it is best to check parameter values in Python before calling the IRAF task to ensure predictable behavior when errors occur. PyRAF Programmer's Guide Previous: 4 Dealing with I/O Up: PyRAF Programmer's Guide Next: 6 Task Parameters Questions or comments? Contact help@stsci.edu Documented updated on
are set on lines 7 and 8 of your login.cl file. To install IRAF, run mkiraf, which will create a new login.cl for you. You may have to change your imdir to "home$images/" or something similar. You must search for the line #set imtype "imh" and change it to read set imtype "fits" (remove the # at the beginning of the line). If you have trouble with .imh files showing up instead of .fits files: check to see if your imtype is set correctly with show imtype. if it's imh, use set imtype=fits to fix it you may need to use the flpr command to make sure IRAF recognizes the change Find your login.cl file. Make sure the set imtype=fits line is uncommented as in the directions above. IRAF quick tips To start logging with pyraf, use the command .logfile [filename.log] -If you see errors that involve "uparm" or "unable to write...": -try to logout of the cl and log back in; make sure you're in the directory with your login.cl file -make sure your login.cl has been edited as per the directions above -If you have problems with imexam and cursor behavior: -restart DS9, try again -restart DS9, logout of the cl and log back in -get frustrated, call or e-mail Adam, see if he gets frustrated -Using IRAF graphics terminals: -q quits; a quit and re-enter solves most problems -? displays help in the terminal. Don't forget to quit out of the help when you're done -:(command) allows "colon commands" that can be quite powerful (see, e.g., "wcs" in imexam) -A syntax error in IRAF generally means you have not loaded the requisite package. -if you don't know what package that is, use the help command (e.g. help temden) Matching Guider Images to Science Images Instead of going through each individual file's header, I recommend using these commands or similar: imhead proc-*.fits[0] lo+ | egrep "Pixel\ file\|UTTIME" imhead e*.fits lo+ | grep -E "Pixel\ file\|UTC-OBS" If you're curious about what those commands mean, read on. You should already be familiar with the imhead command, which with the long option enabl