I'll ask our Product team, and they will evaluate this as a potential feature request based on impact, difficulty to implement, and the number of users who request them.
Hi Alberto, The data displayed in the Sag Table Output text is hard coded into the program and currently there isn’t a way to specify the significant digits there. However, you can try to write a ZPL macro to loop over the surface X and Y coordinates and return the sag information with the Optimization Operand SSAG. Have a look at this article that explains how to get the value for an optimization operand in a macro. Then, in the macro, you can speficy the numerical precision with the keyword FORMAT: The Programming Tab > About the ZPL > KEYWORDS (about the zpl) > FORMAT Best, Berta
Hi Nadav, you can use TEZI to tolerance on surface irregularity. With this operand the max tolerance value is the exact RMS error of the surface in lens units, so you can convert from Angstrom to the lens units defined in your sytem. You can find an example of how to use this operand in this forum thread, as well as in this article. I hope this helps! :) Berta
Hi Matthias, You can no longer apply a Edge Thickness Solve in the Lens Data Editor if the surface thickness is also controlled using a Multi-Configuration Operand. However, you can use TSP1/TSP2/TSP3 to expose and control the thickness solve parameter previously set in the Lens Data Editor. So, for example, in the Edge Thickness Solve, TSP1 controls the thickness and TSP2 the radial height: Best, Berta
Thank you for starting this discussion! Along the lines of keeping track of the changes during the design process, I'd just like to share the method used by one of my colleagues
Hi Alberto, thank you for bringing this to our attention (and for the extra help googling around!). This was caused by a formatting bug when all values in one of the Tolerance Data Retention data series where zero. Our developers have been working on it and the issue has already been resolved.The fix will be included in our next service pack. Sorry about the inconveniences that this may have cause. Do not hesitate to get back to us should you need any further assistance!
In the meantime, you may switch to the "Classic View" tab: If you don’t have this tab, you will need to enable it in Setup > Project Preferences > Graphics Thanks for bringing this to our attention! :)
This error may be caused by your COATING.DAT file, so first thing I’d do is checking if this coating in actually in your coating file. To do it, go to Libraries > Coating Tools > Edit Coating file: The coating should appear at the bottom of the .DAT file. Once you have checked it, reload the Coating File and type the name (EO_MGF2(550NM)) in the Lens Data Editor coating cell. I’d also recommend to check that this file is in the folder \\Zemax\COATINGS, as appear in the Project Preferences, as well as the encrypted file EO_MGF2(550nm).ZEC. If not, I’d suggest to re-install OpticStudio. Find also attached a copy of the COATING.DAT file included in the latest release and the encrypted file, so you can copy it into the coating folder. To be safe, please backup copy your original COATING.DAT file to other folders.  
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.