Hi Martyn,
On Wed, 21 Dec 2011, [email protected] wrote:
Thanks for this. I have recently updated the CCP4-supplied dictionary to
include standard mmCIF, exchange dictionary, plus extra CCP4 items. This
will be in the next release. I was about to update cif2mtz to recognise
these extra columns. Will look at what you have done, may save me a job.
cif2mtz is based on the ccif library, which complains if you try to load a
cif file which contains a non-dictionary item. I'm sure in the past I
tried to find a way round this, and failed.
This can be done, at least to the extent that the non-dictionary item can be
ignored by the application rather than causing it to crash. (Reading data
values from the mmCIF does absolutely require the item to have been defined
in the dictionary though.) If you look at our suggested patch to cif2mtz to
allow reading the map coefficient data you will get a hint about how to do
this, or I can send details to you off-list or to ccp4-dev.
From the user point of view, the mmcif file is ascii and you can hand-edit
the column item names. This is the get-out method if cif2mtz fails. Edit
the item name to something that is recognised.
This is not ideal (says he, not having forgotten his own involvement here
:-)), and it is possible to imagine cases where this is not trivial to do
because of conflicting requirements of different dictionaries. That is not
intrinsic to the way that cif2mtz is written though, and could be fixed.
Regards,
Peter.
--
Peter Keller Tel.: +44 (0)1223 353033
Global Phasing Ltd., Fax.: +44 (0)1223 366889
Sheraton House,
Castle Park,
Cambridge CB3 0AX
United Kingdom
