implot
simintaka wrote on Jan 26, 2011
Hi everyone,I'm a new user of Iraf.
I have some troubles with the implot function.
I launch Iraf in xgterm, but when i try the implot command it doesn't work et
I have this message:
PANIC in `/iraf/iraf/bin.linux64/x_plot.e': Write to IPC with no reader
Does anyone already saw that???
thank you very much
I have some troubles with the implot function.
I launch Iraf in xgterm, but when i try the implot command it doesn't work et
I have this message:
PANIC in `/iraf/iraf/bin.linux64/x_plot.e': Write to IPC with no reader
Does anyone already saw that???
thank you very much
Mike Fitzpatrick wrote on Jan 26, 2011
A "write to IPC" message from a graphics task means that either there was an error in the plot task, or the CL graphics. Do you see the same problem with e.g.
or is it something you can localize to this specific image file? I assume this is a FITS file, if so could you upload it to the anonftp on ftp://iraf.noao.edu/pub so I can try to reproduce the problem? Does an "unlearn implot" to reset the task parameters help? How about a "gflush" in the CL before running the task? Does this happen immediately when you launch the task or in response to some particular keystroke?
Lastly, if you're using the original v2.15 release, then does using the v2.15.1 patch fix it?
cl> implot dev$pixor is it something you can localize to this specific image file? I assume this is a FITS file, if so could you upload it to the anonftp on ftp://iraf.noao.edu/pub so I can try to reproduce the problem? Does an "unlearn implot" to reset the task parameters help? How about a "gflush" in the CL before running the task? Does this happen immediately when you launch the task or in response to some particular keystroke?
Lastly, if you're using the original v2.15 release, then does using the v2.15.1 patch fix it?
simintaka wrote on Jan 26, 2011
Hi, thank you for your answer,
I tried the image on an other computer and it works, so I don't think this comes from the image.
I've tried the command you gave me and the result is:
and the gflush command returns the same error after trying implot.
It appends immediately when I launch the task.
I tried the image on an other computer and it works, so I don't think this comes from the image.
I've tried the command you gave me and the result is:
ecl> implot dev$pix
PANIC in `/iraf/iraf/bin.linux64/x_plot.e': Write to IPC with no reader
Segmentation fault (core dumped)
and the gflush command returns the same error after trying implot.
It appends immediately when I launch the task.
Mike Fitzpatrick wrote on Jan 26, 2011
Could you please post the output of the command "ldd /iraf/iraf/bin.linux64/x_plot.e" from outside of the CL? I'm wondering if there is a shared library problem, it would also help to know which linux distribution you are using.
Another useful thing to try is to execute the binary directly from the unix prompt, e.g.
You should see a ">" prompt if it works (type 'bye' to quit), otherwise a host-level error message may indicate the problem. Do you see similar problems from other tasks, e.g. "cl> prow dev$pix" ??
Another useful thing to try is to execute the binary directly from the unix prompt, e.g.
% /iraf/iraf/bin.linux64/x_plot.e You should see a ">" prompt if it works (type 'bye' to quit), otherwise a host-level error message may indicate the problem. Do you see similar problems from other tasks, e.g. "cl> prow dev$pix" ??
simintaka wrote on Jan 26, 2011
the result of the command "ldd /iraf/iraf/bin.linux64/x_plot.e" is :
when I try the line code you gave it doesn't return any error and I see the ">".
and no problems with the "cl>prow dev$pix.
I'm working on Fedora 13, I don't know if it matters or not.
%ldd /iraf/iraf/bin.linux64/x_plot.e
linux-vdso.so.1 => (0x00007fff6a971000)
libm.so.6 => /lib64/libm.so.6 (0x00000034f4c00000)
libc.so.6 => /lib64/libc.so.6 (0x00000034f4800000)
/lib64/ld-linux-x86-64.so.2 (0x00000034f4400000)
when I try the line code you gave it doesn't return any error and I see the ">".
and no problems with the "cl>prow dev$pix.
I'm working on Fedora 13, I don't know if it matters or not.
Mike Fitzpatrick wrote on Jan 26, 2011
Did you also try "implot dev$pix" or just with your image? So far it looks normal, but if there's an error in your FITS file it might be causing the task to crash and the error message is being masked somehow. Likewise, if "prow yourimage.fits" also fails I would suspect the data, if you could post that to the anonftp on ftp://iraf.noao.edu/pub I'll have a look.
simintaka wrote on Jan 26, 2011
"prow image.fit" return
I've sent my files in the ftp, it is named "Th-Ar1.fit"
thanks a lot
prow Th-Ar1.fits
row to be plotted (1:): 3
Segmentation fault (core dumped)
I've sent my files in the ftp, it is named "Th-Ar1.fit"
thanks a lot
Mike Fitzpatrick wrote on Jan 26, 2011
I got the image and everything looks fine with it and I can IMPLOT with no problems.
If you're still using the original v2.15 release then I'd recommend you apply the v2.15.1 patch. You should do this for other reasons, however it will also fix any installation problems you might now have (e.g. corrupted binaries) by replacing the binaries.
If you've done that and still have problem, then does a task like IMSTAT on the image also fail? I'm trying to figure out whether this is a graphics problem in the one binary, or something affecting all binaries.
If you're still using the original v2.15 release then I'd recommend you apply the v2.15.1 patch. You should do this for other reasons, however it will also fix any installation problems you might now have (e.g. corrupted binaries) by replacing the binaries.
If you've done that and still have problem, then does a task like IMSTAT on the image also fail? I'm trying to figure out whether this is a graphics problem in the one binary, or something affecting all binaries.
simintaka wrote on Jan 26, 2011
All right but does it mean I have to reinstall all the soft, or can I just add the patch ???
Mike Fitzpatrick wrote on Jan 26, 2011
The patch replaces all the binaries (which is why it is so large) and the modified sources. Just unpack as e.g.
% cd $iraf ; tar zxf /path/iraf-linux64.tar.gzsimintaka wrote on Jan 26, 2011
well I don't find the folder you told me,
Can I take patch1.lnux.x86_64.gz
Then I just gzip it in the /home/iraf folder??
Can I take patch1.lnux.x86_64.gz
Then I just gzip it in the /home/iraf folder??
Mike Fitzpatrick wrote on Jan 26, 2011
That's the right filename, to unpack use the 'tar' command in my previous message.
simintaka wrote on Jan 26, 2011
all right I did it, do I have to run the makefile now?
Mike Fitzpatrick wrote on Jan 26, 2011
No need for the makefile, the patch did all you need. Are you still seeing a problem?
simintaka wrote on Jan 26, 2011
Yes I added the patch but i'm not sure I did it right, and the implot doesn't work yet.
Mike Fitzpatrick wrote on Jan 26, 2011
There have been several reports of problems with IMPLOT however I can't reproduce it in any way.
To be sure we're running the same binary, could you post the output of the command:
Also, could you confirm that you are running this in either an XTerm or XGterm window (with the appropriate terminal setting in your login.cl file) and not something like an 'rxvt' or 'gnome-terminal'? Could you also post the output of a "uname -a" command (from outside of iraf)? Can you bring up a graphics cursor with a simple "=gcur" command at the CL prompt? Do tasks like IMSTAT also fail or is it just graphics tasks?
To be sure we're running the same binary, could you post the output of the command:
cl> dir bin$x_plot.e long+Also, could you confirm that you are running this in either an XTerm or XGterm window (with the appropriate terminal setting in your login.cl file) and not something like an 'rxvt' or 'gnome-terminal'? Could you also post the output of a "uname -a" command (from outside of iraf)? Can you bring up a graphics cursor with a simple "=gcur" command at the CL prompt? Do tasks like IMSTAT also fail or is it just graphics tasks?
Last post on Jan 26, 2011