You are here

Lumerical FDTD Solutions

Finite-difference time-domain techniques primarily for electromagnetic propagation problems. 

The Lumerical Engine was formerly available to WestGrid users on the system, with a limit of 10 concurrent simulations. Through a donation from Lumerical, this license has been extended to the Orcinus cluster.

For details how to create the input file and analyze the data, please visit the Lumerical web site.

Restrictions / License Information

WestGrid no longer has the Shared User Interface license. It is up to the users to obtain a client license.

The CAD - FDTD Lumerical User Interface is not supported, please contact Lumerical for details.

Running Lumerical FDTD Solutions on Orcinus

An older example job submission script is available on Orcinus at


However, this script needs to be modified to reflect the current supported versions. An alternative to creating your own batch job script is to run, which is a script that automatically creates and submits a batch job script for each of one or more specified Lumerical .fsp files. Use the module command to set up the environment for the particular version of the FDTD Solutions software you want to use prior to running

module load lumerical -n number_of_processors project1.fsp project2.fsp ...

The script reads the .fsp files to extract information about memory and walltime requirements and substitutes these in a template batch job script (/global/software/FDTD_Solutions-8.7.3/templates/, to produce corresponding batch job files,, etc. in your directory. These scripts are then submitted as individual batch jobs, each to be run on the number of cores specified with the -n argument.

A more recent version of the software is available with

module load lumerical/8.11.337

The -n argument to the script is optional. If it is omitted, the jobs will be run using 8 cores. Also, with the default template file, the script uses the line

#PBS -l qos=parallel

The qos=parallel resource request is appropriate only when the number of cores requested is four or more. The job will generate an error if you try to use the request for jobs with smaller numbers of cores. You could edit the job scripts to remove that line if you wanted to use less than four cores and then manually submit the job with qsub:


A disadvantage of specifying more than one .fsp file on the command line is that the files from all the jobs will be written to the same directory. You may prefer to keep each job in a separate directory.

2017-11-27 - Corrected qsub command line from qsub project<n>.fsp to qsub project<n>.sh

System Orcinus
Version 8.7.3 / 8.11.337 6.0.3