I noticed the Filter String in NSC Layout is not automatically updated when a new object is inserted in the NSC Editor. More specifically, I wonder why the object numbers are not updated automatically in the Filter String when a new object is inserted.
Is this something in the to-do list of Zemax developers? Or, instead, is auto-update unwanted for some reason?
Best answer by Kevin Scales
The filter string does not auto-update for the reasons alluded to. It is a bit of text that can be read and parsed into additional restrictions on the displayed data, and is stored and handled differently than parameters or properties. I couldn’t say why this is done this way, but I’m not aware of plans to change it.
+1It is certainly annoying that filter strings do not update when the NSC editor gets updated, and I don’t think there is anything in the help file indicating the filter strings do not update automatically. I don’t believe the filter string has any connection to the NSC Editor, but I have no idea how the Zemax OpticStudio source code actually works, so this is all just based on personal experience. Merit function, tolerance, multi-config operands, and pickups are all set up with an input for object number when appropriate. This makes it easy to be linked directly to the NSC editor, and update automatically with the NSC editor. Filter strings however, are just strings. In my primitive programming mind, I would imagine the steps to automatically update it would go something like this:
If the number of rows in the NSC editor changes: read the filter string, determine whether it contains a filter that corresponds to an object, extract the object number, compare it to the change in the NSC editor, determine whether a change to the filter string is necessary based on position in NSC editor, update filter string.
Could filter strings be handled differently? I don't know. I don't think a universal “Filter String Editor" would be the answer because you may want different filters for different detector objects, layout windows, ray trace, etc.
I am curious to know if anybody has a unique solution to this!
+1The filter string does not auto-update for the reasons alluded to. It is a bit of text that can be read and parsed into additional restrictions on the displayed data, and is stored and handled differently than parameters or properties. I couldn’t say why this is done this way, but I’m not aware of plans to change it.
Too bad there are no change plans.
Anyway, thank you both for your insights.
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.).
不要提供任何受适用法律，包括中华人民共和国的网络安全和数据安全法限制的信息或数据（如重要数据、国家核心数据等）。