I would expect something like
/*/*/[F,PHI]
to work.
The reason for this notation was indeed that the dataset extension to
the MTZ format was designed to allow multiple columns with the same
names but different datasets. However, everyone else except for me
ignored the new spec, so in practice the feature seems to be redundant.
I've started implementing a 'legacy column mode' in the other clipper
apps - to allow something like F,PHI. We could extend that to coot.
Having said that, I've never used --data and don't know how it works, so
I may be talking out of my hat!
Nathaniel Echols wrote:
Is there a way to open map files from a script with the actual column
labels alone, instead of /crystal/dataset/F, etc.? I tried /*/*/F, but
this doesn't work in 0.6. One of my coworkers claims that MTZ files
don't allow duplicate column names regardless of which crystal or
dataset ID they're associated with, and in practice none of the programs
I've used output columns for more than one crystal/dataset anyway.
However, some of them *do* produce very different crystal or dataset
IDs - in some cases, it appears to be nearly random! Right now I have
to open up the MTZ file separately and figure out what they are, which
is a little more overhead than I'd like.
thanks,
Nat
