2,652
edits
Problems: Difference between revisions
Jump to navigation
Jump to search
→XDS crashes
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
== XDS crashes == | == XDS crashes == | ||
XDS should never crash (if it terminates with an error message, this does not count as crash). If it does, it is either a bug in the program which should be brought to the attention of Wolfgang Kabsch or Kay Diederichs, and will be fixed, or it is a problem with your computer. | XDS should never crash (if it terminates with an error message, this does not count as crash). If it does, it is either a bug in the program which should be brought to the attention of Wolfgang Kabsch or Kay Diederichs, and will be fixed, or it is a problem with your computer, or (rarely) it is due to improper inputs ([[Problems#INTEGRATE_cell_and.2For_distance_run_away.3B_xds_crashes_or_has_to_be_killed|this]] is the only example I know of). | ||
If it crashes for the second reason, these are the things to try/consider: | If it crashes for the second reason, these are the things to try/consider: | ||
| Line 233: | Line 233: | ||
== Integration failure == | == Integration failure == | ||
=== INTEGRATE stops with error message === | |||
If INTEGRATE stops after e.g. | If INTEGRATE stops after e.g. | ||
****************************************************************************** | ****************************************************************************** | ||
| Line 263: | Line 264: | ||
DELPHI=20 ! default is 5, so try with e.g. 10, 20, 45, 90, 180 | DELPHI=20 ! default is 5, so try with e.g. 10, 20, 45, 90, 180 | ||
and re-run INTEGRATE. | and re-run INTEGRATE. | ||
=== INTEGRATE cell and/or distance run away; xds crashes or has to be killed === | |||
If during INTEGRATE the cell keeps increasing or the distance decreasing or both, then xds starts to consume large amounts of memory and becomes very slow. This may finally exhaust all available memory, and the job either crashes or has to be killed by the user. | |||
The fix here is to use | |||
REFINE(INTEGRATE)= BEAM POSITION ORIENTATION ! CELL | |||
instead of (what used to be the default until June 2017) | |||
REFINE(INTEGRATE)= BEAM POSITION ORIENTATION CELL | |||
Quite generally, the more conservative setting without CELL refinement is adequate unless your crystals diffract to quite high resolution. A sure sign that you should not be refining CELL is that the refined cell and/or distance values in INTEGRATE.LP fluctuate without obvious physical reason. Moreover, distance ("POSITION") refinement nicely soaks up any cell change resulting from radiation damage. | |||
A compromise (if you suspect that the cell parameters actually change ''differently'') would be | |||
REFINE(INTEGRATE)= BEAM ORIENTATION CELL ! POSITION | |||
This should also avoid the run-away but gives more freedom to the refinement. Of course it requires a refined distance (from IDXREF, or rather from GXPARM.XDS->XPARM.XDS renaming). | |||
== See also == | == See also == | ||