Learning Forum

[smajety]

Hello,

I would like to run my simulations on the AWS cloud. I run FDTD simulations and convergence testing on photonic devices. I looked into the "Getting Started with AWS" article on Lumerical website but I did not find that quite helpful. Could you please help me with figuring out the most suitable use cases and on-demand plans?

Thank you!

[Lito]

From the getting started with AWS page, you will need to configure AWS and then you can create a Windows server instance with the resources (instance type) you require to run your simulation. Coordinate with your IT to allow access from your AWS instance to obtain the license from your license server on your local network. Once you have your Windows server instance, it would be like sunning your simulation from a local computer but with the resources required by the simulation. The following might be helpful: FDTD-Performance-Benchmarks and Determine optimum resource configuration to run your simulation.

[smajety]

Thank you for the response !
I am currently using a floating license (multiple licenses package) for running simulations on the desktop we have. Can we use the same floating license for running simulations on the AWS? Or do we need to purchase a node locked license to run simulations on AWS?
Please inform on this. Thank you!

[Lito]

You can use your existing license to run Lumerical on the cloud. You will have to consult with IT to allow your cloud compute instance/VMs access/obtain the license from your license server on your institution's local network. Otherwise, if you cannot connect/access your current license server, you will have to buy a separate set of licenses that will be running/hosted on the cloud.

[smajety]

I started using Lumerical on the AWS cloud and after I complete my simulation when I run a script to analyze the results, Lumerical crashes and shuts down. I have faced this issue before when using my desktop and back then you offered a solution to "Roll Back Drivers" under my display adapters in device manager. I tried to do the same thing now but the AWS instance does not have a dedicated display adapter. It has the "Microsoft Basic Display Adapter" and I am unable to do a Roll Back for this particular case. I am not sure why this is happening. Could you please offer a solution to this?
Thank you.

[Lito]

try to download the simulation/project to your local Windows Desktop and run the analysis script.

[smajety]

The issue is the simulations are run with a very dense mesh. Wouldn't it be hard to run the script on my local desktop. The reason for switching to AWS is the Desktop was not able to handle these files. Is this the only work around this problem?

[Guilin Sun]

You may try to copy the analysis script into an independent script file, modify it in your local machine and test it with the coarser mesh, make sure it works. Then run the same script file in AWS where the simulation uses necessarily dense mesh, and see if this independent script file works. Does the file crush when it runs locally with coarse mesh?
There are several different causes of the crushes of the simulated files. One might indicate the simulation settings are problematic; or the file its self may have crush-issues; it could be script issues; it could be memory issues even though there are lots of memory but the script usually runs in one processor, except for some farfield projection with multi-frequencies; project file created in one OS may not work well in the other platform due to some version issues or other unknown issues, and so on.
Please try and let us know your test results.

[smajety]

I copied the existing script to an new script file and saved it as a new file. I did this step both on AWS and my Desktop to generate two independent script files. Both versions of the independent script file was able to run analysis on my Desktop (with coarser mesh). Both versions of the same independent files are crashing Lumerical even when the script files are run for the coarser mesh case.
The file does not crash when run locally. It was crashing in the past and the problem back then was with the latest update of display drivers. When I rolled back the update, the files on my local computer stopped crashing.

[Guilin Sun]

"Both versions of the independent script file was able to run analysis on my Desktop (with coarser mesh)."
Only one version should work. Simply use one independent file.
"Both versions of the same independent files are crashing Lumerical even when the script files are run for the coarser mesh case." on what machine? AWS or local machine?
You may try a simple file downloaded from online example, with similar device, and the same analysis group, and run on AWS , and then see if it crushes.
You can also rebuild the project file on AWS and see if it works.