Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
software:lumerical:caviness [2019-02-05 12:31] – ssunkara | software:lumerical:caviness [2019-02-06 12:05] (current) – ssunkara | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Lumerical on Caviness ====== | ====== Lumerical on Caviness ====== | ||
- | Lumerical requires user(s) to purchase a license in order to gain access to the license server to actually use the software. | + | Lumerical requires user(s) to purchase a license in order to gain access to the license server to actually use the software. |
- | The VALET packages for Lumerical are available to everyone on Caviness, and will load as expected. | + | <code bash> |
+ | export LM_LICENSE_FILE=port@hostname | ||
+ | </ | ||
+ | |||
+ | The VALET packages for Lumerical are available to everyone on Caviness and will load as expected. | ||
<code bash> | <code bash> | ||
Line 27: | Line 31: | ||
</ | </ | ||
+ | Lumerical FDTD does not come with MPI implementation integrated with the installation. Also, the MPI versions expected for the Latest FDTD software are way too older than the actual system-wide installations on Farber or Caviness. Therefore, UD IT made efforts to built suitable openMPI version within the Lumerical FDTD installation and made it available within the valet package. | ||
+ | |||
+ | <code bash> | ||
+ | | ||
+ | contexts: all | ||
+ | actions: { | ||
+ | PATH+=[: | ||
+ | LD_LIBRARY_PATH+=[: | ||
+ | LDFLAGS=+[ ]-L/ | ||
+ | MANPATH+=[: | ||
+ | CPPFLAGS=+[ ]-I/ | ||
+ | } | ||
+ | release 2019a R1 (8.21.1781) | ||
+ | prefix: / | ||
+ | standard paths: { | ||
+ | bin: / | ||
+ | lib: / | ||
+ | } | ||
+ | } | ||
+ | |||
+ | </ | ||
+ | |||
+ | <note important> | ||
+ | Given the older version of openMPI configured with Lumerical FDTD 2019, it does not have the capability to support the Lustre filesystem on Caviness. | ||
+ | </ | ||
+ | After loading the required valet package, one has to set the license file as mentioned above before attempting to run the actual programs. The ideal sequence of steps would be to determine the way(find the suitable commands from the documentation) to run an FDTD simulation on a generic Linux machine, try running that on Caviness and then set them up in a job script to make it run on the compute nodes. |