Running scripts in the background
This information refers to Linux and Mac operative systems
The nohup command
The <t>nohup command allows to run a command in the background, in a fashion that interruptions of the connection will not terminate the job. The terminal containing the job might get closed and the job will still carry on. In order to keep track of the PID (process identifier) assigned by the process to the command launched, remember to use the & at the end of the line that invokes nohup, this will force the system to show the PID after launching the job. This PID might be needed to interrupt the execution of the background job.
Killing a background process
Use the command kill -9 followed by the PID of the process that you want to kill.
kill -9 12657
Retrieving the PID of your process
Use the pgrep command, followed by the command that you nohup-ed. For instance:
to locate PIDs that carry a MATLAB process. Note that in your system, capital letters might not apply
Running Matlab scripts
With a license
If you want to run the script myTest.m through nohup, the advised syntax is:
nohup -nosplash matlab < myTest.m > output.txt &
- no splash inhibited the popup of the Matlab welcome window
- output.txt is a text file that will catch the text that would be shown in the screen if the script would be ran directly (instead of through nohup).
With the standalone
You can replace matlab with dynamo, and use
nohup dynamo < myTest.m > output.txt &
in a terminal where you have activated Dynamo previously.
Matlab scripts including Dynamo commands
Remember that you need to include a line that activates 'Dynamo' inside the script that you submit into nohup. This is not necessary if you use the standalone with nohup dynamo < myTest.m > output.txt &
Running projects in the background
'Dynamo' projects can be run directly by nohup. A project script myProject.exe can be ran by