Re: [COOT] Coot graphical performance
My processor is Intel Core i7-3630QM which appears from the web to be an IVY bridge. I have no problems with coot in windows with this processor and now have to boot to Win7 to model build with COOT and then back to Linux to refine and analyse. It is getting tedious. Paul
Re: [COOT] Coot graphical performance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Paul, I did not follow the rest of this thread, but coot is an OpenGL program and as far as I understand its performance depends on the graphics card and its driver much more than on your CPU. What graphics card (chip) does you computer have, and which driver do you use under Linux? Often problems like the one you describe resolves by using the manufacturer's driver. Best, Tim On 03/29/2013 04:16 PM, Paul Swartz wrote: My processor is Intel Core i7-3630QM which appears from the web to be an IVY bridge. I have no problems with coot in windows with this processor and now have to boot to Win7 to model build with COOT and then back to Linux to refine and analyse. It is getting tedious. Paul - -- Dr Tim Gruene Institut fuer anorganische Chemie Tammannstr. 4 D-37077 Goettingen GPG Key ID = A46BEE1A -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFRVbmcUxlJ7aRr7hoRAkm/AJ0ZFneKdwhezVl4xMQHEICOlbR6vwCcDDK4 QSanddgNrw7cOBwn7uwNrow= =iUIl -END PGP SIGNATURE-
Re: [COOT] Coot graphical performance
On Fri, Mar 29, 2013 at 8:16 AM, Paul Swartz paul_swa...@ncsu.edu wrote: My processor is Intel Core i7-3630QM which appears from the web to be an IVY bridge. I have no problems with coot in windows with this processor and now have to boot to Win7 to model build with COOT and then back to Linux to refine and analyse. It is getting tedious. I don't like using Windows either, but is there any reason why you can't refine and analyze the structure entirely in Windows instead of switching back and forth? -Nat
Re: [COOT] Coot graphical performance
Hi Paul, what is the problem running coot in linux? Installation? Otherwise I do not understand why to use a Win-based setup for model building... Coot runs pretty well, even with the graphic unit of an ivy-bridge, as long as the structures are not too large. Using an Nvidia card will not be an option as you are using a notebook, don't you. Cheers, Georg On 29.03.2013 16:16, Paul Swartz wrote: My processor is Intel Core i7-3630QM which appears from the web to be an IVY bridge. I have no problems with coot in windows with this processor and now have to boot to Win7 to model build with COOT and then back to Linux to refine and analyse. It is getting tedious. Paul -- Universität Tübingen Interfakultäres Institut für Biochemie Dr. Georg Zocher Hoppe-Seyler-Str. 4 72076 Tuebingen Germany Fon: +49(0)-7071-2973374 Mail: georg.zoc...@uni-tuebingen.de http://www.ifib.uni-tuebingen.de
Re: [COOT] Coot graphical performance
On 14/02/13 21:54, Paul Swartz wrote: I am attempting to use coot0.7 installed using the yum archive on Fedora 18 and a computer with intel HD graphics 4000 driver. When coot starts initially, the rotation and translation is nearly at the speed that I am used to with Fedora 16 install. If I do not translate, the rotation speed remains good. If I do translate, the rotation speed drops off by about 50 %. We are talking about merely translating the view here (not the molecule) right? At drops off more after each translation and eventually is so slow that it is unusable. I do not think that it is a graphics issue as pymol does not have any speed problems even with surfaces exhibited. Does anyone have a suggestion as to what I am doing wrong in the coot install? Thank you very much for any help you can give me. Sounds like a graphics driver bug to me. If I had to guess, I'd suggest that pymol uses display objects and (for the most part) coot does not (it uses immediate mode). We did hear before about problems of Sandy Bridge with Fedora 18, IIRC (and thus I tried to install Fed 18 on my laptop (to share the pain) but the installer crashed in a heap at partition-time - I gave up). I'd be curious to know if the problem still occurs with either Nahalem or Ivy Bridge. Not much help - sorry. Paul.
