Hello Experts,I am trying to compare a Shack Hartmann wavefront measurement with my Zemax wavefront map.Image depicting the measurement setup from the website of the Shack Hartmann Sensor manufacturer (Optocraft)The Shack Hartmann setup I have is a double pass system where the objective is illuminated with a plane wave output from the sensor with a spherical mirror placed below the lens under test. The rays from the mirror are reflected back through the lens under test and then through the internal optical system of the measurement setup to the sensor. I am trying to model the double pass system so that i can replicate the setup as closely as possible. What I have done so far is:1. Use the “make double pass” replacing the image surface with a spherical mirror. This makes the first surface of the lens under test as the new “image” surface (after making double pass the first surface is also the last surface)2. I use the knowledge base article  “https://optics.ansys.com/hc/en-us/articles/

The example script for the interactive mode in Ansys Zemax OpticStudio 2024 R1.03 does not work out of the box. It manages to find the path of the ZOSAPI_NetHelper.dll from the windows registry (path is to C:/Users/username….) but it says:Exception: Cannot find OpticStudioI don't know why this automatic path is not found, if I put manually the path inside the script (line 24):pathToInstall = r'C:\Program Files\Ansys Zemax OpticStudio 2024 R1.03'It works! Not sure if it is related that I used Zemax before it was acquired by Ansys and it is looking in the wrong location.Just for those who'd like to use the zospy library, you can also pass the path directly:import zospy as zpopticstudio_directory = r'C:\Program Files\Ansys Zemax OpticStudio 2024 R1.03'zos = zp.ZOS(opticstudio_directory=opticstudio_directory)oss = zos.connect("extension")Perhaps it helps others to save some time.

Hello,The following  ZPL-macro is run which performs a geometric analysis and then saves the text of this window: OPENANALYSISWINDOW IMA, GIA_cfg_file$n_GIA_window = WINL()SAVEWINDOW n_GIA_window, A$ The size of the image is 125 pixels, resulting in a text file size of 400 KBWhat I observed is that the time it takes to execute the SAVEWINDOW function takes a very long time of about 20 seconds (!), regardless of whether the text file is a temporary or permanent file.The saving takes nearly as long as the execution of the image analysis.However, if the text output of the very same “Geometric Image Analysis” window is saved manually to the very same file A$, the saving is performed in no time.The subsequent extracting of specific strings from this text file by using OPEN, READSKIP and READSTRING  is also  executed within “no” time. So my question is:why is SAVEWINDOW so slow or more importantly: how can I significantly speed up the saving process?Best regards, Marcel Zemax-Version:  Ansys

In interactive mode - I would like to update the merit value and the operand values after every perturbation I do on a surface variable (e.g.; Decenter-X). For some reason - executing this code line does not seem to update the IDE at all.# Before perturbation: apply a value to a surface cellTheSystem.MFE.CalculateMeritFunction()# After perturbation: Step to read updated Merit Values and Merit Operand Values - No Change!Any ideas?

Typically I would only save the Zemax file as below for later useTheSystem.SaveAs(r"C:\Path\To\Save\MyLens.zmx")Is there a way to save the Zemax file as a Lens Project to a folder? With all the dependencies pointed to the folder root? Such as: GLASSCAT, COATING, CONFIG, etc.?Thanks

I need to exchange the Data File Name of a Source File Object:   I tried to do that by python code:import zospyzos = zospy.ZOS()oss = zos.connect()oss.load(‘zmx_file.zmx’)led = oss.NCE.GetObjectAt(1)TypeSet_LED = led.GetObjectTypeSettings(zp.constants.Editors.NCE.ObjectType.SourceFile)TypeSet_LED.FileName1 = 'filename.dat'I wrote that code according to section #! [e21s03_py] in example 21 of the ZOS-API Python examplesApparently, the code does not work.Did anyone ever manage to exchange source files via python?Can you provide a code snippet that works? Thanks in advance

When I write a *.dll such as n(x,y,z) = a*x → where I expect a linear GRIN (non radially symmetric), instead what happens is that the rays do not bend at all, and the result is modeled as wavefront error with no ray deflection. I made sure to mark it as non-radially symmetric.  However, I do know that GRIN4 exists and works. But, there is no example of GRIN4 in sequential mode under surfaces. Any tips for what I might be doing wrong? I did double check all the derivatives, and an analogous version of my code works in non-sequential mode.  

Hi all, does anyone have a simple method to get all variables and associated parameters?Similar to GETVARDATA in ZPL.Please no workaround like the text file from prescription data.Many Thanks!Hans-Jürgen

Hi all,How can I change the multi-configuration control parameter (current, 1/N, 2/N, etc.) in a POP analysis window using ZOS API?I would like to save the beam file output for each configuration.Cheers - Asuku

Hi, I try to retrieve the output POP field distrubution via python. I looked in the help at IAS_PhysicalOpticsPropagation and couldn't find direct way to do it. I know I can manually save ZBF files and then load, but I need a script as I change parameters and want to retrieve the output beam. How would you advise to do so?   Thanks, Leonid

This forum post is a place to collect update history of diffractive tools beta functions, which includes all RCWA DLLs (and visualization API), polygon DLL, and Zemax Grating Data (ZGD) DLL. Content:1. Overview2. Resources3. Change history OverviewCurrently in OpticStudio, we are adding some useful DLLs to enhance the ability of fully simualting gratings. They allow OpticStudio to consider the efficiency when rays pass through diffractive optical elements (DOE), such like 1D/2D gratings, binary optics, or volume holograms. These extensions can be found in OpticStudio installations.These tools improve frequently based on users’ feedback. We decide to provide functions with DLL so it can be updaetd fast upon users' request. Between each OpticStudio public releases, there might be several minor updates and bug fixes. This forum post is a place for changes history.Note all tools provided here are only available with OpticStudio Premium Subscription. If users are interested in these functio

Hi everybody,I would like to write a macro in which I determine the 100 largest and smallest pixel values on a detector. Only pixels in a certain region of interest should be considered. I have already successfully implemented the criterion of whether a pixel is within the ROI.I also have a solution in mind for determining the 100 largest and smallest values, which I think should already work.When I run the macro, the array with the values also fills up at first, but at some point it stops and no new values are added.Do you guys have an idea why this is not working? Could there be some kind of buffer overflow or so? Or do I have a fundamental error in my macro?I added my macro and an exemplary result belowThanks for any help or hint :)  Best,Matteo ! Calculates the max and min intensity (from the 100 largest and lowest pixels) in a circle centered in the detector plane! Calculates the uniformity = min/max from the in that circledetector = 28size = 51max_radius = 25center = 26total = si

   I created a DLL to model a gradient index surface and while it is working, the modeling results are very similar to a standard surface. It seems that somehow Zemax is not using the gradient index during the refraction process. I have been investigating what I am doing wrong and got more confused.  Your help will be greatly appreciated! :-)   Looking into the example from /zemax/dll/surfaces/us_grin1.c, the refractive indices used for refraction in case 5 are FD->n1 and FD->n2, which are the indices before and after the GRIN surface. In case 6, which is where the index and its derivatives are defined, the refractive index is calculated and the assignment UD->index = index is made, as well as the dn/dx, dn/dy and dn/dz.   So, I am a bit confused:Which refractive index is used during refraction, UD->index or FD->n2? I was expecting that I would use UD->index, but that is not what happens in case 5. How does Zemax ‘know’ that it is dealing with a gradient index materia

Hello community,  I hope somebody is familiar with this topic and has a quick hint. I would like to use the transmission plots (especially TransmissionFan) of Zemax by controlling them in Python. Yet, I miss the possibility to change the settings. My Code looks as follows: {… I hope the stuff before is clear ...}    TheAnalyses = TheSystem.AnalysesWindow= TheAnalyses.New_Analysis(ZOSAPI.Analysis.AnalysisIDM.TransmissionFan)Settings= Window.GetSettings()dir(Settings)The output looks as follows:['AddChild', 'Analysis', 'CreateObjRef', 'Disconnect', 'Equals', 'Finalize', 'GetHashCode', 'GetLifetimeService', 'GetType', 'InitializeLifetimeService', 'IsActiveWindow', 'IsValid', 'Load', 'LoadFrom', 'MemberwiseClone', 'ModifySettings', 'OS', 'Overloads', 'Parent', 'ReferenceEquals', 'RemoveChild', 'Reset', 'Save', 'SaveTo', 'TheDataID', 'ToString', 'Update', 'UpdateCore', 'UpdateUI', 'Verify', 'WriteToStream', '__call__', '__class__', '__delattr__', '__delitem__', '__dir__', '__doc__', '__eq__

When I use Q-Type Asphere (Qcon), F-number solve calculates wrong value.I want to know if this is solve error.If this is an solve calculation error at Q-Type, I hope to fix it.  Radius Solve: F-number 2.65<Standard> <Q-type Asphere (QCon)>All extended parameters values are zero. 

Hi,I am trying to optimize a simple lens that focuses and couples a Gaussian beam into two different fibers. I want to optimize a lens that will yield the best combined coupling efficiency for both fibers. Just to clarify, the beam will be coupled into one fiber at a time, but the same lens will be used to couple a Gaussian beam into both fibers. The fibers are represented by .zbf files which are loaded in the Fiber Data tab in Physical Optics. Right now, I’ve written two ZPL macros that will each open a different .zbf, and they are called in the MFE using two separate ZPLM operands. Each ZPLM operand is immediately followed by a POPD operand to get the coupling efficiency which is then optimized, as shown below. I am not sure if this works as intended. When optimizing, are the operands in the MFE cycled in a loop, so to speak? Also is there a more elegant way of doing this, other than using ZOS-API, or should I use ZOS?Thank you,Sam

I tried those code:FOR i = -0.500, 0.500, 0.1      PRINT $STR(i)," ",NEXTPRINT! This one starts from -0.5 and ends at 0.5FOR i = -0.500, 0.500, 0.05      PRINT $STR(i)," ",NEXTPRINT! This one starts from -0.5 and ends at 0.5FOR i = -0.500, 0.500, 0.01      PRINT $STR(i)," ",NEXTPRINT! This one starts from -0.5 and ends at 0.49, WHY? Thanks!Xing 

Hi, I’m currently trying to trace a large amount (~1 million) of rays with very specific output position and trace their path length it takes them to reach a detector and then output the position as well as the specific path length of that beam. Currently not using scattering, but in future, I would like to extend this to scattering as well. My first thought was to create a loop that would create single rays, trace them, return the OPL through a Merit Function and then output in the end, but I assume that this would take forever to compute. Any idea how this would be done more efficiently? I’ve seen that batch ray trace might be an option, but I don’t know enough about it or other alternatives to evaluate correctly. Thank you for any help!

I don’t understand how I should set the Filter and RayDatabaseFile of the DetectorViewer in non-sequential mode.SHould I use : DetectorView = zos.system.Analyses.New_DetectorViewer()or :DetectorView = zos.system.Analyses.New_Analysis(zos.ZOSAPI.Analysis.AnalysisIDM.DetectorViewer)Then should I use :        settings = DetectorView.GetSettings()and/or ?        settings = zos.ZOSAPI.Analysis.Settings.RayTracing.IAS_DetectorViewer(settings)Then using :         settings.RayDatabaseFilename = db_file        settings.Filter = "h9"Those seems to make the analysis fail       

This MATLAB standalone code imports data from the Interogram analysis feature, plots the Interferogram data as a MATLAB figure and saves it as a png file. This code was written by Michael Humphreys.Language: Matlab  Click here to download Date Version OpticStudio Version Comment 2020/01/14 1.0 19.8 Creation

Hello, I am working on a macro as described in the following article, but converted in Python:https://support.zemax.com/hc/en-us/articles/1500005579082-Modeling-Rotationally-Symmetric-Irregularity-RSI-with-the-APIAs working directly on the system, each modification saves an UNDO file and the action is repeated for each Zernike coefficient, for each surfaces, that slows down the execution.The actual way :Get the system with :TheSystem = TheApplication.PrimarySystemand work on it directly I tried to get a copy of the system with the CopySystem function, modify the copy and push it back :TheSystem = TheApplication.PrimarySystemnew_system = TheSystem.CopySystem()# does work hereTheSystem = new_system.CopySystem() When looking at the surface type of TheSystem, I can see that it changed correctly, however it is not applied in the Zemax main window.I used the TheSystem.UpdateStatus() function, but does not help. Ideally my goal would be to be able to make all modifications outside of Zemax an

How can I extract detector data using the API? And how can I be sure I'm using the correct settings?

This looks like a bug in ZOS API : when calling FindMaterialCatalog on a row of a non-sequential model with ABSORB as mateial, it returns the first catalog in the available catalog listI would except this call to return None or “”

In non-sequential mode, I am trying to automate the process of reviewing any input data that is spectral. The idea is to review how all models (in the wide sense) behave wrt wavelength in a quick way to make sure there’s nothing shady happening, using the ZOS API.For now I’m trying to review :  - all coatings used, and their spectral response wrt incidence angle and wavelength - all materials used and their refractive index and extinction response wrt wavelengthbecause given the complexity of a NSC model, the complexity of coatings definitions/catalogs, material definition/catalogs, a mistake can happen quickly.For now the idea is to review those spectral model dependencies only in a “passive” manner, using the NCE - without running a raytrace specifiicaly.If anyone has ideas or guideline on this process, feel free to comment ! :)

Hi all, I am trying to use ZOS API to assign the diffraction-based dll for the User Defined Object in Non-sequential mode. I have tried normal ‘Diffraction Grating’ object and it works good, however, for the User Defined Object, it did not work. Could anybody share some insights for me? Thank you! Part of the code for normal ‘Diffraction Grating’ object: (This works!)TheNCE.InsertNewObjectAt(1);o1 = TheNCE.GetObjectAt(1);o1.ChangeType(o1.GetObjectTypeSettings(ZOSAPI.Editors.NCE.ObjectType.DiffractionGrating));o1.DiffractionData.Split=ZOSAPI.Editors.NCE.DiffractionSplitType.SplitByDLL;o1.DiffractionData.DLL='srg_trapezoid_RCWA.DLL';o1.DiffractionData.StartOrder=-1;o1.DiffractionData.StopOrder=1; Part of the code for ‘User Defined Object’: (This  does not work!)TheNCE.InsertNewObjectAt(1);o1 = TheNCE.GetObjectAt(1);o1.ChangeType(o1.GetObjectTypeSettings(ZOSAPI.Editors.NCE.ObjectType.UserDefinedObject));o1.Comment = 'DiffractionGrating.DLL';o1.DiffractionData.Split=ZOSAPI.Editors.NCE.Diff