Tagged: fdtd, inverse-design, lumopt
-
-
August 3, 2022 at 8:46 pm
mo_911
SubscriberHello,
I just wanted to use the sample for "Inverse Design of a Splitter Using Topology Optimization" (https://optics.ansys.com/hc/en-us/articles/1500007182141).
According to the Lumerical's presentation file that I have attached below, the optimization depends on the initial conditions. So, I would like to change the initial condition as shown in the slide.
The initial conditions for "Filled", "Empty", and "Average" are available in the python script as I have attached the screenshot below. However, the initial condition for "Naive Splitter" is not available. How could I use "Naive Splitter" as an initial condition for both 2.5D and 3D optimizations? Sometimes this condition had the best solution.
-
August 4, 2022 at 5:20 pm
Taylor Robertson
Ansys EmployeeHello,
I believe that by the naive splitter you mean this sort of structure?
You can see that this structure, is actually part of a structure group with the name initial_guess. To define your own initial guess in a structure group of the exact same name. Then to use this as your starting point you set initial_cond = None in the python script. This is a special value that tells Python to mesh this structure and use this as a starting point, this is noted in the comments. You could also do this using an np array, but that would be a bit more challenging, because you need to match the simulation grid exactly.
Alternatively if you want to restart from a previous solution you could use the method outlined in optimization continuation.
Best Regards,
-
August 4, 2022 at 6:38 pm
mo_911
SubscriberHello,
Yes, this is what I wanted to do. Sorry, I overlooked the comments. In the python script "splitter_opt_2D_TE_topology_minfeaturesize.py", I set initial_cond = None. Then I was able to use the initial_guss structure as an initial guess for 2.5D topology optimization. Thank you for your help!
However, this method did not work for 3D optimization. In the python script "splitter_opt_3D_TE_topology_minfeaturesize.py", I set startingParams = None and set start_from_2d_result = False not to use the 2d result as shown below.
After running the python script, I got errors on the python terminal window as shown below. It looks like the FDTD grid and the initial_guess pixel size do not match. How can I resolve this mismatch?
-
August 25, 2022 at 5:50 pm
mo_911
SubscriberI am still wondering how to use a naive splitter as an initial guess for 3D topology optimization. As I told you, your sample python script is not working with this option.
I tried to use polygons defined by lsf script as an initial guess for 3D topology optimization, but I got an error as well.
-
- You must be logged in to reply to this topic.

Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.

Ansys Blog
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.
- “Import optical generation” or “delta generation rate”?
- Why am I getting “process exited without calling finalize”, and how do I fix it?
- Error on Lumerical device
- Using a license file on a new license server
- Error: addfdtd is not a valid function or a variable name
- Ansys Insight: Diverging Simulations
- Ansys Insight: Transmission results greater than one
- Ansys Insight: About override mesh in FDTD: its use and settings
- Ansys Insight: Convergence issues in CHARGE
- Is there a Lumerical script command to output the Simulation and Memory requirements?
-
2656
-
2120
-
1345
-
1118
-
461
© 2023 Copyright ANSYS, Inc. All rights reserved.