From a1e0854a972a988a7153df04f74dcee3ff9e75b9 Mon Sep 17 00:00:00 2001 From: Thomas White Date: Thu, 10 Jan 2013 13:49:11 +0100 Subject: indexamajig: Add --integrate-found --- doc/man/indexamajig.1 | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'doc/man') diff --git a/doc/man/indexamajig.1 b/doc/man/indexamajig.1 index 3519dc5f..9933627c 100644 --- a/doc/man/indexamajig.1 +++ b/doc/man/indexamajig.1 @@ -334,6 +334,11 @@ Normally, reflections which contain one or more pixels above max_adu (defined in .PD When using \fB--peaks=hdf5\fR, the peaks will be put through the same checks as if you were using \fB--peaks=zaef\fR. These checks reject peaks which are too close to panel edges, are saturated (unless you use \fB--use-saturated\fR), fall short of the minimum SNR value given by \fB--min-snr\fR, have other nearby peaks (closer than twice the inner integration radius, see \fB--int-radius\fR), or have any part in a bad region. Using this option skips this validation step, and uses the peaks directly. +.PD 0 +.IP \fB--integrate-found\fR +.PD +Without this option, peaks will be predicted in each pattern based on the crystal orientation from autoindexing and the parameters in the beam description file. With this option, indices will be assigned to the peaks found by the peak search, and the positions of those peaks used for the final integration stage. + .SH BUGS Don't run more than one indexamajig jobs simultaneously in the same working directory - they'll overwrite each other's DirAx or MOSFLM files, causing subtle -- cgit v1.2.3