Compiling GMIN with CHARMM

So, you want to get the latest version of GMIN from the Wales Group repository. The GMIN code is managed by Subversion version control (SVN), and before you can access it, you need an account on the departmental SVN server.

Getting an account on the SVN server

The SVN server we use is run by the good people in the Unilever Centre, so you should email ucc-support@ch.cam.ac.uk, CCing in David (dw34) to request access to the Wales Group repository. Make sure you include your CRSID, the bit before @cam.ac.uk in your email address.

Once they reply, you should be able to set up your password here after logging into Raven. To check you have access to the repository, try logging in here. If you can't, you've done something wrong! Get help!

Setting up your SVN details

Open a shell on the machine where you plan on using GMIN. To make subversion easy to use, you need to specify some locations in your .bashrc file as environment variables. We do this as follows:

vi ~/.bashrc

This opens the vi editor. Press SHIFT+G to go to the bottom of the file, then press I to enter insert mode. Add the following to the bottom:

export SVN=https://wwmm.ch.cam.ac.uk/svn2/groups/wales/
export MYSVN=https://wwmm.ch.cam.ac.uk/svn2/users/CRSID/

where CRSID is the user name you use to log into Raven with. When you're done, we need to save he changes, press ESC to exit insert mode (check 'Insert' isn't still showing at the bottom!) and then type:

:wq

and press ENTER. This should exit the editor, and return you to the directory you were in before. These variables will now be automatically set when you open a new shell, but for now, we need to load them manually. We do this using the source command:

source ~/.bashrc

We're now ready to check if you have access to the repository from your chosen machine. Lets try listing the contents of the GMIN trunk directory. Type the following ($SVN is the environmental variable we set to the location of the Wales Group repository above):

svn ls $SVN/GMIN/trunk 

You will be prompted to validate a security certificate so press p and then ENTER to accept it permenantly. Now enter the password you set above (you only need to do this once!). You should see the files that make up GMIN displayed, ending in something like this:

... wenzel.f wham_djw.f90 zwischen.f

Congratulations! You're now good to download the GMIN code :)

'Checking out' the GMIN code

The first time you want to access the code, you need to 'check it out'. This will pull the entire code from the repository into a local directory for your use. For example,

svn co $SVN/GMIN/trunk ~/GMIN

You'll need to wait a while for the code to transfer! Once it has finished, you'll see a message like this:

Checked out revision 9853.

The number given is the version number you have just obtined. Whenever changes are make to the code and uploaded to the repository, this number is incremented. It might be increased by more than one between versions as the counter is common for all software, not just GMIN. That's it! You now have a copy of the GMIN code. Here are a few notes on its structure for new users.

• CHARMM31 contains the CHARMM source code. It was compiled before it was added to the repository using pgi64/7.1-6, so if the compiler used with GMIN is different, or even just a different version of Portland, you'll need to recompile it yourself before you compile GMIN with CHARMM.
• CHARMMinterface contains the CHARMM interface files which link GMIN to the CHARMM source. We try to change the CHARMM source itself as little as possible, so most changes are made here.
• AMBER contains the AMBER9 source code.
• AMH contains the files used for the AMH potential as implemented by Dr Mike Prentiss.