Heidelberg Group Information

PRCS Repository

The MCTDH project is stored in a PRCS repository. The file prcs.cnf defines some environment variables needed by the PRCS program. To use the PRCS, add the following line to your .profile or .bashrc file.

PRCS checkin

Before one checks in into PRCS, the following steps should be taken.

0) Work on a Linux-PC, not on DEC, not on hitchcock.

1) Merge your code with the newest PRCS version, i.e. while being in your MCTDH directory type:
prcs merge mctdhall

2) If the conflict editor pops up, of course, remove the conflicts.

3) Run fcheck -s (or just fcheck) on a Linux-PC. Improve the code till fcheck is happy.

4) Run checkpop. If checkpop has found unpopulated files, inspect if you need to populate some of those. (See below).

5) Run the elk-test! Do so on a PC and on tarzan, using tarzan compiled code. It is also useful to run the elk-test with a debug code (i.e. mctdh83d or mctdh83D). If you are really nice, you run it even on an AIX.

6) Document your changes in the file changelog ($MCTDH_DIR/changelog). The script mchangelog makes it very simple to keep the correct format. If you have implemented new features, please document them also in $MCTDH_DIR/doc/mctdh/changes_docu.html (What's New).

7) Confirm that nobody has checked in after your merge. Otherwise go to 1).

8) While being in your MCTDH directory type:
prcs checkin mctdhall.
Answer e to the question of PRCS. Type some meaningful comments, describing the changes you have made. To end the comments, just type a dot followed by return. After the checkin is complete, type
prcs rekey mctdhall
in order to set the keys appropriately (e.g. ProjectHeader).

9) Send an e-mail to MCTDH-TC@listserv.uni-heidelberg.de to inform your colleges. (Only for larger changes).

If you have made very few local changes, it may be useful to check in a single file or a single directory. E.g:
prcs checkin mctdhall source/gendvr/init.F
or
prcs checkin mctdhall elk_inputs/

When you have created a new file, you have to populate it before checkin.
prcs populate mctdhall source/propwf/newfile.F
If everything had worked, PRCS will answer: One file added.

NEVER give the command
prcs populate mctdhall
i.e populate without a file name. This will populate all files, e.g. all binaries and object files. If you have done this mistake, DO NOT checkin but edit your mctdhall.prj file.

If you want to see the differences between your version and the last PRCS version type while being in your mctdh directory:
prcs diff -P -r83.@ mctdhall | less
One may have to replace -r83.@ by -r84.@ etc, when these versions exist. The symbol @ refers to the latest revision.

Preparing a Release

• The new name of the release has the form mctdh< version>release.revision, e.g. mctdh81.6 is version 8 release 1 revision 6.
• The release and revision numbers must match that specified in the source/include/versions.inc file. It is also written at the top of the user guide and on-line documentation. Check that User's Guide (PostScript) (edit doc/guide/guide.tex if wrong) and doc/index.html are correct.
• Run the script ~mctdh/bin/version_install. It checks out the last version from PRCS and installs it to /usr/people/mctdh and to /usr/people/WWW/mctdh/packages/ . The directory doc and the files guide.ps and guide.ps.gz on /usr/people/WWW/mctdh/ are renewed.