aboutsummaryrefslogtreecommitdiff
path: root/doc/man
diff options
context:
space:
mode:
authorThomas White <taw@physics.org>2014-04-09 15:25:17 +0200
committerThomas White <taw@physics.org>2014-04-09 15:25:17 +0200
commit11f6cfac04d54acf71f7c7a18fc05fc346ac888e (patch)
tree680f35efd6fe9f63f889934c8d42308ce68bd0d0 /doc/man
parent2dc09493d78eaa26f2f8a07bfdeb7b3f7a030fa4 (diff)
Remove vestigial "closer-peak" option
Diffstat (limited to 'doc/man')
-rw-r--r--doc/man/indexamajig.114
1 files changed, 0 insertions, 14 deletions
diff --git a/doc/man/indexamajig.1 b/doc/man/indexamajig.1
index ae71a571..124ee459 100644
--- a/doc/man/indexamajig.1
+++ b/doc/man/indexamajig.1
@@ -288,20 +288,6 @@ Run \fIn\fR analyses in parallel. Default: 1.
Don't attempt to correct the prefix (see \fB--prefix\fR) if it doesn't look correct.
.PD 0
-.IP \fB--closer-peak\fR
-.PD
-If you use this option, indexamajig will integrate around the location of a detected peak instead of the predicted peak location if one is found close to the predicted position, within ten pixels. \fBDon't use this option\fR, because
-there is currently no way to set the definition of 'nearby' to be appropriate
-for your data.
-
-.PD 0
-.IP \fB--no-closer-peak\fR
-.PD
-This is the opposite of \fB--closer-peak\fR, and is provided for compatibility
-with old scripts because this option selects the behaviour which is now the
-default.
-
-.PD 0
.IP \fB--no-use-saturated\fR
.PD
Normally, peaks which contain one or more pixels above max_adu (defined in the detector geometry file) will be used for indexing (but not used in the final integration - see the section on peak integration above). Using this option causes saturated peaks to be ignored completely. The opposite is \fB--use-saturated\fR, which is the default.