Differences between revisions 2 and 4 (spanning 2 versions)
Revision 2 as of 2016-04-14 07:48:01
Size: 905
Editor: NicoleThomas
Comment:
Revision 4 as of 2020-08-10 10:03:33
Size: 914
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
The source code is under control of the CVS (Concurrent Version System) utility. To get the source code the environment variable CVSROOT must be set to ''/usr/nfs/local/archive''. The command The source code is hosted on the gitlab server gitlab.fz-juelich.de. The command
Line 8: Line 8:
cvs co messy-tools git clone git@gitlab.fz-juelich.de:clams/messy-tools.git <target-directory>
Line 10: Line 10:
creates a directory ''messy-tools'' in the current working directory and copies the current version of the package ''messy-tools'' to this directory. creates the target directory in the current working directory and copies the current version of the package ''messy-tools'' to this directory.
In case of access problems contact Nicole Thomas of jens-Uwe Grooß.

messy-tools

Check out source code

The source code is hosted on the gitlab server gitlab.fz-juelich.de. The command

git clone git@gitlab.fz-juelich.de:clams/messy-tools.git <target-directory>

creates the target directory in the current working directory and copies the current version of the package messy-tools to this directory. In case of access problems contact Nicole Thomas of jens-Uwe Grooß.

Tools

The package messy-tools contains the following programs:

  • messy-rm-mdi: Remove missing values in MESSy-CLaMS output file

  • messy2clams: Create CLaMS init file from MESSy-CLaMS output file

Compile

The programs can be compiled with the command

make progname

leading to an executable file with same name in the messy-tools directory.

Execute

progname input-file output-file

messy/MessyTools (last edited 2022-05-16 09:17:00 by NicoleThomas)