2,684
edits
(→Windows: update with info about CU of WSL) |
|||
Line 205: | Line 205: | ||
== Windows == | == Windows == | ||
The programs of the [[XDS]] package as well as [[XDSGUI]], [[XDSSTAT]], [[XDSCC12]] and so on may be run on 64bit | The programs of the [[XDS]] package as well as [[XDSGUI]], [[XDSSTAT]], [[XDSCC12]] and so on may be run on 64bit Windows 10 within the [http://www.pcworld.com/article/3050473/windows/heres-how-windows-10s-ubuntu-based-bash-shell-will-actually-work.html Linux Subsystem for Windows] (WSL). This (easily!) installs a Ubuntu 14.04.5 LTS environment, which supports the apt package manager, so in principle any software available for Ubuntu may be installed. | ||
[https://blogs.msdn.microsoft.com/commandline/2017/04/11/windows-10-creators-update-whats-new-in-bashwsl-windows-console/ Windows 10 Creators Update] (CU) allows to install (or update to) Ubuntu 16.04 , and fixes many bugs. | |||
Graphical Linux programs require installation of a X server like [https://sourceforge.net/projects/xming/files/latest/download Xming] on the Windows host. To use it, one has to say in the shell window | Graphical Linux programs require installation of a X server like [https://sourceforge.net/projects/xming/files/latest/download Xming] on the Windows host. To use it, one has to say in the shell window | ||
export DISPLAY=:0 | export DISPLAY=:0 | ||
before running the program. XDSGUI requires | before running the program. Running XDSGUI under WSL's Ubuntu 14.04 requires installation of a few packages with | ||
sudo apt-get install libgomp1 libqtgui4 | sudo apt-get install libgomp1 libqtgui4 | ||
and [[generate_XDS.INP]] requires a number of packages (some of which are only for specific detectors!); I'd start with | and [[generate_XDS.INP]] requires a number of packages (some of which are only for specific detectors!); I'd start with | ||
Line 215: | Line 217: | ||
and if required, also install python and hdf5-tools. | and if required, also install python and hdf5-tools. | ||
Unfortunately, only single-processor xds runs smoothly, whereas the parallel xds_par stops with an error message. | Unfortunately, only single-processor xds runs smoothly, whereas the parallel xds_par stops with an error message (supposedly fixed by the CU). The workaround is: | ||
* in XDS.INP, specify MAXIMUM_NUMBER_OF_JOBS= <number of cores> and MAXIMUM_NUMBER_OF_PROCESSORS=1 | |||
This will then use process-level parallelization instead of thread-level parallelization, and works rather well. | This will then use process-level parallelization instead of thread-level parallelization, and works rather well. | ||
XDSSTAT and the conversion to MTZ files by XDSCONV require a CCP4 installation. | XDSSTAT and the conversion to MTZ files by XDSCONV require a CCP4 installation accessible by WSL. In principle, CCP4 may be installed within WSL (have not tested this), or on the Windows host. |