TAGGED: fom, inverse-design, phase-change
-
-
February 19, 2025 at 6:54 pm
partha.nakti
SubscriberI have been working with the Lumerical FDTD and Lumopt API for my simulation setup, and I am currently using the ModeMatch function to set transmission as a figure of merit (FOM) for evaluating insertion loss. The code I’m using looks like this:
classlumopt.figures_of_merit.modematch.ModeMatch(monitor_name, mode_number, direction, multi_freq_src=False, target_T_fwd=
>, norm_p=1) As per the documentation, the
target_T_fwdparameter can be adjusted from 0 to 1 depending on the requirements, and thedirectionparameter can be set as either "forward" or "backward."However, I would like to know if it's possible to set the phase as the FOM instead of the transmission in Lumopt. I understand that phase can be extracted from a time monitor using Fourier transforms, as shown in the script below:
Ey = pinch(getdata("monitor","Ey"));
t = getdata("monitor","t");
f = linspace(c/1600e-9,c/1500e-9,100);
w = 2*pi*f;
Ew = czt(Ey,t,w)/sourcenorm(f);
phi = unwrap(angle(Ew));
plot(c/f*1e9,phi,"Wavelength(nm)","phase");This script successfully calculates the phase values. My question is: Does the Lumopt API allow for phase to be used as the figure of merit (FOM) in place of transmission, and if so, how can this be done?
I would greatly appreciate any insights or suggestions from the community regarding this matter.
Â
-
February 21, 2025 at 1:00 am
Kyle
Ansys EmployeeHello, phase is not a supported FOM for lumopt. The two figures of merit currently supported are:
- Power coupling of guided modes
- Light intensity over a surface or volume for a specified wavelength
If you'd like, you can submit a feature request on this topic here: Ideas
-
- You must be logged in to reply to this topic.
-
6745
-
1906
-
1484
-
1324
-
1047
© 2026 Copyright ANSYS, Inc. All rights reserved.