aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas White <taw@physics.org>2013-02-15 11:55:54 +0100
committerThomas White <taw@physics.org>2013-02-15 11:55:54 +0100
commit51d15260fcadeccb9be481ff9807d023e05d4c6d (patch)
tree33ec155e9123e9c7703230e6c7f03a5fc9aa8750
parent45c2b8fa8c4ca803973876a01dccbf780482f6c4 (diff)
Add a small warning to the docs
-rw-r--r--doc/man/indexamajig.13
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/man/indexamajig.1 b/doc/man/indexamajig.1
index 1c525ad6..2f06d8d3 100644
--- a/doc/man/indexamajig.1
+++ b/doc/man/indexamajig.1
@@ -104,6 +104,9 @@ The default indexing method is 'none', which means no indexing will be done. Th
.PP
Your indexing methods will be checked for validity, incompatible flags removed, and warnings given about duplicates. For example, \fBmosflm\fR and \fBmosflm-comb-latt\fR represent the same indexing method, because \fB-comb\fR and \fB-latt\fR are the default behaviour for \fBmosflm\fR. The 'long version' of each of your indexing methods will be listed in the output, and the stream will contain a record of which indexing method successfully indexed each pattern.
+.PP
+It's risky to use \fBmosflm-nolatt\fR in conjunction with either \fB-comb\fR or \fB-axes\fR when you have a rhombohedral cell. This would be an odd thing to do anyway: why withhold the lattice information from MOSFLM if you know what it is, and want to use it to check the result? It's risky because MOSFLM will by default return the "H centered" lattice for your rhombohedral cell, and it's not completely certain that MOSFLM consistently uses one or other of the two possible conventions for the relationship between the "H" and "R" cells. It is, however, very likely that it does.
+
Examples of indexing methods: 'dirax,mosflm,reax', 'dirax-raw,mosflm-raw', 'dirax-raw-bad'.