Suppose you are able to log on to the remote machine and suppose the machine is called, and your login there is myname (of course you will use real values instead of these). The other condition is: AMS must be installed on the remote machine and the commands that set up relevant environment variables must be present in the shell profile file, for example ~/.profile.
Unix/Linux users probably already know how to do this.
Detailed instructions for Windows users are available in the Readme.rtf document and in its PDF version DocInstallation_windows.pdf (both in the AMS installation folder). The common way for this is using public key authentication and the ssh-agent. The main condition is that you must be able to log on to the remote computer using ssh (or, on Windows, plink.exe) without being asked for any passwords or confirmations. There are some conditions that must be fulfilled however. It is easy to have your local GUI to set up and monitor jobs as well as visualize results, while submitting jobs to remote queues.Ī video shows how to set up remote queues on Windows. Scientists interested in further developing the Amsterdam Modeling Suite should e-mail us to discuss a possible collaboration with SCM, including a discounted (source code) license. Changes in the compiler flags, which have been carefully optimized for performance and robustness, are not recommended and the use of different compiler flags is at your own risk.
Only when you want to modify the source code to use non-standard options and features do you need to purchase the source code.
In this case we do not charge you for using the source code. If you are an experienced system administrator you can also compile AMS yourself e.g. Should the latest binary for your system not be available, we are happy to help you port it to your platform. The binaries are also shipped with linked-in mkl libraries, and are thoroughly tested against a test set before they are released. The binaries work out-of-the-box in parallel with fast interconnects through included MPI libraries or with the native parallel libraries (MPT, POE). We collaborate with all major hardware vendors to port and optimize our code on the most popular platforms.
No, usually you don’t need the source code. Similar requirements should hold for BAND (maybe you can benefit from even more disk space) and ReaxFF (less memory intensive than ADF). Make sure you download the Linux binaries optimized for AMD Zen. 4GB RAM per core and SSD are still recommended.
Update mid-2019: Rome, the latest Zen 2 AMD architecture (Epyc, 3rd generation Ryzen), give very good performance for ADF. For calculations on multiple nodes, get a fast interconnect (Infiniband). Using an SSD becomes more essential as the number of cores per node increases.
High-end workstation or a cluster: a dual-CPU Xeon SP setup with at least 2GB, but better 4GB, of RAM per core and an SSD. As of mid-2017, these configurations should give the best performance for ADF:ĭesktop or laptop: an Intel i7 processor from the latest generation, 16GB of RAM or more, and an SSD (a fusion drive may also work). Note that since chips are continuously improved, specific recommendations may change. run one process per floating point unit). Since floating-point performance is crucial for ADF, we do not recommend to use hyperthreading or use all Opteron logical cores (i.e. For the latest information, see our installation manual.īased on your budget, an older processor, 2GB of RAM per core and a standard hard drive may also be sufficient for running ADF jobs. See also the summary of a hardware FAQ session from October 2020. In general, the best hardware will be: the latest generation of processors, 4GB RAM per core and an SSD.