!!Execution requirements 

SimTree assumes and requires in its standard configuration the following system environment:

* In general, SimTree assumes a UNIX like system environment. Currently only
  Linux-Systems are supported. Using SimTree under Windows is not supported
  and support for this is not planned.

* SimTree is written in Java and requires a Java Runtime Environment (JRE)
  Version 1.6 or later. SimTree does not depend on external Java
  libraries besides the standard JRE 1.6 libraries.

* SimTree is provided as a Java jar-file. This jar file should be run by a script
  which calls the Java VM and transfers all commandline parameters to the executable.
  The script must be called SimTree because SimTree calls itself to execute
  simulation or collect processes. The script SimTree must be executable through
  the current PATH.

* SimTree uses a lot of internal assertions to check its correct operation.
  Setting the option -ea for the java VM is recommended. Please report
  all failed assertions as bug reports. 

* SimTree uses a UNIX-shell script template to execute a simulation or collect
  process and assumes that this template is executable on the local and - if
  required - on the remote host(s). The builtin default template may be replaced by
  a custom template (see intro-hooks).

* SimTree assumes that some commonly used programs are installed and executable
  (i.e. bzip2, rm). These programs are assumed to be in the current PATH. The
  programs may be replaced by setting according properties (see intro-properties).

* When using the feature to start simulation or collect processes on remote hosts
  (option [@o]--remote-process-slots) the following requirements must be fulfilled:

** The local host and the remote hosts(s) must share the StudyRoot in a common
   filesystem, i.e. by using NFS or CIFS.

** Starting a process on a remote hosts must be possible by using a ssh/rsh-like
   command (property CMD_REMOTE_SHELL). The called command interpreter on the
   remote host must understand the UNIX-shell syntax. A profile is executed on the
   remote host (property REMOTE_PROFILE_FNAME) before starting the simulation
   or collect process. This profile may be used to set PATHs and other system
   requirements.
   
. Some adaption to a different system environment may be possible by changing the
  hooks which are used to start a simulation remotely.
