2,684
edits
Problems: Difference between revisions
→XDS crashes
(→IDXREF ends with message: as confirmed with WK) |
|||
| Line 5: | Line 5: | ||
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. | ||
If it crashes for the second reason, there are | If it crashes for the second reason, there are four things to try/consider: | ||
* increase the stack limit of your shell, e.g. (if using csh or tcsh) with | * increase the stack limit of your shell, e.g. (if using csh or tcsh) with | ||
limit stacksize 102400 | limit stacksize 102400 | ||
| Line 11: | Line 11: | ||
ulimit -s 102400 | ulimit -s 102400 | ||
The numbers above mean a 10-fold increase over the default, and should be enough. I've found this to be necessary for unusually large frames (32 MB). | The numbers above mean a 10-fold increase over the default, and should be enough. I've found this to be necessary for unusually large frames (32 MB). | ||
* if you used xds when it crashes, try xds_par, and ''vice versa''. xds_par uses OpenMP for parallelization, which adds complexity. | * if you used xds when it crashes, try xds_par, and ''vice versa''. xds_par uses OpenMP for parallelization, which adds complexity. If it works with xds, bot not with xds_par, then the XDS developers would like to learn about this. | ||
* if the error message is | * if the error message is | ||
xds: Exec format error. Wrong Architecture. | xds: Exec format error. Wrong Architecture. | ||
make sure to use the 32bit version of XDS instead - you were trying to run the 64bit version on a 32bit operating system. | or | ||
-bash: /usr/local/bin/xds: cannot execute binary file | |||
make sure to use the 32bit version of XDS instead - you were trying to run the 64bit version on a 32bit operating system. | |||
* if the error message is | |||
forrtl: severe (168): Program Exception - illegal instruction | |||
Image PC Routine Line Source | |||
xds 08055250 Unknown Unknown Unknown | |||
xds 0804B3F6 Unknown Unknown Unknown | |||
this means that unfortunately the CPU of your machine is too old to be supported by XDS. This may happen e.g. with old AMD CPUs that don't support SSE2 (on Linux check the ''flags'' field of /proc/cpuinfo for the presence of the sse2 flag). Please find a newer machine - AMD is perfectly fine, but just not the oldest ones. | |||
== Indexing failures == | == Indexing failures == | ||