Last change: $Id: chapter_5.1.html 404 2009-11-04 09:44:42Z fuhrmann $
The PALM group announces code revisions by emails send to the PALM mailing list. If you like to be put on this list, just send an email to raasch@muk.uni-hannover.de. Details about new releases can be found in the technical/numerical documentation.
Generally, there are two ways of installing new / other versions. You can install a version from the list of available PALM releases or you can update your current installation with the newest developer version of PALM.
If you have previously checked out the most recent (at that time) PALM developer version by using
svn checkout ...../palm/trunk trunk ,
you can easily make an update to the newest version by changing into the working directory ~/palm/current_version and executing
svn update trunk
This updates all files in the PALM working copy in subdirectory trunk. The update may fail due the subversion rules, if you have modified the contents of trunk. In case of any conflicts with the repository, please refer to the subversion documentation on how to remove them. In order to avoid such conflicts, modifications of the default PALM code should be omitted and be restricted to the user-interface only (see chapter 3.5).
Alternatively, you can install new or other releases in a different directory, eg.
mkdir
~/palm/release-3.1c
cd
~/palm/release-3.1c
svn
checkout --username <your username>
svn://130.75.105.2/palm/tags/release-3.1c trunk
However, this would require to carry out again the complete installation process described in chapter 5.0. So far, differet versions of PALM cannot be used at the same time. The PALM releases from palm/tags never have to be updated with "svn update", since these releases are frozen!
After updating the working copy, please check for any differences between your current configuration file (.mrun.config) and the default configuration file under trunk/SCRIPTS/.mrun.config.default and adjust your current file, if neccessary.
The scripts and the pre-compiled code must then be updated via
or via
mbuild -u
mbuild
on all remote hosts listed in the configuration file .mrun.config.
You can use "subversion" for code comparison between the different versions. Also, modified code can be committed to the repository, but this is restricted to PALM developers.
As a last step, a suitable test run should be carried out. It should be carefully examined whether and how the results created by the new version differ from those of the old version. Possible discrepancies which go beyond the ones announced in the technical/numerical documentation should be communicated as soon as possible to the PALM group.
Last
change: $Id: chapter_5.1.html 404 2009-11-04 09:44:42Z fuhrmann $