Indexing: Difference between revisions

385 bytes added ,  Wednesday at 15:32
→‎Indexing single images: remove, seems outdated
(→‎Indexing single images: remove, seems outdated)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Indexing single images ==
__TOC__


It may be advisable to increase INDEX_ERROR to (e.g.) a value of 0.2 (from its default of 0.05). This is because the 3-dimensional spotfinding in COLSPOT cannot produce a good phi estimate for the spots, so a larger error can be expected.  
Please also see [[IDXREF.LP]] !


== Indexing images from non-merohedrally twinned crystals (i.e. several lattices) ==
== Indexing images from non-merohedrally twinned crystals (i.e. several lattices) ==
Line 50: Line 50:
* just because XDS decides not to use some spots for indexing doesn't mean these initially non-indexed spots really belong to a separate lattice: compare the indexing/orientation matrices for the different solutions to see if they are significantly different (e.g. related by a one degree rotation). Also, check your images visually (ideally with the predictions on top) to make sure you acrtually have several lattices.
* just because XDS decides not to use some spots for indexing doesn't mean these initially non-indexed spots really belong to a separate lattice: compare the indexing/orientation matrices for the different solutions to see if they are significantly different (e.g. related by a one degree rotation). Also, check your images visually (ideally with the predictions on top) to make sure you acrtually have several lattices.
* the refinement of parameters (during the INTEGRATE step) can be very unstable: often, the spots of the two (or more) lattices are very close together: during data collection, some orientations of the spindle axis might make them move even closer until full overlap. At that point (or shortly after) the parameter refinement might 'jump' into the wrong lattice by chance. So look out for any jumps in parameters (distance, detector origina, scale, mosaicity etc), or prevent refinement of orientation in INTEGRATE altogether (REFINE(INTEGRATE)= without parameters).
* the refinement of parameters (during the INTEGRATE step) can be very unstable: often, the spots of the two (or more) lattices are very close together: during data collection, some orientations of the spindle axis might make them move even closer until full overlap. At that point (or shortly after) the parameter refinement might 'jump' into the wrong lattice by chance. So look out for any jumps in parameters (distance, detector origina, scale, mosaicity etc), or prevent refinement of orientation in INTEGRATE altogether (REFINE(INTEGRATE)= without parameters).
== Finding out the angular difference between two lattices ==
This can be easily found with "cmpmat" from [http://www.globalphasing.com/autoproc/ GlobalPhasing's autoPROC] package.
cmpmat 01/XPARM.XDS 02/XPARM.XDS P212121
would compare the orientations stored in 01/XPARM.XDS and 02/XPARM.XDS (assuming both were determined for space group P212121), and return the lowest angular difference from all combinations of symmetry-related crystal setting matrices.
  cmpmat 01/XPARM.XDS 02/XPARM.XDS P212121 -2
would return ''all'' angular differences, for ''all'' pairs of symmetry-related crystal setting matrices.
2,710

edits