Use “qstat” (or qmon) to see the job waiting, then running, and once it’s finished, you should have several files in your output directory, including a. Your job 1886511 ('fdtd-mpi-example.sh') has been submitted Then, to run the job: scc ~ $ qsub job.sh Mpirun -mca btl_tcp_if_include eth0 -np $NSLOTS /ad/eng/opt/64/lumerical/mpitest/cpi-ompi-lcl

# This select Parallel Environment 'mpi' with 4 nodes There are many ways to invoke this and many options that you can pass, but here’s a simple example using Lumerical ompi test.įirst, the job script fdtd-mpi-example.sh is this: # This 'cwd' line will make sure to run from inside the current directory Now, we can run any MPI program we choose on any queue that has the “mpi” parallel environment configured, and Grid Engine will dynamically allocate hosts to the PE. If you are using lumerical device instead of lumerical fdtd, you will also have to load the lumerical/device module. OR you can use modules, like so: module use -s /ad/eng/etc/modulefiles (That’s covered here, but the link has the basic setup, before Lumerical.)įirst, ssh to the SCC and then run: export PATH=/ad/eng/bin:/ad/eng/bin/64/:$PATH

You must be set up to run MPI jobs with OpenMPI.

Note the publicly accessible MPI cluster on the ENG-Grid was retired in 2018.

You must already be using Engineering grid or SCC and successfully running test jobs.

See here for more information about setting up licensing for Lumerical.

Your username must be in an appropriate list on the Lumerical license server for you to receive a license.

Fdtd solutions