i think what gerhard ment to say is:
it would be good if you always could explain a bit:
- which part of the docu you have read
- what you have tried
- and what exactly did not work as decribed there
this allows for more focussed answers and will help the programmers to
improve their
Dear Paul,
we have happily been running the coot-Linux-x86_64-centos-5-gtk2-python
build on our Scientific Linux 6.1 (RHEL-6 clone) machines. In
particular, version 3607 has been working very well for quite some time
now.
Today I tried to upgrade to version 3965, using
For the record, I hope/think that this is the same problem that is
currently affecting the RedHat 5 builds too about which one or two
others have contacted me. (We don't catch it because the automatic
testing doesn't start the gui.)
Paul.
On 26/01/12 13:36, Bernhard Lohkamp wrote:
Hi Kay,
I would be a bit more concerned with the apparent lack of fit of the model to
the map. It looks as if there is unoccupied side chain density, and possibly
side chains that don't occupy density. It is hard to tell from a snapshot, but
if this is the case, make sure everything is in register
On Jan 26, 2012, at 5:36 AM, Bernhard Lohkamp wrote:
Hope this resolves the problem,
B
Seems to fix it on OS X
-- Bill
Ha. Now that's just about where I went running (comments in the other
thread on ligand restraints...). See what I mean? Got to watch your
step...next run I'll bring my red/green glasses...
On Thu, Jan 26, 2012 at 12:06 PM, William G. Scott wgsc...@ucsc.edu wrote:
Does coot do red/greed
Personally, I like the ability to at least have a sanity check of the
HETNAM with the dictionary - and if they do not match - do not use
it... Assuming people provide a unique name in their dictionary - even
if it is FOO1, FOO2, etc - this could catch the issue. This assumes
that the refinement
On 26/01/12 21:48, Ezra Peisach wrote:
Personally, I like the ability to at least have a sanity check of the
HETNAM with the dictionary - and if they do not match - do not use
it... Assuming people provide a unique name in their dictionary - even
if it is FOO1, FOO2, etc - this could catch the
