Guide Section: Couple EASA to a software application | EASAP Tree: PROCESSES
A PROCESS executes the commands that run underlying software applications.
A PROCESS is a parent for data manipulation objects (MAP, EXPAND and COMPUTE) and REPLACEMENT used to execute the process.
Run Using: specifies commands to run executables, to run scripts or to execute system commands.
Software: specifies which Compute Server to use, it may be a machine with MATLAB or other specialized software installed.
There is a pre-configured local Compute Server available called 'demo' which is used in Cantilever Plate Analysis (Introductory Batch).
If a PROCESS is linked to an object in the GUI, refresh the GUI each second by setting USER INTERFACE > Results Time: 1
![]() |
|
---|---|
Essential Parameters: | |
Object Name: | Enter a name for this object |
Run Using: | Enter a command to run a software application LIST and/or SCALAR references allowed |
Software: | Name of software to be run as specified in Compute Server Config Tool. |
Optional Parameters: | |
Run if: | Logical expression, if true then run process and not otherwise Default: true |
Delimiter: | Character to delimit a LIST or SCALAR reference in Run Using: |
Computational Dependencies: | Select from list of all available objects to track run time dependencies on these objects values. Object values must be real or integer numbers. Multiple selections allowed, but best if number of selections is less then 10. |
Status Text: | Text to display in the 'Status' column of Results pages instead of the usual % 'percentage completed' |
If a process is specific to either Windows or UNIX then the Software: must specify a Compute Server running that OS.
It is possible to run more than one command in a single PROCESS.
For Windows a double- ampersand ( && ) joins consecutive commands in Run Using:
For UNIX a semi-colon (;) joins consecutive commands.
Alternatively run a script file with multiple commands from Run Using:
After a PROCESS completes the Compute Server copies all files in the 'sim' folder back to the EASA Server.
A subsequent PROCESS copies these files back to the Computer Server, executes the PROCESS, then copies them back to the EASA Server upon completion.
Run multiple commands in a single PROCESS to lower file transfer overhead.
Additionally, add a final CLEAR FILESPACE to prevent temporary files from being copied back to the EASA Server.
Below we demonstrate a simple EASAP that will display in the GUI output from the 'dir' command run on the simulation folder: