Hi Thomas,
You can also zoom out to get everything in view. You can also change
the field of view. And then you can ray just the way you want, based
on what you have in sight, in as high a resolution you want.
Cheers,
Tsjerk
On Thu, Oct 22, 2009 at 9:35 PM, Thomas Stout wrote:
>
> But isn't it
Hi folks,
I was using PyMol with no problems about a year ago. I believe that my PyMol
version was in the 0.9x series. I was using Ubuntu Linux 6.06 on a Pentium IV
machine.
Since then I have upgraded to a new multi-core motherboard, and Ubuntu Linux
8.04. The Linux repository has a PyM
Hello again,
With some hints from Ubuntu Forums, I tracked down and corrected my problem.
Hopefully this will be of help to someone else.
The fancy new desktop rendering schemes which are part of Ubuntu v.8, but which
were not part of Ubuntu v.6, use 3D graphics to grow, shrink, and move wi
John,
We have seen such problems with OpenGL-based applications, including PyMOL,
running under ATI Radeon hardware & graphics with older versions of the
OpenGL-based Compiz window manager.
The easiest solution is to reconfigure Linux to disable compositing and/or use
a conventional window
Hi John,
I have a similar problem with my ubuntu 8.10. When I use a command
window, I get the error message:
Traceback (most recent call last):
File "/var/lib/python-support/python2.5/pymol//__init__.py", line 167,
in
import pymol
File "/var/lib/python-support/python2.5/pymol/__init__.py
Andrea,
I use MD quite a lot myself and we have some "in-house" tools that perform this
function (converting a set of PDB files into a trajectory). However, I took it
upon myself as a challenge to see if I could implement this into PyMOL as a
Python script. Thus, last night I worked feverish
Hi All,
I was wondering if there was a faster way to replace all coordinates. I've
used commands such as iterate_state and alter_state before but they are far too
slow since they have to iterate over each atom. Instead, I want to replace one
set of coordinates that correspond to a specific s
Tsjerk,
I think you are missing the point of Tom's post, which was a suggestion to
aid someone who's computer could NOT deliver the image in "as high a
rsolution as you want', so Tom was proposing a way to break the image down
into bite-size chunks that the computer COULD then handle. So the sugges
