imstack crash V2.14

Robert Blum wrote on Jan 17, 2008

I get the following error when running nfextract (gemini.nifs.nfextract) after upgrading to V2.14:

ERROR: Error writing output image
"imstack("@"//tmpfile,tmpcube,title="*",pixtype="double")"
line 316: /home/blum/IRAF/scripts/nfextract.cl
called as: `nfextract (inimages=tfbrsnN20060722S0064)'

I have tried to run the imstack command separately and I get the same error.

Running nfextract on the same image works on my laptop which is still V2.12.2a (same gemini package v 1.9).

Thanks,
Bob

---

Mike Fitzpatrick wrote on Jan 17, 2008

Hi Bob,

First, be sure you've installed the patched binaries for v2.14 announced on the homepage, this affects anything using an image section. If you just installed v2.14 since last Tuesday you already have the fix.

If that doesn't fix it, an 'Error writing output image' could be a permissions problem on the output directory or image (e.g. does the image exist already?) or even a full disk (check /tmp as well as the output image disk).

Cheers,
-Mike

---

Robert Blum wrote on Jan 17, 2008

Thanks Mike. I reinstalled the binaries and it works now.

---

Catherine Farage wrote on Jan 17, 2008

Hi,

I have the same problem as Bob, which alerted me to the fact that I hadn't updated to the patched version of IRAF 2.14.
I downloaded the latest binaries for Mac Intel (ib.macx.x86 and nb.macx.x86), copied them to my irafbin directories and ran the install script again. Is that all that is required to reinstall the binaries, as it doesn't seem to have fixed the error?

Thanks,
Catherine.

---

Mike Fitzpatrick wrote on Jan 17, 2008

It shouldn't be necessary to rerun the install script, simply replacing the binaries should do it. You can verify that the binaries were indeed updated using the command:

cl> dir bin$x_images.e long+

Check the file date is from Jan 14 and not the original Dec release. If not, the files may have been unpacked in the wrong place.

That's not to say there may not still be some other bug, but you'll need to post parameters and perhaps data so we can reproduce the problem. It would also help if you posted the output of the 'dir' command above.

-Mike

---

Robert Blum wrote on Jan 17, 2008

cfarage

Hi,

I have the same problem as Bob, which alerted me to the fact that I hadn't updated to the patched version of IRAF 2.14.
I downloaded the latest binaries for Mac Intel (ib.macx.x86 and nb.macx.x86), copied them to my irafbin directories and ran the install script again. Is that all that is required to reinstall the binaries, as it doesn't seem to have fixed the error?

Thanks,
Catherine.

Hi Catherine,

I believe that is correct. At least, all I did was install the patched binaries.

-Bob

---

Catherine Farage wrote on Jan 17, 2008

Thank you both very much for your (very prompt!) replies, and the tip for checking whether I actually had updated. And yes - it was just a problem with the way I'd unpacked the archives - I'd managed to just copy the archive to the irafbin directory, rather than actually unpacking it :oops:

Thanks for your help,
Catherine.

---

Last post on Jan 17, 2008