Photonics

Photonics

Topics related to Lumerical and more

setmaterial command not working as expected in Lumerical 2023 R2.2

    • Jared Sisler
      Subscriber
    • Amrita Pati
      Ansys Employee

      Hi Jared,

      Would you be able to provide more details? Screenshots would be useful as well. Thank you!

      Regards,
      Amrita

    • Jared Sisler
      Subscriber

      Woah, sorry, somehow the body of my post got lost. Let's try again. Thanks for your help!

      When I run the following script in Lumerical 2022 R2.3, it runs as expected by creating a new material with Re(index xx) = 2, Re(index yy) = 3, Re(index zz) = 4. However, when I run it in Lumerical 2023 R2.2, it creates a new material with Re(index xx) = 2, Re(index yy) = 2, Re(index zz) = 2. (All imaginary parts are 0 in both cases) Is this a bug or is there a change in how I need to define the index of a diagonal, anisotropic material? Thanks!

      permittivity = [c/1e-6, 4+1i*0, 9+1i*0, 16+1i*0]
      temp = addmaterial("Sampled 3D data");
      setmaterial(temp,"name","TestMat");
      setmaterial("TestMat","Anisotropy","Diagonal");
      setmaterial("TestMat","sampled data", permittivity);

    • Amrita Pati
      Ansys Employee

      Hi Jared,

      It indeed seems to be a bug. We tested it in 2022 R2.3, 2023 R1.3, and 2023 R2.2. It works well in the first two releases. In the latest release, it sometimes shows unexpected behavior as you reported. On other ocassions FDTD just crashes. I am reporting this as a bug. I will keep you posted on the updates. Thanks for brining this to our attention.

      Regards,
      Amrita

    • Jared Sisler
      Subscriber

      Hi Amrita,

      Thanks for the response and confirming that it is indeed a bug. Do you know the rough timeline in which this issue can be resolved?

      Thanks,
      Jared

    • Amrita Pati
      Ansys Employee

      Hi Jared,

      It is hard to tell when it would be fixed at this stage. We may have a target fix release over the next few days once the bug has been triaged. It also varies from bug to bug. I will let you know when I have more information.

      I was also checking if there is a workaround. Importing the data in a text file using the GUI is working (Creating new sampled data materials in FDTD). I know a lot of people rely on scripts to generate automated simulation workflows and the script command not working can stand in the way of that. But would you be able to give the GUI a try and check if it would work for your simulation for now? Thank you.

      Regards,
      Amrita

Viewing 5 reply threads
  • You must be logged in to reply to this topic.