Cheat sheet: Difference between revisions

(6 intermediate revisions by the same user not shown)

Line 1:

{| class="wikitable"

|+

!<big>XDS processing workflow</big>. The links given like e.g. [[XDSGUI#Frame]] refer to the XDSwiki at https://wiki.uni-konstanz.de/xds/index.php/

!<big>XDS processing workflow</big>. The links given like e.g. [[XDSGUI#Frame]] refer to the

XDSwiki at https://wiki.uni-konstanz.de/xds/index.php/

!The programs must have been properly installed - see [[Installation]]. Troubleshooting hints are at [[Problems]].

|-

Line 23:

Line 24:

|-

|'''4.''' '''Define untrusted detector areas.''' Mask the shaded regions of the detector: at least the beamstop and its holder. There is a button <code>Untrusted areas (...)</code> towards the upper right with three tools: UNTRUSTED_ELLIPSE, UNTRUSTED_RECTANGLE, UNTRUSTED_QUADRILATERAL

|This step is important, do not forget it! Reason is in the XDSGUI paper (reference ~~at the end~~). More explanation of the tools is at [[XDSGUI#Frame]] . ~~Wrongly placed UNTRUSTED~~ areas can be removed by deleting their lines in <code>XDS.INP</code> .

|This step is important, do not forget it! Reason is in the XDSGUI paper (reference below). More explanation of the tools is at [[XDSGUI#Frame]] . Unwanted UNTRUSTED_* areas can be removed by deleting their lines in <code>XDS.INP</code> .

|-

|'''5.''' '''Review and adjust XDS.INP.''' Go to the <code>XDS.INP</code> tab and inspect it. For a first XDS run, accept defaults, except increase MINIMUM_NUMBER_OF_PIXELS_IN_A_SPOT to 6 (rather than 3) for broad reflections with many pixels, i. In later runs, tweak parameters to optimize processing. JOB=XYCORR INIT COLSPOT IDXREF DEFPIX INTEGRATE CORRECT is only needed at the beginning i.e. for the first run.

|The paradigm of manual processing is to repeat INTEGRATE and CORRECT with ~~optimized~~ parameters that are available after a completed XDS run. ~~Please note~~ that geometry parameters ~~for~~ INTEGRATE are in <code>XPARM.XDS</code>, not in <code>XDS.INP</code> !

|The paradigm of manual processing is to repeat INTEGRATE and CORRECT with optimised parameters that are available after a completed XDS run. Note that geometry parameters used by INTEGRATE are in <code>XPARM.XDS</code>, not in <code>XDS.INP</code> !

|-

|'''6.''' '''Run XDS and handle errors.''' After changing <code>XDS.INP</code>, click <code>Save</code> (unless greyed out) and <code>Run XDS</code> . The tasks of the JOB keyword are run one after the other. Thus watch the adjacent tabs to the right flash yellow as they are being filled with text and graphics. Inspect the left (text) and right (graphics) sides of these tabs. Once the CORRECT tab is filled, the XDS run has completed, and the reflection file XDS_ASCII.HKL is available. The goal is to make sure that spacegroup and resolution are correct or at least reasonable, and that the processing is optimal.

|If XDS stops after the IDXREF step (with ERROR in IDXREF.LP), this most often happens because it could index less than 50% of the spots only. This may be due to ice rings that obviously cannot be indexed, or due to additional lattices. In most cases, this should at least prompt you to think about the possible reasons. To continue, set JOB=DEFPIX INTEGRATE CORRECT in ~~the~~ XDS.INP ~~tab~~, <code>Save</code> and <code>Run XDS</code>.

|If XDS stops after the IDXREF step (with ERROR in IDXREF.LP), this most often happens because it could index less than 50% of the spots only. This may be due to ice rings that obviously cannot be indexed, or due to additional lattices. In most cases, this should at least prompt you to think about the possible reasons. To continue, set JOB=DEFPIX INTEGRATE CORRECT in XDS.INP, <code>Save</code> and <code>Run XDS</code>.

|-

|'''7. First run of XDS: inspect and analyse diffraction.''' COLSPOT tab: is the "number of spots" evenly distributed among the frames? If not, it may be a sign of radiation damage or anisotropy, or plate-shaped crystal. Maybe see [https://wiki.uni-konstanz.de/xds/index.php?search=COLSPOT&title=Special%3ASearch&fulltext=1 COLSPOT] IDXREF tab: does the plot of spots appear elliptical - that would indicate anisotropy? Inspect the <code>predictions</code> in <code>Frame</code> . Do they match the observed reflections? ''Visualize reflections in reciprocal space'' : in <code>tools</code> go to <code>Further analyses</code> and click the second button from the top. This will load the indexed reflections (yellow) and non-indexed ones (pink) as pseudo-PDB files into <code>Coot</code>. Inspect the lattices: is the "yellow lattice" convincing, and/or do the pink reflections form their own lattice(s), or are they just random?

|'''7. First run of XDS: inspect and analyse diffraction.''' COLSPOT tab: is the "number of spots" evenly distributed among the frames? If not, it may be a sign of radiation damage or anisotropy, or plate-shaped crystal. Maybe see [https://wiki.uni-konstanz.de/xds/index.php?search=COLSPOT&title=Special%3ASearch&fulltext=1 COLSPOT] . IDXREF tab: does the plot of spots appear elliptical - that would indicate anisotropy? Inspect the <code>predictions</code> in <code>Frame</code> . Do they match the observed reflections? ''Visualize reflections in reciprocal space'' : in <code>tools</code> go to <code>Further analyses</code> and click the second button from the top. This will load the indexed reflections (yellow) and non-indexed ones (pink) as pseudo-PDB files into <code>Coot</code>. Inspect the lattices: is the "yellow lattice" convincing, and/or do the pink reflections form their own lattice(s), or are they just random?

|IDXREF tab: are the "CLUSTER INDICES" of the difference vectors integer numbers, or close to integers? Are the cell parameters reasonable? Is the first POPULATION of the first SUBTREE close to 3000? Ice rings? See [[IDXREF.LP]] and [[IDXREF]] .~~~~

|IDXREF tab: are the "CLUSTER INDICES" of the difference vectors integer numbers, or close to integers? Are the cell parameters reasonable? Is the first POPULATION of the first SUBTREE close to 3000? Ice rings? See [[IDXREF.LP]] and [[IDXREF]]. INTEGRATE tab: are the curves smooth (good) or are there jumps (bad)? Try to think of reasons for jumps/spikes! Could it be the beamline flux or the crystal changing? Are their straight red and green lines all along the "Beam divergence" and "Mosaicity" plots? If not, too few strong reflections were found (inspect the "THREE-DIMENSIONAL PROFILE" output in the text part) and you should add DELPHI=20 in <code>XDS.INP</code>, or increase the parameter if the keyword already exists.

~~~~INTEGRATE tab: are the curves smooth (good) or are there jumps (bad)? Try to think of reasons for jumps/spikes! Could it be the beamline flux or the crystal changing? Are their straight red and green lines all along the "Beam divergence" and "Mosaicity" plots? If not, too few strong reflections were found (inspect the "THREE-DIMENSIONAL PROFILE" output in the text part) and you should add DELPHI=20 in <code>XDS.INP</code>, or increase the parameter if the keyword already exists.

|-

|'''8.''' '''Inspect scaling & statistics.''' In the CORRECT tab: Numerical values and plots are only meaningful if the spacegroup is correct (screw axes don't matter for the statistics, though). If the spacegroup is unknown, the text part reports the spacegroup that XDS determines automatically. To benefit from a more advanced (but not infallible) algorithm, in <code>tools / Further analyses</code> use <code>determine spacegroups with pointless</code>. Output is in the terminal window! Modify the SPACE_GROUP_NUMBER and UNIT_CELL_CONSTANTS in <code>XDS.INP</code> accordingly (unless you know better, of course). Often there are two [[Space group determination#Space group selected by XDS: ambiguous with respect to enantiomorph and screw axes|enantiomorphic spacegroups]] possible ([[Space group determination#Table of space groups by Laue class and Bravais type|table]]), or a [[Space group determination#Subgroup and supergroup relations of these space groups|subgroup]] is correct; keep that in mind for the structure solution - the correct spacegroup is only confirmed when the structure is solved and well refined.

|The first look should go to the the first plot (I/sigma unmerged data). The red horizontal line is [[ISa]] - what is its value? The exact numerical value is in the text part, but the plot is enough for a good estimate. If the value is less than 5, something (likely indexing or spacegroup) is severely wrong. Good values are 20 and higher.

|The first look should go to the the first plot (I/sigma unmerged data). The red horizontal line is [[ISa]] - what is its value? The exact numerical value is in the text part, but the plot is enough for a good estimate. If the value is less than 5, something (likely indexing or spacegroup) is severely wrong. Good values are 20 and higher.

The blue line should be well below the red line, otherwise this is a sign of overexposure - in that case, the systematic error limits the quality of the data, not the random error.

The blue line should be well below the red line, otherwise this is a sign of overexposure - in that case, the systematic error limits the quality of the data, not the random error.

|-

|'''9.''' '''Spacegroup and resolution cutoff.''' If the spacegroup that CORRECT determined differs from the one that pointless determined, ~~CORRECT should be re-run:~~ change the JOB=... line to JOB=CORRECT, and ~~go to step 6.~~<~~/small~~><~~small~~>If the spacegroup is correct, decide about the high-resolution cutoff: go to the section after STATISTICS OF SAVED DATA SET "XDS_ASCII.HKL" and inspect the table SUBSET OF INTENSITY DATA WITH SIGNAL/NOISE >= -3.0 . A useful estimate of the high-resolution limit is the last resolution range that still gets a star "*" in the CC1/2 column; you may also consider the <nowiki><I/sigma> column. </nowiki>Put the upper resolution value into the INCLUDE_RESOLUTION_RANGE line in <code>XDS.INP</code>, and set JOB=CORRECT. Go to step 6.

|'''9.''' '''Spacegroup and resolution cutoff.''' If the spacegroup that CORRECT determined differs from the one that pointless determined: in <code>XDS.INP</code>, fix SPACE_GROUP_NUMBER and UNIT_CELL_CONSTANTS, change the JOB=... line to JOB=CORRECT, and <code>Run XDS</code>. If the spacegroup is correct, decide about the high-resolution cutoff: go to the section after STATISTICS OF SAVED DATA SET "XDS_ASCII.HKL" and inspect the table SUBSET OF INTENSITY DATA WITH SIGNAL/NOISE >= -3.0 . A useful estimate of the high-resolution limit is the last resolution range that still gets a star "*" in the CC1/2 column; you may also consider the <nowiki><I/sigma> column. </nowiki>Put the upper resolution value into the INCLUDE_RESOLUTION_RANGE line in <code>XDS.INP</code>, and set JOB=CORRECT. Go to step 6.

|Use FRIEDEL'_LAW=FALSE if the anomalous signal is so strong that you want to see the proper statistics (completeness ...). FRIEDEL'S_LAW= TRUE if scaling and merging should not take the anomalous signal into account. Low resolution anomalous correlation above 60% is what I consider strong. Modify <code>XDS.INP</code> accordingly.

|Use FRIEDEL'_LAW=FALSE if the anomalous signal is so strong that you want to see the proper statistics (completeness ...). Use FRIEDEL'S_LAW= TRUE if scaling and merging statistics should not take the anomalous signal into account. Low resolution anomalous correlation above 60% is what I consider strong. Modify <code>XDS.INP</code> accordingly.

|-

|'''10.''' '''Optimize by iterative comparison.''' Second and further runs of XDS typically refine the upper resolution limit and optimize the geometric parameters. It is useful to compare, after each modification, the resulting CORRECT.LP with the best one previously available. This is achieved by items in <code>tools / Saving and comparing good results</code> and <code>tools / Optimizing data quality</code>

|Thus, re-run INTEGRATE CORRECT or just CORRECT as needed (step 6). See [[Optimisation]], [[XDSGUI#How to use XDSGUI]]

|-

|'''11. Statistics tab.''' The XDSCC12 and XDSSTAT programs give you additional statistics for the frames of the DATA_RANGE.

|Look out for radiation damage. Bad frames have negative delta-CC1/2.

|-

|12. '''Creating MTZ file.''' Use the XDSCONV tab. Un-comment GENERATE_FRACTION_OF_TEST_REFLECTIONS=0.05 if you intend to use the MTZ file for refinement. '''To obtain a MTZ file from StarAniso''', use (in Tools/Further analyses/last line) the command "mkdir staraniso; cd staraniso; aP_scale -hkl ../XDS_ASCII.HKL; echo StarAniso is ready". Of course this requires that autoPROC is installed.

|FRIEDEL'S_LAW=FALSE is good even if little anomalous signal (FRIEDEL'S_LAW= TRUE in <code>XDS.INP</code>) since you may see metals or sulphur atoms in an anomalous map.

|}

The XDSGUI paper (Brehm, Triviño, Krahn, Usón and Diederichs (2023) XDSGUI: a graphical user interface for XDS, SHELX and ARCIMBOLDO. J. Appl. Cryst. 56) is open access at <nowiki>https://doi.org/10.1107/S1600576723007057</nowiki> .

@@ Line 1: / Line 1: @@
 {| class="wikitable"
 |+
-!<big>XDS processing workflow</big>. The links given like e.g. [[XDSGUI#Frame]] refer to the XDSwiki at https://wiki.uni-konstanz.de/xds/index.php/
+!<big>XDS processing workflow</big>. The links given like e.g. [[XDSGUI#Frame]] refer to the
+XDSwiki at https://wiki.uni-konstanz.de/xds/index.php/
 !The programs must have been properly installed - see [[Installation]]. Troubleshooting hints are at [[Problems]].
 |-
@@ Line 23: / Line 24: @@
 |-
 |<small>'''4.''' '''Define untrusted detector areas.''' Mask the shaded regions of the detector: at least the beamstop and its holder. There is a button <code>Untrusted areas (...)</code> towards the upper right with three tools: UNTRUSTED_ELLIPSE, UNTRUSTED_RECTANGLE, UNTRUSTED_QUADRILATERAL</small>
-|<small>This step is important, do not forget it! Reason is in the XDSGUI paper (reference at the end). More explanation of the tools is at [[XDSGUI#Frame]] . Wrongly placed UNTRUSTED areas can be removed by deleting their lines in <code>XDS.INP</code> .</small>
+|<small>This step is important, do not forget it! Reason is in the XDSGUI paper (reference below). More explanation of the tools is at [[XDSGUI#Frame]] . Unwanted UNTRUSTED_* areas can be removed by deleting their lines in <code>XDS.INP</code> .</small>
 |-
 |<small>'''5.''' '''Review and adjust XDS.INP.''' Go to the <code>XDS.INP</code> tab and inspect it. For a first XDS run, accept defaults, except increase MINIMUM_NUMBER_OF_PIXELS_IN_A_SPOT to 6 (rather than 3) for broad reflections with many pixels, i. In later runs, tweak parameters to optimize processing. JOB=XYCORR INIT COLSPOT IDXREF DEFPIX INTEGRATE CORRECT is only needed at the beginning i.e. for the first run.</small>
-|<small>The paradigm of manual processing is to repeat INTEGRATE and CORRECT with optimized parameters that are available after a completed XDS run. Please note that  geometry parameters for INTEGRATE are in <code>XPARM.XDS</code>, not in <code>XDS.INP</code> !</small>
+|<small>The paradigm of manual processing is to repeat INTEGRATE and CORRECT with optimised parameters that are available after a completed XDS run. Note that  geometry parameters used by INTEGRATE are in <code>XPARM.XDS</code>, not in <code>XDS.INP</code> !</small>
 |-
 |<small>'''6.''' '''Run XDS and handle errors.''' After changing <code>XDS.INP</code>, click <code>Save</code> (unless greyed out) and <code>Run XDS</code> . The tasks of the JOB keyword are run one after the other. Thus watch the adjacent tabs to the right flash yellow as they are being filled with text and graphics. Inspect the left (text) and right (graphics) sides of these tabs. Once the CORRECT tab is filled, the XDS run has completed, and the reflection file XDS_ASCII.HKL is available. The goal is to make sure that spacegroup and resolution are correct or at least reasonable, and that the processing is optimal.</small>
-|<small>If XDS stops after the IDXREF step (with ERROR in IDXREF.LP), this most often happens because it could index less than 50% of the spots only. This may be due to ice rings that obviously cannot be indexed, or due to additional lattices. In most cases, this should at least prompt you to think about the possible reasons. To continue, set JOB=DEFPIX INTEGRATE CORRECT in the XDS.INP tab, <code>Save</code> and <code>Run XDS</code>.</small>
+|<small>If XDS stops after the IDXREF step (with ERROR in IDXREF.LP), this most often happens because it could index less than 50% of the spots only. This may be due to ice rings that obviously cannot be indexed, or due to additional lattices. In most cases, this should at least prompt you to think about the possible reasons. To continue, set JOB=DEFPIX INTEGRATE CORRECT in XDS.INP, <code>Save</code> and <code>Run XDS</code>.</small>
 |-
-|<small>'''7.  First run of XDS: inspect and analyse diffraction.'''</small> <small>COLSPOT tab: is the "number of spots" evenly distributed among the frames? If not, it may be a sign of radiation damage or anisotropy, or plate-shaped crystal. Maybe see [https://wiki.uni-konstanz.de/xds/index.php?search=COLSPOT&title=Special%3ASearch&fulltext=1 COLSPOT]</small> <small>IDXREF tab: does the plot of spots appear elliptical - that would indicate anisotropy? Inspect the <code>predictions</code> in <code>Frame</code> . Do they match the observed reflections? ''Visualize reflections in reciprocal space'' : in <code>tools</code> go to <code>Further analyses</code> and click the second button from the top. This will load the indexed reflections (yellow) and non-indexed ones (pink) as pseudo-PDB files into <code>Coot</code>. Inspect the lattices: is the "yellow lattice" convincing, and/or do the pink reflections form their own lattice(s), or are they just random?</small>
+|<small>'''7.  First run of XDS: inspect and analyse diffraction.'''</small> <small>COLSPOT tab: is the "number of spots" evenly distributed among the frames? If not, it may be a sign of radiation damage or anisotropy, or plate-shaped crystal. Maybe see [https://wiki.uni-konstanz.de/xds/index.php?search=COLSPOT&title=Special%3ASearch&fulltext=1 COLSPOT]</small> . <small>IDXREF tab: does the plot of spots appear elliptical - that would indicate anisotropy? Inspect the <code>predictions</code> in <code>Frame</code> . Do they match the observed reflections? ''Visualize reflections in reciprocal space'' : in <code>tools</code> go to <code>Further analyses</code> and click the second button from the top. This will load the indexed reflections (yellow) and non-indexed ones (pink) as pseudo-PDB files into <code>Coot</code>. Inspect the lattices: is the "yellow lattice" convincing, and/or do the pink reflections form their own lattice(s), or are they just random?</small>
-|<small>IDXREF tab: are the "CLUSTER INDICES" of the difference vectors integer numbers, or close to integers? Are the cell parameters reasonable? Is the first POPULATION of the first SUBTREE close to 3000? Ice rings? See [[IDXREF.LP]] and [[IDXREF]] .</small>
+|<small>IDXREF tab: are the "CLUSTER INDICES" of the difference vectors integer numbers, or close to integers? Are the cell parameters reasonable? Is the first POPULATION of the first SUBTREE close to 3000? Ice rings? See [[IDXREF.LP]] and [[IDXREF]]. INTEGRATE tab: are the curves smooth (good) or are there jumps (bad)? Try to think of reasons for jumps/spikes! Could it be the beamline flux or the crystal changing? Are their straight red and green lines all along the "Beam divergence" and "Mosaicity" plots? If not, too few strong reflections were found (inspect the "THREE-DIMENSIONAL PROFILE" output in the text part) and you should add DELPHI=20 in <code>XDS.INP</code>, or increase the parameter if the keyword already exists.</small>
-<small>INTEGRATE tab: are the curves smooth (good) or are there jumps (bad)? Try to think of reasons for jumps/spikes! Could it be the beamline flux or the crystal changing? Are their straight red and green lines all along the "Beam divergence" and "Mosaicity" plots? If not, too few strong reflections were found (inspect the "THREE-DIMENSIONAL PROFILE" output in the text part) and you should add DELPHI=20 in <code>XDS.INP</code>, or increase the parameter if the keyword already exists.</small>
 |-
 |<small>'''8.''' '''Inspect scaling & statistics.''' In the CORRECT tab: Numerical values and plots are only meaningful if the spacegroup is correct (screw axes don't matter for the statistics, though). If the spacegroup is unknown, the text part reports the spacegroup that XDS determines automatically. To benefit from a more advanced  (but not infallible) algorithm, in <code>tools / Further analyses</code> use <code>determine spacegroups with pointless</code>. Output is in the terminal window! Modify the SPACE_GROUP_NUMBER and UNIT_CELL_CONSTANTS in <code>XDS.INP</code> accordingly (unless you know better, of course). Often there are two [[Space group determination#Space group selected by XDS: ambiguous with respect to enantiomorph and screw axes|enantiomorphic spacegroups]] possible ([[Space group determination#Table of space groups by Laue class and Bravais type|table]]), or a [[Space group determination#Subgroup and supergroup relations of these space groups|subgroup]] is correct; keep that in mind for the structure solution - the correct spacegroup is only confirmed when the structure is solved and well refined.</small>
-|The first look should go to the the first plot (I/sigma unmerged data). The red horizontal line is [[ISa]] - what is its value? The exact numerical value is in the text part, but the plot is enough for a good estimate. If the value is less than 5, something (likely indexing or spacegroup) is severely wrong. Good values are 20 and higher.
+|<small>The first look should go to the the first plot (I/sigma unmerged data). The red horizontal line is [[ISa]] - what is its value? The exact numerical value is in the text part, but the plot is enough for a good estimate. If the value is less than 5, something (likely indexing or spacegroup) is severely wrong. Good values are 20 and higher.</small>
-The blue line should be well below the red line, otherwise this is a sign of overexposure - in that case, the systematic error limits the quality of the data, not the random error.
+<small>The blue line should be well below the red line, otherwise this is a sign of overexposure - in that case, the systematic error limits the quality of the data, not the random error.</small>
 |-
-|<small>'''9.''' '''Spacegroup and resolution cutoff.''' If the spacegroup that CORRECT determined differs from the one that pointless determined, CORRECT should be re-run: change the JOB=... line to JOB=CORRECT, and go to step 6.</small><small>If the spacegroup is correct, decide about the high-resolution cutoff: go to the section after STATISTICS OF SAVED DATA SET "XDS_ASCII.HKL" and inspect the table SUBSET OF INTENSITY DATA WITH SIGNAL/NOISE >= -3.0 . A useful estimate of the high-resolution limit is the last resolution range that still gets a star "*" in the CC<sub>1/2</sub> column; you may also consider the <nowiki><I/sigma> column. </nowiki>Put the upper resolution value into the INCLUDE_RESOLUTION_RANGE line in <code>XDS.INP</code>, and set JOB=CORRECT. Go to step 6.</small>
+|<small>'''9.''' '''Spacegroup and resolution cutoff.''' If the spacegroup that CORRECT determined differs from the one that pointless determined: in <code>XDS.INP</code>, fix SPACE_GROUP_NUMBER and UNIT_CELL_CONSTANTS, change the JOB=... line to JOB=CORRECT, and <code>Run XDS</code>. If the spacegroup is correct, decide about the high-resolution cutoff: go to the section after STATISTICS OF SAVED DATA SET "XDS_ASCII.HKL" and inspect the table SUBSET OF INTENSITY DATA WITH SIGNAL/NOISE >= -3.0 . A useful estimate of the high-resolution limit is the last resolution range that still gets a star "*" in the CC<sub>1/2</sub> column; you may also consider the <nowiki><I/sigma> column. </nowiki>Put the upper resolution value into the INCLUDE_RESOLUTION_RANGE line in <code>XDS.INP</code>, and set JOB=CORRECT. Go to step 6.</small>
-|Use FRIEDEL'_LAW=FALSE if the anomalous signal is so strong that you want to see the proper statistics (completeness ...). FRIEDEL'S_LAW= TRUE if scaling and merging should not take the anomalous signal into account. Low resolution anomalous correlation above 60% is what I consider strong. Modify <code>XDS.INP</code> accordingly.
+|Use FRIEDEL'_LAW=FALSE if the anomalous signal is so strong that you want to see the proper statistics (completeness ...). Use FRIEDEL'S_LAW= TRUE if scaling and merging statistics should not take the anomalous signal into account. Low resolution anomalous correlation above 60% is what I consider strong. Modify <code>XDS.INP</code> accordingly.
 |-
 |<small>'''10.''' '''Optimize by iterative comparison.''' Second and further runs of XDS typically refine the upper resolution limit and optimize the geometric parameters. It is useful to compare, after each modification, the resulting CORRECT.LP with the best one previously available. This is achieved by items in <code>tools /  Saving and comparing good results</code> and <code>tools /  Optimizing data quality</code></small>
 |Thus, re-run INTEGRATE CORRECT or just CORRECT as needed (step 6). See [[Optimisation]], [[XDSGUI#How to use XDSGUI]]
+|-
+|<small>'''11. Statistics tab.''' The XDSCC12 and XDSSTAT programs give you additional statistics for the frames of the DATA_RANGE.</small>
+|<small>Look out for radiation damage. Bad frames have negative delta-CC<sub>1/2</sub>.</small>
+|-
+|<small>12. '''Creating MTZ file.''' Use the XDSCONV tab. Un-comment GENERATE_FRACTION_OF_TEST_REFLECTIONS=0.05 if you intend to use the MTZ file for refinement. '''To obtain a MTZ file from StarAniso''', use (in Tools/Further analyses/last line) the command "mkdir staraniso; cd staraniso; aP_scale -hkl ../XDS_ASCII.HKL; echo StarAniso is ready". Of course this requires that autoPROC is installed.</small>
+|<small>FRIEDEL'S_LAW=FALSE is good even if little anomalous signal (FRIEDEL'S_LAW= TRUE in <code>XDS.INP</code>) since you may see metals or sulphur atoms in an anomalous map.</small>
 |}
 The XDSGUI paper (Brehm, Triviño, Krahn, Usón and Diederichs (2023) XDSGUI: a graphical user interface for XDS, SHELX and ARCIMBOLDO. J. Appl. Cryst. 56) is open access at <nowiki>https://doi.org/10.1107/S1600576723007057</nowiki> .