Why is coot 0.5 relying on the element card at the right end of a pdb file for
proper atom colouring? Can one turn back the 0.4.1 behaviour?
--Björn
***
This e-mail may contain confidential information proprietary to Karo
Bjorn:
First I presume you mean element field (or column) rather than card.
Second, at least since COOT 0.3, which is when I started using COOT, it
has used the element field to colo[u]r atoms, so this is not new
behavio[u]r.
Steven
Björn Kauppi wrote:
Why is coot 0.5 relying on the
Yes, I put coot 0.5.0 into fink cvs, both stable and unstable
yesterday. Barring bug fixes, I won't touch the stable entry until 0.6
is released.
fink selfupdate-rsync
or
fink selfupdate-cvs
I've also built these on my 10.5 machines so they are available as
fink binary debian packages.
To answer your question then, there is no way in 0.5 to turn
back to the
old behaviour. It might be possible in new versions to
enable this, but
currently I am against the idea.
Running the file through pdbset solves the missing element identifier problem
-- not elegant, but quick
FWIW: If you have an 'old' pdb file, just run it through pdbset with no
keywords (other than 'END'), and the 'element column' will be added for you.
Johan
Paul Emsley wrote:
I think Björn means that previous versions of Coot could read archaic
(version 2.3) pdb files and infer the element
Another remark on colours in 0.5: redhat8 (non-pythonic) binaries on RHEL4 seem to have lost colours --
the model/fit/refine window, scripting window etc are all grey.
Dear Judit,
Oh I see.
It's a gtk1 vs gtk2 problem:
Please replace your xxx/share/coot/cootrc with the one in:
