Indexing: Difference between revisions

Jump to navigation Jump to search
677 bytes added ,  21 May 2014
no edit summary
(INDEX_ERROR)
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
Please also see [[IDXREF.LP]] !
__TOC__
== Indexing single images ==
== Indexing single images ==


Line 15: Line 19:


'''3.''' split the indexed/non-indexed spots:
'''3.''' split the indexed/non-indexed spots:
  % grep " 0      0      0" SPOT.XDS > SPOT.XDS_bad
  % grep " 0 0 0" SPOT.XDS > SPOT.XDS_bad
  % grep -v " 0       0       0" SPOT.XDS > SPOT.XDS_good
% # for old XDS versions use: grep " 0      0      0" SPOT.XDS > SPOT.XDS_bad
  % grep -v " 0 0 0" SPOT.XDS > SPOT.XDS_good
  % mv SPOT.XDS SPOT.XDS_orig
  % mv SPOT.XDS SPOT.XDS_orig
  % cp -p SPOT.XDS_good SPOT.XDS
  % cp -p SPOT.XDS_good SPOT.XDS
Line 22: Line 27:
  % xds
  % xds
Now you have (basically) indexed lattice 1. You could repeat this step a bit further:
Now you have (basically) indexed lattice 1. You could repeat this step a bit further:
  % grep  -v " 0       0       0" SPOT.XDS > SPOT.XDS_tmp
  % grep  -v " 0 0 0" SPOT.XDS > SPOT.XDS_tmp
  % mv SPOT.XDS_tmp SPOT.XDS
  % mv SPOT.XDS_tmp SPOT.XDS
  % xds
  % xds
Line 34: Line 39:
  % xds
  % xds
Are there still too many spots rejected? Check with
Are there still too many spots rejected? Check with
  % grep -c " 0       0       0" SPOT.XDS    # gives non-indexed spots
  % grep -c " 0 0 0" SPOT.XDS    # gives non-indexed spots
  % grep -vc " 0       0       0" SPOT.XDS  # gives indexed spots
  % grep -vc " 0 0 0" SPOT.XDS  # gives indexed spots
Maybe you have a third (fourth etc) lattice? Then repeat step 3 for this one ... etc
Maybe you have a third (fourth etc) lattice? Then repeat step 3 for this one ... etc


Line 49: Line 54:
* 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,652

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu