Skip to content

BleedingEdgeNews

JhanSrbinovsky edited this page May 5, 2013 · 15 revisions
  • [Jhan Srbinovsky, 18/12/12] It may need to be emphasised more strongly that whilst specific requirements of a user might suggest copying a tagged version from either tags or branches/Share directories in the repository, it is preferable to copy from the trunk to your user branch, before then checking out this copy to work with. The reason being that merging updates from the trunk to this working copy is far more straight forward, as is potential reintegration with the trunk.

  • [Jhan Srbinovsky, 18/12/12] see Ticket #11

  • [Jhan Srbinovsky, 07/03/13] Unfortunately I forgot about this space, and neglected to use it appropriately whilst the user guide was being updated. It is now uploaded. The modifications documented are science neutral. Apart from several minor bug fixes, the updates are to include the offline multi-processor drivers (MPI), a simple tool for testing bitwise reproducibility between revisions, and code added to report the version number of the code to the appropriate CABLE log file. Also, as CABLE is now a software group at NCI in its own right, there have been changes to the download procedure, and we no longer rely on the sharepoint site to include our non-ACCESS brethren.

PLEASE see the user guide for more details.

  • [Jhan Srbinovsky, 06/05/13] It is mentioned on the front page as well, but incase it was missed - Please don't forward the initial registration number given by NCI upon "receipt" of your application. They will forward an NCI identity of the form abc123 once your application has been "accepted".

  • [Jhan Srbinovsky, 06/05/13] The registration process may seem a little awkward, but please bear in mind that cable_help people are spread across various institutions.

Clone this wiki locally