Optimisation: Difference between revisions
Line 7: | Line 7: | ||
== Final polishing == | == Final polishing == | ||
=== Re-INTEGATEing with the refined geometry === | === Re-INTEGATEing with the correct spacegroup and refined geometry === | ||
After running through all steps of XDS (including space group determination), one might want to | After running through all steps of XDS (including space group determination), one might want to | ||
cp GXPARM.XDS XPARM.XDS | cp GXPARM.XDS XPARM.XDS | ||
Line 15: | Line 15: | ||
echo "JOB=INTEGRATE CORRECT" >> XDS.INP | echo "JOB=INTEGRATE CORRECT" >> XDS.INP | ||
cat XDS.INP.new >> XDS.INP | cat XDS.INP.new >> XDS.INP | ||
and thereby re-run the INTEGRATE and CORRECT steps. This has the advantage that the refined geometry parameters (from CORRECT) are recycled into INTEGRATE, which sometimes leads to better R-factors. | and thereby re-run the INTEGRATE and CORRECT steps. This has the advantage that the refined geometry parameters (from CORRECT) are recycled into INTEGRATE, which sometimes leads to better R-factors. It also results in the spacegroup's restraints on the unit cell parameters being used for the prediction of spot positions; these are therefore slightly more accurate. | ||
=== Wilson outliers (aliens) === | === Wilson outliers (aliens) === |
Revision as of 17:37, 23 December 2007
General guidelines for obtaining a good result from XDS
- read the article XDS.INP
- for good indexing, follow XDS.INP#Keywords which affect whether indexing will succeed
- for good completeness read MINIMUM_ZETA
Final polishing
Re-INTEGATEing with the correct spacegroup and refined geometry
After running through all steps of XDS (including space group determination), one might want to
cp GXPARM.XDS XPARM.XDS mv CORRECT.LP CORRECT.LP.old egrep -v 'JOB|REIDX' XDS.INP > XDS.INP.new echo "! JOB=XYCORR INIT COLSPOT IDXREF DEFPIX INTEGRATE CORRECT" > XDS.INP echo "JOB=INTEGRATE CORRECT" >> XDS.INP cat XDS.INP.new >> XDS.INP
and thereby re-run the INTEGRATE and CORRECT steps. This has the advantage that the refined geometry parameters (from CORRECT) are recycled into INTEGRATE, which sometimes leads to better R-factors. It also results in the spacegroup's restraints on the unit cell parameters being used for the prediction of spot positions; these are therefore slightly more accurate.
Wilson outliers (aliens)
- Look through the list of reflections labeled as "aliens" at the bottom of CORRECT.LP. Decide whether they follow a slowly decaying non-Wilson distribution (resulting in many reflections with Z > 8 instead of almost none in the case of a Wilson distribution), or whether the top ones are true outliers. The latter arise most often from ice reflections (these may even be there when no ice rings are visible). Outliers should be put (i.e. copied) into REMOVE.HKL, and CORRECT then should be re-run.
My personal rule of thumb is that when the integer parts of Z ("int(Z)") are the numbers 8, 9, ... n, but there are no aliens (or just a single one) with int(Z) = n+1, then I consider all aliens with Z > n+1 as outliers.
A different rule of thumb would be to simply consider aliens with Z of 20 or more as outliers (see Wishlist). This may be accomplished by
awk '/alien/ { if (strtonum($5) > 19) print $0 }' CORRECT.LP >> REMOVE.HKL
It is useful to inspect the list of aliens after re-running CORRECT; maybe a few more of those should be put into REMOVE.HKL. But this process of rejecting Wilson outliers usually converges very quickly.
- Another way to judge Wilson outliers is to identify resolution ranges that deviate from 1. in the table HIGHER ORDER MOMENTS OF WILSON DISTRIBUTION OF ACENTRIC DATA in CORRECT.LP. "Aliens" that are put into REMOVE.HKL will lower the values in these resolution ranges!
- SCALEPACK users: don't confuse this process of rejecting Wilson outliers with the iterative procedure of rejecting scaling outliers that is usually done when using SCALEPACK. Scaling outliers are handled non-iteratively in XDS; the only way to influence XDS in this respect is by modifying WFAC1.
Optimizing the anomalous signal
Re-run CORRECT with FRIEDEL'S_LAW=TRUE, and read Tips_and_Tricks#SAD.2FMAD_data_reduction concerning STRICT_ABSORPTION_CORRECTION.