Project Site

The sourceforge project site is

There is also additional documentation available from there under the Docs section.

Joining the JMulTi Project

Developers with a background in either Java or Gauss coding are more than welcome to join the team. It is also vital for the project to provide good documentation and to test the software. This work is highly appreciated as well.

Java programmers could work on new features or extend existing modules. The main work on the Java side is GUI design.

Numercial algorithms for JMulTi are currently mainly coded in Gauss, therefore experienced Gauss programmers are needed to maintain and improve the existing code base, as well as to provide new procedures.

Alternatively, numerical procedures could also be coded in R, Ox, C/C++, or Java. The underlying framework JStatCom allows to call such methods as well.

If you plan to join the JMulTi project, just send an email to the project admin.

Gauss Versions

JMulTi can run with the installed Gauss as well on Win32. For this jm.bat must be used to start the program with the option GRTE set to "false". This might be helpful to do changes in the Gauss code under jgauss/src or to test new procedures. In addition, the option DEBUG can be set to "true" to use the Gauss library system instead of the compiled GCG file. This is useful to test Gauss code changes on-the-fly without the need to restart JMulTi. The following tools are provided:

  • jgauss/jgauss_gcg.bat to compile the Gauss sources, it uses the config file jgauss/compile.xml in XML format
  • jgauss/jgauss_lib.bat to create LCG libraries from the Gauss sources, it uses the config file jgauss/lib.xml in XML format
However, it is important to note that the GRTE never uses the changed Gauss code. This is because compilation of a valid GCG file for this engine requires a GRTE license. For some more details, see the READMEs in the program, jgauss, and jgrte directories.

The following table is only relevant if an installed Gauss instead of the GRTE is used on Win32. Most Gauss versions are supported by the jgauss communication libraries. There are some problematic variants of the major releases that are listed below.

Version Comments
4.0 (probably only early releases) FOR loops index should not be referenced in method calls, only a copy of it, may cause problems occasionally, in general it is taken care of
3.2.19 (and earlier 3.2.x) FOR loops not supported, does not run
3.2.x (all Versions) 16 bit restrictions on directory names, do not use names with spaces or longer that 8 characters for the program directory as well as for the temporary directory (can be adjusted in xlm.cfg)
3.5.15 (and earlier 3.5.x) unresolved problem with VAR/VEC residual analysis, runs otherwise
3.6 jmulti.gcg file might be too big after compilation, remove files not needed from jgauss/compile.xml and run jgauss_gcg.bat, for example remove all files starting with cafp, they are needed for nonparametric analysis only
5.0 light does not include command line version tgauss.exe, not supported