2,652
edits
Problems: Difference between revisions
Jump to navigation
Jump to search
m
→IDXREF ends with !!! ERROR !!! message
(→64bit binary on a 32bit operating system: remove section about 32bit, and create new "frame numbers beyond 999999") |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 57: | Line 57: | ||
bash: export KMP_INIT_AT_FORK=FALSE | bash: export KMP_INIT_AT_FORK=FALSE | ||
tcsh: setenv KMP_INIT_AT_FORK FALSE | tcsh: setenv KMP_INIT_AT_FORK FALSE | ||
=== ASSERT VIOLATION === | === ASSERT VIOLATION === | ||
| Line 142: | Line 129: | ||
THE "DATA_RANGE=" IN FILE "XDS.INP" AND START ALL OVER AGAIN. | THE "DATA_RANGE=" IN FILE "XDS.INP" AND START ALL OVER AGAIN. | ||
This is printed out for you to actually read, and take action accordingly. In most cases you just change the JOB= line in XDS.INP to read | This is printed out for you to actually read, and take action accordingly: it may result from one or more additional crystals contributing to the diffraction patterns. Or it may just be the case that there are ice rings with very many isolated ice reflections (in that case you may want to use EXCLUDE_RESOLUTION_RANGE for the IDXREF task, or just to ignore the message and go on with JOB=DEFPIX INTEGRATE CORRECT). Or you have MINIMUM_NUMBER_OF_PIXELS_IN_A_SPOT of 3, but your reflections comprise many more pixels and COLSPOT may "see" several reflections when there's only one (in that case use MINIMUM_NUMBER_OF_PIXELS_IN_A_SPOT=6 or even 12). In most cases you just change the JOB= line in XDS.INP to read | ||
JOB= DEFPIX INTEGRATE CORRECT | JOB= DEFPIX INTEGRATE CORRECT | ||
and then continue to run XDS. In other cases you may want to change SPOT.XDS, or other keywords in [[XDS.INP]] (see also below). But in any case this is an important alert that should make you check the correctness of the parameters that describe the data collection (X-RAY_WAVELENGTH, DETECTOR_DISTANCE, ORGX, ORGY, OSCILLATION_RANGE, NAME_TEMPLATE_OF_DATA_FRAMES). | and then continue to run XDS. In other cases you may want to change SPOT.XDS, or other keywords in [[XDS.INP]] (see also below). But in any case this is an important alert that should make you check the correctness of the parameters that describe the data collection (X-RAY_WAVELENGTH, DETECTOR_DISTANCE, ORGX, ORGY, OSCILLATION_RANGE, NAME_TEMPLATE_OF_DATA_FRAMES). | ||
See also [[Problems#frame_numbers_beyond_999999]] below. | |||
=== IDXREF produces too short cell parameter(s) === | === IDXREF produces too short cell parameter(s) === | ||
| Line 265: | Line 254: | ||
A final possibility: your crystal may really be triclinic - hopefully you collected 180° of data, or even a bit more than that. | A final possibility: your crystal may really be triclinic - hopefully you collected 180° of data, or even a bit more than that. | ||
=== frame numbers beyond 999999 === | |||
If the number of question marks "?" in NAME_TEMPLATE_OF_DATA_FRAMES is larger than 6, to allow for e.g. | |||
DATA_RANGE= 1000001 10001000 | |||
then IDXREF cannot properly read SPOT.XDS written by COLSPOT, and stops with | |||
!!! ERROR !!! CANNOT READ SPOT.XDS | |||
This happens when the filenames of the frames have digits before the actual number, as in myframe1000001.cbf . | |||
The workaround is to specify e.g. | |||
NAME_TEMPLATE_OF_DATA_FRAMES=myframe100????.cbf | |||
DATA_RANGE=1 1000 | |||
(Problem reported by Pedro Dinis) | |||
== Integration failure == | == Integration failure == | ||