Welcome to iraf.net Tuesday, April 23 2024 @ 09:25 PM GMT


 Forum Index > Help Desk > General IRAF New Topic Post Reply
  IRAF 2.16.1: gkimos problem
   
rjvo
 10/24/2013 02:03PM (Read 2336 times)  
+++++
Active Member

Status: offline


Registered: 04/21/2007
Posts: 134
The new version has also some problems with "gkimos". There is an error:
PHP Formatted Code
X Error of failed request:  BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request:  53 (X_CreatePixmap)
  Resource id in failed request:  0x3c00036
  Serial number of failed request:  24383
  Current serial number in output stream:  24414
 

For some plots, the command is able to block the xgterm completely.

 
Profile Email
 Quote
fitz
 10/24/2013 03:02PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
This is an X11 error related to the XGterm and has nothing to do with the IRAF version. Which binary are you using (linux or mac)?

 
Profile Email
 Quote
rjvo
 10/25/2013 08:00AM  
+++++
Active Member

Status: offline


Registered: 04/21/2007
Posts: 134
I use Debian Linux last version.
Yes, the error is in X but is caused by xgterm and I do not know who is able to correct it. Isn't the xgterm a part of IRAF?

 
Profile Email
 Quote
fitz
 10/25/2013 07:05PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
With v2.16.1 the XGterm binary is part of the core installation. On Linux systems we distribute a statically linked version since it is becoming more common that newer linux distros don't default to install 32-bit compatability libs. This is an old binary (newer GCC versions don't compile statically without complaining about glibc functions that should be dynamic) and may not be playing nice with the X server.

If you did a personal installation you can simply delete $HOME/.iraf/bin/xgterm (and 'ximtool') to go back to using the xgterm binary you previously had installed. You can also get X11IRAF linux binaries from

ftp://iraf.noao.edu/iraf/x11iraf/x11iraf-v2.0BETA-bin.linux.tar.gz

Note the personal install will modify your $PATH to put $HOME/.iraf/bin ahead of other directories, so if you install new binaries you should replace the versions in $iraf/vendor/x11iraf/bin.linux to be sure you're using the right one.

 
Profile Email
 Quote
Anonymous: carrot
 10/30/2013 12:21PM  



Quote by: fitz

With v2.16.1 the XGterm binary is part of the core installation. On Linux systems we distribute a statically linked version since it is becoming more common that newer linux distros don't default to install 32-bit compatability libs. This is an old binary (newer GCC versions don't compile statically without complaining about glibc functions that should be dynamic) and may not be playing nice with the X server.

If you did a personal installation you can simply delete $HOME/.iraf/bin/xgterm (and 'ximtool') to go back to using the xgterm binary you previously had installed. You can also get X11IRAF linux binaries from

ftp://iraf.noao.edu/iraf/x11iraf/x11iraf-v2.0BETA-bin.linux.tar.gz

Note the personal install will modify your $PATH to put $HOME/.iraf/bin ahead of other directories, so if you install new binaries you should replace the versions in $iraf/vendor/x11iraf/bin.linux to be sure you're using the right one.



I got a similar error message from mac (OS X 10.8.x)
My imac can't get a coordinates from DS9 when I display images to ds9 from iraf
while there is no problem when images were opened from ds9 menu bar.

How can I delete the xgterm binary in mac?

---

xgterm: warning, error event received:
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 53 (X_CreatePixmap)
Resource id in failed request: 0xc00013
Serial number of failed request: 28781
Current serial number in output stream: 28812

 
 Quote
fitz
 10/30/2013 04:17PM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040

You can delete/rename the binaries in $iraf/vendor/x11iraf/bin.linux (and/or bin.macintel) and your path should pick up the previous binary you were using. A BadDrawable error may indicate you're not using a compatible X visual (e.g. a 16-bit default for some reason), you can use the 'xdpyinfo' command to verify what your default visual us. XGterm/XImtool do support 24- and 32-bit visuals.

 
Profile Email
 Quote
Anonymous: carrot
 10/31/2013 06:13AM  



Quote by: fitz


You can delete/rename the binaries in $iraf/vendor/x11iraf/bin.linux (and/or bin.macintel) and your path should pick up the previous binary you were using. A BadDrawable error may indicate you're not using a compatible X visual (e.g. a 16-bit default for some reason), you can use the 'xdpyinfo' command to verify what your default visual us. XGterm/XImtool do support 24- and 32-bit visuals.



xdpyinfo prints next:
visual:
visual id: 0x139
class: TrueColor
depth: 15 planes
available colormap entries: 32 per subfield
red, green, blue masks: 0x7c00, 0x3e0, 0x1f
significant bits in color specification: 5 bits


I'm using imt4096 setting to display 2048x4096 images.
but if an image is called from iraf display task, ds9 displays it with wrong coordinates.
Y pixels are good, but ds9 shows x pixels up to more than 3000 pixel.
Iraf get this wrong coordinates and when I use imexam task, iraf give me an information for this wrong coordinates.
Of course, if I hit s or r on the pixels higher than 2048, irafterm answers "Warning: Pixels out of bounds".
There is no such a problem is an image is called using menu bar of ds9.

I tested with imt2048 by modifying login.cl, and in this case there is no problem in X pixel,
but iraf get wrong Y pixel from ds9.

I tried several re-installs of iraf, xgterm, and ds9, but the problem can not be fixed.

I tried to install both 32-bit and 64-bit iraf.
also I tried to install x11iraf-v2.0BETA-bin.macintel.tar.gz for xgterm.

What's wrong in my installation?
I'm using iMac with OS X 10.8.5.
I bought this only a week ago.

 
 Quote
fitz
 10/31/2013 06:36AM  
AAAAA
Admin

Status: offline


Registered: 09/30/2005
Posts: 4040
There is a known bug in DS9 v7.2 related to coord readback within IRAF, I think Gemini is recommending v7.1 as a workaround at the moment.

 
Profile Email
 Quote
Anonymous: carrot
 10/31/2013 07:38AM  



Quote by: fitz

There is a known bug in DS9 v7.2 related to coord readback within IRAF, I think Gemini is recommending v7.1 as a workaround at the moment.



Thank you very much!
The problem was fixed!!.

 
 Quote
   
Content generated in: 0.38 seconds
New Topic Post Reply

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login