This is the Project Home Page for CCP4Forge project series-65.

Installing CCP4-6.5 with the i2 GUI

Mac OS X

• Download and open ccp4-6.5-i2-setup.dmg
• Launch ccp4 setup manager
• Proceed with ccp4 installation as usual
• On page 2, make sure that ccp4i2 box is ticked
• Updates for ccp4 core will be installed automatically
• For future ccp4 core updates: launch CCP4i, then CCP4i main window > Manage Updates etc.
• Launch ccp4i2: by default, the i2 icon is located in /Application/ccp4-6.5
  
• Update ccp4i2: Menu Bar > Utilities > Update CCP4I2; Update if prompted
• The ccp4i2 update may take some time because of installing demo data
• Restart ccp4i2
• Register at SHELX web-site
• Download shelxc, shelxd and shelxe, change permissions to executable and move to ccp4-6.5/bin

Linux

• Download and unpack ccp4-6.5-i2-setup-linux32.tgz or ccp4-6.5-i2-setup-linux64.tgz
• Launch ccp4 setup manager
• Proceed with ccp4 installation as usual
• On page 2, make sure that ccp4i2 box is ticked
• Updates for ccp4 core will be installed automatically
• For future ccp4 core updates: launch CCP4i, then CCP4i main window > Manage Updates etc.
• Launch ccp4i2: double-click the i2 icon on your Desktop
• Update ccp4i2: Menu Bar > Utilities > Update CCP4I2; Update if prompted
• The ccp4i2 update may take some time because of installing demo data
• Restart ccp4i2
• Register at SHELX web-site
• Download shelxc, shelxd and shelxe, change permissions to executable and move to ccp4-6.5/bin

Windows

• Download and unpack ccp4-6.5-i2.zip
• Launch ccp4i: open ccp4-6.5-i2 folder and double-click on ccp4i icon (this is a bat-file)
• You can also create a shortcut to ccp4i and put it on your Desktop
• Update ccp4 as usual: CCP4i main window > Manage Updates etc.
  
• Launch ccp4i2: in ccp4-6.5-i2 folder, double-click on ccp4i2 icon (this is a bat-file)
• You can also create a shortcut to ccp4i2 and put it on your Desktop
• Update ccp4i2: Menu Bar > Utilities > Update CCP4I2; Update if prompted
• The ccp4i2 update may take some time because of installing demo data
  
• Restart ccp4i2
  
• Register at SHELX web-site
• Download SHELX suite installer and run it
• Move shelxc.exe, shelxd.exe and shelxe.exe to CCP4/6.5/bin
• Install WinCoot

ccp4-6.5-i2 packages synced on 23 Mar 2015

Updating CCP4-6.5 with the i2 GUI

The ccp4-6.5-i2 distribution supersets the standard ccp4-6.5 distribution available from CCP4 Downloads. Accordingly, the extended distribution has two independent update systems. The first system is the same as for the standard distribution. The second system provides the fast track updates for i2 GUI only.

To fully update the ccp4-6.5-i2 installation you will need to apply both sets of updates:

• Launch ccp4i (the old GUI)
• Press Manage Updates button in the right bottom corner to launch the Update Manager
• Follow instructions in the Update Manager.
• Exit ccp4i or restart it if you want to continue using it.

• Launch ccp4i2 (the new GUI)
• Open update dialogue window (Menu Bar > Utilities > Update CCP4I2)
• The dialogue shows the current status of your installation. Press Update button if there are new updates.
• Restart ccp4i2

Alternatively, update your ccp4-6.5 + i2 installation from the command line, e.g.

/Applications/ccp4-6.5/bin/ccp4um -auto
/Applications/ccp4-6.5/bin/ccp4i2-update

Note: the full path is only needed if ccp4 setup scripts are not sourced.

Updates Tracker - notes for developers

Developers, who want to release updates to their software via ccp4 updates, are encouraged to provide required information using Tracker updates. (E-mail communication is of course possible as well).

Please initialise a new update request (press Submit New tab, which is just under the yellow Tracker tab), and then

• (+) select Component (component name = branch name in the series-65 repository)
• (+) select Platforms to which the new feature or fix applies
• (+) briefly comment on the new features or bug fixes (Summary text field)
• set Priority
• specify in Detailed Description text field:
• revisions to be pulled or merged from trunk to the release branch
• related revisions in other components / repositories
• any other relevant details

Once all this information is in place, the core group will know what to pull or merge from trunk to the release branch. In addition, the items marked by (+) in the above list will appear in the update manager and on-line.

Navigation (recommended route):

• CCP4Forge > tab My Page > section My Projects > link series-65 > section Public Areas > link updates
  

More details:

• Summary and Detailed Description text fields can be edited at any time. (Layouts of already existing and a newly created request pages are slightly different. In particular, note the Edit button next to Detailed Description label in the already existing request page).
• Please keep the default Priority of 3 for regular updates, set it to 5 for critical bug fixes and 1 for updates that can (or should) wait.
• The Assign To select box is there only because its presence is not configurable. Keep the default assignment to Nobody.
• State is managed by the core group
• Each change in a particular request triggers an E-mail to the person who submitted that request and to anyone who added a comment to it. [Stop] Monitor tab in the third row of tabs controls monitoring of the whole tracker, and the [Stop] Monitor link next to envelope icon controls monitoring of a particular request submitted by someone else.
  
• Currently, all past requests are visible in the default view of the Tracker page. In the future, the completed requests will be assigned status Closed and could be seen as follows. Select Simple Filtering and Sorting, select State Any and press Quick Browse.