2,652
edits
XDS.INP: Difference between revisions
Jump to navigation
Jump to search
→Keywords which affect the speed of data reduction
| (One intermediate revision by the same user not shown) | |||
| Line 107: | Line 107: | ||
;[http://xds.mpimf-heidelberg.mpg.de/html_doc/xds_parameters.html#MAXIMUM_NUMBER_OF_JOBS= MAXIMUM_NUMBER_OF_JOBS] | ;[http://xds.mpimf-heidelberg.mpg.de/html_doc/xds_parameters.html#MAXIMUM_NUMBER_OF_JOBS= MAXIMUM_NUMBER_OF_JOBS] | ||
:speeds up XDS by chopping the DATA_RANGE into (2-99) pieces, and feeding each piece to a new process. That process may run on the local machine, or a different one (but this needs to be configured). | :speeds up XDS by chopping the DATA_RANGE into (2-99) pieces, and feeding each piece to a new process. That process may run on the local machine, or a different one (but this needs to be configured). | ||
Some amount of "overcommiting of resources" is OK, i.e. if you are the sole user of a Dual-core workstation, you may set both parameters to 2. Wolfgang Kabsch found that this utilizes the machine even a bit better than either MAXIMUM_NUMBER_OF_PROCESSORS=2 or MAXIMUM_NUMBER_OF_JOBS=2. | Some amount of "overcommiting of resources" is OK, i.e. if you are the sole user of a Dual-core workstation, you may set both parameters to 2. Wolfgang Kabsch found that this utilizes the machine even a bit better than either MAXIMUM_NUMBER_OF_PROCESSORS=2 or MAXIMUM_NUMBER_OF_JOBS=2. | ||
| Line 121: | Line 121: | ||
The most important possible pitfalls are: | The most important possible pitfalls are: | ||
* | * Blanks in the parameter of the NAME_TEMPLATE_OF_DATA_FRAMES keyword. Fix: use a symlink to the directory with the frames. | ||
* Error due to omitting the "=" directly after the keyword (i.e. having an intervening blank). | * Error due to omitting the "=" directly after the keyword (i.e. having an intervening blank). | ||