Notes for users of previous versions of SHARP/autoSHARP

If you're running any other version please ignore these notes (or get in contact with us if you still have questions).

• How can I find out which version I'm currently running?
  1. the SHARP version is printed at the top of each LIST.html file
  2. run the SHARP binary (in $BDG_home/bin/*_exe/sharp) with the -v command line flag
  3. the Sushi version is printed at the top of the "SHARP Control Panel" after you connect to the SHARP server
  4. the Sushi version is also in file $BDG_home/sushi/.version

• How can I find out which versions are available on this WWW server?

  You can find the versions of SHARP and Sushi available for download by following this link.

• Should I upgrade or just re-install?

  That depends on the amount of customization you've done with your existing server (and if you're prepared to redo this). In general, upgrading is less intrusive and should do the trick. But if you first want to check the new versions you can always install it in a fresh directory.

• What is the normal upgrade procedure?
  1. log into the account that your existing SHARP/autoSHARP server is installed under (probably your usual crystallographic software account).

  2. go to the SHARP server directory (what we call $BDG_home)

  3. after you got the latest versions of SHARP (sharp.*.tar.gz), Sushi (sushi.tar.gz), the tutorials (sharp_tutorials.tar.gz) and the installation script (installSHARP) :

     % chmod +x ./installSHARP
     % ./installSHARP -u         # answer all questions
     	    

  4. Sometimes it might be necessary to run a new setup script for all machines you have installed. This will clearly be stated in the release notes (that you'll find on the download page too).

     Alternatively, you can also run the upgrade using

     % chmod +x ./installSHARP
     % ./installSHARP -U         # answer all questions
     	    

     which will re-run the configuration of every machine.

  5. Sometimes it might be necessary for each SHARP user to re-run the useSHARP script. This will also be stated in the release notes.