Lumerical FDTD

UCSB has a license for Lumerical's FDTD software (as well as DEVICE and MODE - see this page for how to run them).

To run on the head node, login with X forwarding (i.e. ssh -X) or use NX, then you start it with


or, better yet, you can add the following to your .bash_profile so that it's set to start correctly with the command 'fdtd-solutions'

source /sw/cnsi/lumerical/

When you're finished, please quit the program so other people can use it, we have a lot of licenses, but not unlimited, and it's a popular program.

To run in the queue, you set your project up with the gui, then submit with the command (if you didn't modify your .bash files, you'll need to use the full path, i.e. add /sw/cnsi/lumerical/fdtd/bin/  before the command names )- see for example

[pcw@knot ~/lumerical]$ fdtd-solutions 2d.fsp

[pcw@knot ~/lumerical]$ -n 8 2d.fsp



This will have submitted the job.  You can check on them with the 'qstat -u username' command, where you substitute your username in there so you only see your jobs.  

[pcw@knot ~/lumerical]$ qstat -u pcw


node96:                                                                                   Req'd    Req'd       Elap Job ID                  Username    Queue    Jobname          SessID  NDS   TSK   Memory   Time    S   Time ----------------------- ----------- -------- ---------------- ------ ----- ------ ------ --------- - --------- 580512.node96           pcw         batch               --      1      8  667mb  00:26:08 R  00:00:02


In this case it was run with 8 cores - that's the -n flag  (you can run it with up to 12 cores)

The last command 'qstat' shows you what the job is doing.  Once it shows C in the status column (in this example it's running 'R') you can open the fsp file with the GUI and do the analysis.


If you're getting errors about licenses being checked out - click here to see who is using it .