Automatic local launch

By default the ACSI will prompt the user to launch the co-simulating processes manually. However, options execution_command and working_directory may be used to have the ACSI launch the co-simulating processes automatically. Any Adams, Marc or EDEM process may be launched automatically as long as all processes (ACSI glue code, Adams, Marc and EDEM) are running on the same host.

The new options execution_command and working_directory are optional. If a process group does not have the execution_command option, then the ACSI will prompt the user to launch the code manually. The co-simulation accepts processes manually launched as well as processes automatically launched on the same job.

The execution_command option must include the full path to the executable, optional flags and the name of the model. For example, in a Linux environment you may type the following to launch EDEM:

While in Windows you may enter:

Notice that in Windows you may enter blank spaces if needed. Do not place quotes or escape characters.

The execution command may include a final redirection to a file, for instance:

The execution command must be a single execution command without pipes. Compound commands are not supported. Here is an example of a not supported compound command:

Similarly, option working_directory should define the full path to the working directory. In a Linux environment you may type:

In a Windows environment you may type:

Notice that blank spaces are allowed. Do not use quotes or escape characters to define the paths.

Both the execution_command and working_directory options support the use of environment variables. Environment variables must be entered using any of the following two formats: ${NAME} or %NAME% regardless of the architecture. NAME stands for the name of the environment variable.