Content:
We try to keep these notes for the CCP4/Shanghai (October 2019) workshop up-to-date as we go along.
Remember, our software is usually run from the command-line (within a terminal). You should be reasonably familiar with some basic so-called shell commands - see e.g. also here.
To keep the different program and tutorial runs organised, it might be a good idea to run everything related to autoPROC in a separate directory, e.g. doing
mkdir ~/autoPROC cd ~/autoPROC
(the first command creates a sub-directory in your home directory and the second command changes your current working directory to that newly created one).
You should have a copy of the 2-sided autoPROC reference card in your handouts with the most commonly used command-line arguments. More details can be found in the online manual or locally here. The crucial bits to remember are:
There are some local example datasets available at
/home/ccp4admin/examples/mosflm/brazil
that can be used as examples for the different data processing tutorials during the workshop. After opening a terminal (click on the icon called "Terminal" on your desktop) you should be able to run autoPROC on these using e.g.
mkdir ~/autoPROC cd ~/autoPROC process -I /home/ccp4admin/examples/mosflm/brazil -d autoPROC.01 | tee autoPROC.01.lis
In a second terminal, open the summary.html file via
cd ~/autoPROC firefox autoPROC.01/summary.html
We will use this example during the practical tutorial - and then go through the output to show you the type of information provided by autoPROC processing with XDS, indication of possible problems,scaling, merging and anisotropy metrics.
This would not be fundamentally different to using the example/tutorial data mentioned above. Some additional care should be taken though - especially in checking for any beamline-specific settings.
For data collected on Monday, 13th October 2019 at the SSRF beamlines (during this workshop), please remember that the rotation axis needs to be defined as rotating the reverse way by adding the parameter ReverseRotationAxis=yes, e.g.
process ReverseRotationAxis=yes -I /where/ever/your/images -d autoPROC.01 > autoPROC.01.lis & firefox autoPROC.01/summary.html
If (a) the beamline/instrument you used for collecting your data is not listed, or (b) the instrumentation/setup has changed without us being aware of it and (c) data processing is not working, the most common reasons (apart from poor diffraction quality) are
Have a close look at the information provided by the summary.html file, especially any warning messages that might point to problems with diffraction, crystal, instrumentation or processing.