.\" .\" indexamajig man page .\" .\" Copyright © 2012-2013 Deutsches Elektronen-Synchrotron DESY, * a research centre of the Helmholtz Association. .\" .\" Part of CrystFEL - crystallography with a FEL .\" .TH INDEXAMAJIG 1 .SH NAME indexamajig \- bulk indexing and data reduction program .SH SYNOPSIS .PP .BR indexamajig \fB-i\fR \fIfilename\fR \fB-o\fR \fIoutput.stream\fR \fB-g\fR \fIdetector.geom\fR \fB-b\fR \fIbeamline.beam\fR \fB--peaks=\fR\fImethod\fR \fB--indexing=\fR\fImethod\fR [\fBoptions\fR] \fB...\fR .PP \fBindexamajig --help\fR .SH DESCRIPTION \fBindexamajig\fR takes a list of diffraction snapshots from crystals in random orientations and attempts to find peaks, index and integrate each one. The input is a list of diffraction image files in HDF5 format and some auxiliary files and parameters. The output is a long text file ('stream') containing the results from each image in turn. For minimal basic use, you need to provide the list of diffraction patterns, the method which will be used to index, a file describing the geometry of the detector, and a PDB file which contains the unit cell which will be used for the indexing. Here is what the minimal use might look like on the command line: .IP \fBindexamajig\fR .PD -i mypatterns.lst -j 10 -g mygeometry.geom --indexing=mosflm,dirax --peaks=hdf5 -b myxfel.beam -o test.stream -p mycell.pdb .PP More typical use includes all the above, but might also include extra parameters to modify the behaviour. The HDF5 files might be in some folder a long way from the current directory, so you might want to specify a full pathname to be added in front of each filename. You'll probably want to run more than one indexing job at a time (-j ). You can include a table of saturation values for in the HDF5 file, if you have a method for estimating the intensities of saturated peaks. It goes in /processing/hitfinder/peakinfo_saturated, and should be an n*3 two dimensional array, where the first two columns contain fast scan and slow scan coordinates (in that order) and the third contains the value which should belong in a peak at the given location. The value will be spread in a small cross centred on that location. See \fBman crystfel_geometry\fR for information about how to create a geometry description file and a beam parameters file. .SH PEAK DETECTION You can control the peak detection on the command line. Firstly, you can choose the peak detection method using \fB--peaks=\fR\fImethod\fR. Currently, two values for "method" are available. \fB--peaks=hdf5\fR will take the peak locations from the HDF5 file. It expects a two dimensional array at where size in the first dimension is the number of peaks and the size in the second dimension is three. The first two columns contain the fast scan and slow scan coordinates, the third contains the intensity. However, the intensity will be ignored since the pattern will always be re-integrated using the unit cell provided by the indexer on the basis of the peaks. You can tell indexamajig where to find this table inside each HDF5 file using \fB--hdf5-peaks=\fR\fIpath\fR. If you use \fB--peaks=zaef\fR, indexamajig will use a simple gradient search after Zaefferer (2000). You can control the overall threshold and minimum squared gradient for finding a peak using \fB--threshold\fR and \fB--min-gradient\fR. The threshold has arbitrary units matching the pixel values in the data, and the minimum gradient has the equivalent squared units. Peaks will be rejected if the 'foot point' is further away from the 'summit' of the peak by more than the inner integration radius (see below). They will also be rejected if the peak is closer than twice the inner integration radius from another peak. You can suppress peak detection altogether for a panel in the geometry file by specifying the "no_index" value for the panel as non-zero. .SH INDEXING METHODS You can choose between a variety of indexing methods. You can choose more than one method, in which case each method will be tried in turn until one of them reports that the pattern has been successfully indexed. Choose from: .IP \fBdirax\fR .PD Invoke DirAx, check linear combinations of the resulting cell axes for agreement with your cell, and then check that the cell accounts for at least half of the peaks from the peak search. .IP \fBmosflm\fR .PD As \fBdirax\fR, but invoke MOSFLM instead. If you provide a PDB file (with \fB-p\fR), the lattice type and centering information will be passed to MOSFLM, which will then return solutions which match. Note that the lattice parameter information will \fBnot\fR be given to MOSFLM, because it has no way to make use of it. .IP \fBreax\fR .PD Run the DPS algorithm, looking for the axes of your cell. .PP You can add one or more of the following to the above indexing methods: .IP \fB-raw\fR .PD Do not check the resulting unit cell. This option is useful when you need to determine the unit cell ab initio. Use with 'dirax' and 'mosflm' - the other indexing methods need the unit cell as input in any case, and cannot determine the unit cell ab initio. See \fB-comb\fR and \fB-axes\fR. .IP \fB-axes\fR .PD Check permutations of the axes for correspondence with your cell, but do not check linear combinations. This is useful to avoid a potential problem when one of the unit cell axis lengths is close to a multiple of one of the others. Can be used with \fBdirax\fR and \fBmosflm\fR. See \fB-raw\fR and \fB-comb\fR. .IP \fB-comb\fR .PD Check linear combinations of the unit cell basis vectors to see if a cell can be produced which looks like your unit cell. This is the default behaviour for \fBdirax\fR and \fBmosflm\fR. See \fB-raw\fR and \fB-axes\fR. .IP \fB-bad\fR .PD Do not check that the cell accounts for any of the peaks as described in \fBdirax\fR above. Might be useful to debug initial indexing problems, or if there are many multi-crystal patterns and the indexing method has no concept of multiple crystals per pattern (which, at the moment, means all of them). Can be used with any indexing method, but is generally a bad idea. .IP \fB-nolatt\fR .PD Do not use the lattice type information from the PDB file to help guide the indexing. Use with \fBmosflm\fR, which is the only indexing method which can optionally take advantage of this information. This is the default behaviour for \fBdirax\fR. This option makes no sense for \fBreax\fR, which is intrinsically based on using known lattice information. .IP \fB-latt\fR .PD This is the opposite of \fB-nolatt\fR, and is the default behaviour for \fBmosflm\fR and \fBreax\fR. .PP The default indexing method is 'none', which means no indexing will be done. This is useful if you just want to check that the peak detection is working properly. .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'. .SH PEAK INTEGRATION If the pattern could be successfully indexed, peaks will be predicted in the pattern and their intensities measured. The peak integration relies on knowing an accurate radius to integrate the peak within, and that the annulus used to estimate the background level is not so big that that it covers neighbouring peaks. However, indexamajig cannot (yet) determine these values for you. You need to specify them using the \fB--int-radius\fR option (see below). .PP To determine appropriate values, index some patterns with the default values and view the results using \fBcheck-near-bragg\fR (in the scripts folder). Set the binning in \fBhdfsee\fR to 1, and adjust the ring radius until none of the rings overlap for any of the patterns. This ring radius is the outer radius to use. Then reduce the radius until the circles match the sizes of the peaks as closely as possible. This value is the inner radius. The middle radius should be between the two, ideally between two and three pixels smaller than the outer radius. .PP If it's difficult to do this without setting the middle radius to the same value as the inner radius, then the peaks are too close together to be accurately integrated. Perhaps you got greedy with the resolution and put the detector too close to the interaction region? Improved integration algorithms, designed to handle such difficult cases, are under development. .SH OPTIONS .PD 0 .IP "\fB-i\fR \fIfilename\fR" .IP \fB--input=\fR\fIfilename\fR .PD Read the list of images to process from \fIfilename\fR. The default is \fB--input=-\fR, which means to read from stdin. .PD 0 .IP "\fB-o\fR \fIfilename\fR" .IP \fB--output=\fR\fIfilename\fR .PD Write the output data stream to \fIfilename\fR. The default is \fB--output=-\fR, which means to write to stdout. .PD 0 .IP \fB--peaks=\fR\fImethod\fR .PD Find peaks in the images using \fImethod\fR. See the second titled \fBPEAK DETECTION\fB (above) for more information. .PD 0 .IP \fB--indexing=\fR\fImethod\fR .PD Index the patterns using \fImethod\fR. See the section titled \fBINDEXING METHODS\fR (above) for more information. .PD 0 .IP "\fB-g\fR \fIfilename\fR" .IP \fB--geometry=\fR\fIfilename\fR .PD Read the detector geometry description from \fIfilename\fR. See \fBman crystfel_geometry\fR for more information. .PD 0 .IP "\fB-b\fR \fIfilename\fR" .IP \fB--beam=\fR\fIfilename\fR .PD Read the beam description from \fIfilename\fR. See \fBman crystfel_geometry\fR for more information. .PD 0 .IP "\fB-p\fR \fIfilename\fR" .IP \fB--pdb=\fR\fIfilename\fR .PD Read the unit cell for comparison from the CRYST1 line of the PDB file called \fIfilename\fR. .PD 0 .IP "\fB-e\fR \fIpath\fR" .IP \fB--image=\fR\fIpath\fR .PD Get the image data to display from \fIpath\fR inside the HDF5 file. For example: \fI/data/rawdata\fR. If this is not specified, the default behaviour is to use the first two-dimensional dataset with both dimensions greater than 64. .PD 0 .IP \fB--int-radius=\fR\fIinner,middle,outer\fR .PD Set the inner, middle and outer radii for three-ring integration. See the section about \fBPEAK INTEGRATION\fR, above, for details of how to determine 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 Remove the directory parts of the filenames taken from the input file. If \fB--prefix\fR or \fB-x\fR is also given, the directory parts of the filename will be removed \fIbefore\fR adding the prefix. .PD 0 .IP "\fB-x\fR \fIprefix\fR" .IP \fB--prefix=\fR\fIprefix\fR .PD Prefix the filenames from the input file with \fIprefix\fR. If \fB--basename\fR is also given, the filenames will be prefixed \fIafter\fR removing the directory parts of the filenames. .PD 0 .IP \fB--hdf5-peaks=\fR\fIpath\fR .PD When using \fB--peaks=hdf5\fR, read the peak locations from a table in the HDF5 file located at \fIpath\fR. .PD 0 .IP \fB--tolerance=\fR\fItol\fR .PD Set the tolerances for unit cell comparison. \fItol\fR takes the form \fIa\fR,\fIb\fR,\fIc\fR,\fIang\fR. \fIa\fR, \fIb\fR and \fIc\fR are the tolerances, in percent, for the respective direct space axes when using \fB-axes\fR in the indexing method (see below). \fIang\fR is the tolerance in degrees for the angles. When \fBnot\fR using \fB-axes\fR, they represent the respective \fIreciprocal\fR space parameters. Sorry for the horrifying inconsistency. .PD The default is \fB--tolerance=5,5,5,1.5\fR. .PD 0 .IP \fB--filter-cm\fR .PD Attempt to subtract common-mode noise from the image. The filtered image will be used for the final integration of the peaks (in contrast to \fB--filter-noise\fR. It is usually better to do a careful job of cleaning the images up before using indexamajig, so this option should not normally be used. .PD 0 .IP \fB--filter-noise\fR .PD Apply a noise filter to the image with checks 3x3 squares of pixels and sets all of them to zero if any of the nine pixels have a negative value. This filter may help with peak detection under certain circumstances, and the \fIunfiltered\fR image will be used for the final integration of the peaks. It is usually better to do a careful job of cleaning the images up before using indexamajig, so this option should not normally be used. .PD 0 .IP \fB--no-sat-corr\fR .PD This option is here for historical purposes only, to disable a correction which is done if certain extra information is included in the HDF5 file. .PD 0 .IP \fB--threshold=\fR\fIthres\fR .PD Set the overall threshold for peak detection using \fB--peaks=zaef\fR to \fIthres\fR, which has the same units as the detector data. The default is \fB--threshold=800\fR. .PD 0 .IP \fB--min-gradient=\fR\fIgrad\fR .PD Set the gradient threshold for peak detection using \fB--peaks=zaef\fR to \fIgrad\fR, which units of "detector units per pixel". The default is \fB--min-gradient=100000\fR. .PD 0 .IP \fB--min-snr=\fR\fIsnr\fR .PD Set the minimum I/sigma(I) for peak detection when using \fB--peaks=zaef\fR. The default is \fB--min-snr=5\fR. .PD 0 .IP \fB--min-integration-snr=\fR\fIsnr\fR .PD Set the minimum I/sigma(I) for a peak to be integrated successfully. The default is \fB--min-snr=-infinity\fR, i.e. no peaks are excluded. .PD 0 .IP \fB--copy-hdf5-field=\fR\fIpath\fR .PD Copy the information from \fIpath\fR in the HDF5 file into the output stream. The information must be a single scalar value. This option is sometimes useful to allow data to be separated after indexing according to some condition such the presence of an optical pump pulse. You can give this option as many times as you need to copy multiple bits of information. .PD 0 .IP \fB--verbose\fR .PD Be more verbose about indexing. .PD 0 .IP "\fB-j\fR \fIn\fR" .PD Run \fIn\fR analyses in parallel. Default: 1. .PD 0 .IP \fB--no-check-prefix\fR .PD 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-bg-sub\fR .PD Don't subtract local background estimates from integrated intensities. This is almost never useful, but might help to detect problems from troublesome background noise. .PD 0 .IP \fB--use-saturated\fR .PD Normally, peaks which contain one or more pixels above max_adu (defined in the detector geometry file) will not be used for indexing. Using this option skips this check, possibly improving the indexing rate if there is a large proportion of saturated peaks. .PD 0 .IP \fB--integrate-saturated\fR .PD Normally, reflections which contain one or more pixels above max_adu (defined in the detector geometry file) will not be integrated and written to the stream. Using this option skips this check, and allows saturated reflections to be passed to the later merging stages. This is not usually a good idea, but might be your only choice if there are many saturated reflections. .PD 0 .IP \fB--no-revalidate\fR .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 problems which can't easily be detected. .PP ReAx indexing is experimental. It works very nicely for some people, and crashes for others. In a future version, it will be improved and fully supported. .SH AUTHOR This page was written by Thomas White. .SH REPORTING BUGS Report bugs to , or visit . .SH COPYRIGHT AND DISCLAIMER Copyright © 2012-2013 Deutsches Elektronen-Synchrotron DESY, a research centre of the Helmholtz Association. .P indexamajig, and this manual, are part of CrystFEL. .P CrystFEL is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. .P CrystFEL is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. .P You should have received a copy of the GNU General Public License along with CrystFEL. If not, see . .SH SEE ALSO .BR crystfel (7), .BR crystfel_geometry (5), .BR process_hkl (1), .BR partialator (1)