Problems: Difference between revisions
m →Indexing failures: add links |
m fix typo JOBS= -> JOB= |
||
| (One intermediate revision by the same user not shown) | |||
| Line 253: | Line 253: | ||
It is a good idea to use many frames for the SPOT_RANGE, (e.g. the first half of the DATA_RANGE, as does the [[generate_XDS.INP]] script) for the COLSPOT and IDXREF steps. | It is a good idea to use many frames for the SPOT_RANGE, (e.g. the first half of the DATA_RANGE, as does the [[generate_XDS.INP]] script) for the COLSPOT and IDXREF steps. | ||
It is entirely possible to run COLSPOT for the ''complete'' DATA_RANGE (in that case the parameters of SPOT_RANGE are the same as for the DATA_RANGE), and to try smaller SPOT_RANGEs in IDXREF - this means COLSPOT has to be run only once, and the | It is entirely possible to run COLSPOT for the ''complete'' DATA_RANGE (in that case the parameters of SPOT_RANGE are the same as for the DATA_RANGE), and to try smaller SPOT_RANGEs in IDXREF - this means COLSPOT has to be run only once, and the JOB= line has e.g. | ||
JOB= IDXREF | |||
only. Maybe some SPOT_RANGE sub-range gives a clear answer. In that case it may be useful to use | only. Maybe some SPOT_RANGE sub-range gives a clear answer. In that case it may be useful to use | ||
REFINE(INTEGRATE)=! AXIS BEAM ORIENTATION CELL DISTANCE | REFINE(INTEGRATE)=! AXIS BEAM ORIENTATION CELL DISTANCE | ||
| Line 281: | Line 281: | ||
=== INTEGRATE stops with error message === | === INTEGRATE stops with error message === | ||
When using [[XDSGUI]], also inspect XDS.LP (to the right of the "Run XDS" button)! | |||
If INTEGRATE stops after e.g. | If INTEGRATE stops after e.g. | ||
****************************************************************************** | ****************************************************************************** | ||