Dynamo is distributed as a .tar package. After download, choose a location in your file system, which we will call DYNAMO_ROOT in this page.
Got to that location, i.e.
and untar the tar file with:
tar -xf dynamo-v-1.1.157_MCR-9.0.0_GLNXA64.tar
In general, you can install it to a different folder through the flag -C
tar -xf <absolute path to tar file> -C <DYNAMO_ROOT>
A general guide for installation can be found in the text file README.txt generated in the DYNAMO_ROOT folder.
The steps in this article are referred to the installation of Dynamo on a single machine with one or several CPUs. Please, note that further steps are needed for installation on GPU and/or a parallel cluster.
The distributed tar package should work out of the box, and be able to be run inside Matlab or as standalone executable.
The distributed tar package can be used under Matlab. The standalone versions for Mac in the Downloads area are not frequently updated.
Currently we do not offer support for windows.
Activating Dynamo in Matlab
After starting Matlab in a Linux or Mac machine, type inside the Matlab window:
This should work out of the box in Linux. Dynamo is now activated and the Matlab shell will recognize any Dynamo command. You can type for instance:
to see the general menu of options.
On a Mac
Dynamo will try to recompile part of its code in your Mac. This means that you need to have XCode installed (currently not a default setting in Apple computers!).
Activating Dynamo as standalone program
In a system shell, execute:
on a shell and be patient: the first time a shell initiates a Dynamo process, it can takes several minutes. New invocations to the MCR libraries will be much faster, and commands inside the opened Dynamo session will run immediately.
Technical information Dynamo is distributed with a version of the free Matlab MCR libraries, that's why the package is 2Gb... If you detect strange graphical behaviour on your system, you might want to use your own installation of the MCR. In such cases, you can activate Dynamo with
If you use your own MCR libraries, you should also make certain that the $LD_LIBRARY_PATH environment variable is correctly set to include all the elements of your MCR installation. Also, you need to make certain that you are using the same MCR version used by us during compilation time].