diff options
| author | Thomas White <taw@physics.org> | 2012-05-22 15:12:51 +0200 |
|---|---|---|
| committer | Thomas White <taw@physics.org> | 2012-05-22 15:12:51 +0200 |
| commit | 9af9d74f4d3260972566651f534e3e797da7543f (patch) | |
| tree | c9b79cbcb85eb93dc9e99babb405bd30c4d6bd10 /doc/man/indexamajig.1 | |
| parent | 8aae37896eab7414ab5f384e4152f72e57d0c788 (diff) | |
| parent | f080e3ac0a741e55d573e14c98c1e0250fb881df (diff) | |
Merge branch 'master' into tom/speed
Diffstat (limited to 'doc/man/indexamajig.1')
| -rw-r--r-- | doc/man/indexamajig.1 | 12 |
1 files changed, 10 insertions, 2 deletions
diff --git a/doc/man/indexamajig.1 b/doc/man/indexamajig.1 index ac443906..5bc3f7c0 100644 --- a/doc/man/indexamajig.1 +++ b/doc/man/indexamajig.1 @@ -216,7 +216,6 @@ these. The defaults are probably not appropriate for your situation. .PD The default is \fB--int-radius=4,5,7\fR. - .PD 0 .IP \fB--basename\fR .PD @@ -296,9 +295,18 @@ 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 -Normally, 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. This option disables this behaviour. Normally it doesn't make much difference either way. +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--insane\fR |