Ed,
Currently command line data are handled in Coot before any scripting
information (e.g. preferences) is processed. Hence the default map
sampling is valid for the command line map but the preference set one
for subsequently opened maps. I guess we may want to revisit the command
line arguments and consider processing some (all?) after the scripting
(i.e. preferences) is dealt with.
B
I think the preferences are ignored when I use "coot --auto mymap.mtz"
or such to load the map from command line. I noticed because I always
set map sampling rate to 2.5, and when --auto option is used from
command line, I am positive maps are rendered with the default value of
1.5. Curiously, after quitting coot and restarting it and picking the
last state, it's the same map but this time sampled at 2.5.
This is exactly the reason I don't use the "View result of refinement in
Coot" button in ccp4i - it ignores whatever preferences I have set
previously. So I used to simply open coot and load the latest pdb/mtz
from the current folder manually, but then I thought myself smarter than
that and wrote a little script that picks the latest pdb/mtz from the
current folder and opens them in coot. To my dismay, the preferences
are ignored and I end up using the script but then going through
quit/restart routine - works, but not perfect. I can think of couple of
more elegant workarounds, but the question remains - why coot local
ignores preferences whenever you supply options in a command line? Bug
or feature?
Cheers,
Ed.
--
***************************************************
Dr. Bernhard Lohkamp
Assistant Professor
Div. Molecular Structural Biology
Dept. of Medical Biochemistry and Biophysics (MBB)
Karolinska Institutet
S-17177 Stockholm
Sweden
phone: (+46) 08-52487651
fax: (+46) 08-327626
email: [email protected]
