Has anyone noticed any issues with using IGNM operand or any other operand in MFE?
I set IGNM of Surfaces A → B to “1”. And I sometimes see the rows disabled and other times not. There is something not quite right and I am not doing anything complex.
Feels like a bug. Can someone confirm here if there are experiencing the same?
Cheers!
Best answer by MichaelH
Hey Asuku,
Can you provide a little more context? What version of OpticStudio are you using? What other operands do you have in the MCE? How many configurations do you have? What surface type are you trying to ignore & is this the Stop surface? I remember some weird behavior like this before but I think this was many years ago.
When I try this on the Double Gauss using IGNM, I see the correct behavior using both OpticStudio 24R2 & 25R2.
+2Hey Asuku,
Can you provide a little more context? What version of OpticStudio are you using? What other operands do you have in the MCE? How many configurations do you have? What surface type are you trying to ignore & is this the Stop surface? I remember some weird behavior like this before but I think this was many years ago.
When I try this on the Double Gauss using IGNM, I see the correct behavior using both OpticStudio 24R2 & 25R2.
Hello
I had IGNM/IGNR operands defined for the same surface listed more than one time in the MFE, and as per documentation, only the last operand listed in the multi-configuration editor will be applied for the surface.
Once I corrected this, the problem disappeared. False alarm, OS IGNM/IGNR operands are behaving as expected. User error.
Cheers!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Do not provide any information or data that is restricted by applicable law, including by the People’s Republic of China’s Cybersecurity and Data Security Laws ( e.g., Important Data, National Core Data, etc.).
不要提供任何受适用法律，包括中华人民共和国的网络安全和数据安全法限制的信息或数据（如重要数据、国家核心数据等）。
