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 pro

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

   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

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', 'RemoveCh

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 sp

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.Copy

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

I would like to access, through ZOSAPI, detector data which has been fitered by a filter string. I know how to access detector data through ZOSPI. And it is of course possible to view filtered data in OpticStudio by saving a trace to a ZRD file and specifiying that as the database for a detector viewer. The filter string can be applied as the ZRD is saved, or applied in the settings of the detector viewer. But I would ike to access the filtered data as it is viewed in the detector viewer, rather than the unfiltered data. Is this possible? I am actually using ZOSAPI from Mathematica, but an answer related to Python or C++ would be useful.  Kind regards, David,

Following, Feature Request: ZOS-API Layouts Exports Completion | Zemax Community, I’d also advocate for making the 3 cutting plane tools from the NSC Shaded model available in ZOS API.Those cutting tools are quite efficient in visualisation, and sometimes even absolutely necessary. Now that we can export the shaded model to png easily, it’d be great to be able to enable/disable those cutting planes as well. In the same manner, having access to the Camera View would be nice:  

Hi,I would like to use zpl to update my detector viewer and save it as an image.However, neither Ray Database nor Filter are adjusted in the detector viewer.#trace rays & evaluate Detectorfilter$ = "h3&h6&!x_hitface(8,0)&!x_hitface(8,2)&!x_hitface(4,0)&(x_hitface(7,1)|x_hitface(7,0))"filter2$="h3&h6&!x_hitface(8,0)&!x_hitface(8,2)&!x_hitface(4,0)"fileName$ = "ZMPRays.ZRD"NSTR 1, 0,0,0,0,1,0,1,fileName$temp = NSDD(1,0,0,0) ZRDPlayback fileName$,1,0,1, filter2$UPDATE ALLPRINT NSDD(1,9,0,0)ZRDPlayback fileName$,1,0,1, filter$UPDATE ALLPRINT NSDD(1,9,0,0)settingsFile$= "...\Zemax\Configs\DVR.CFG"MODIFYSETTINGS settingsFile$, DVW_ZRD, fileName$MODIFYSETTINGS settingsFile$, DVW_FILTER, filter$UPDATE ALLThe  PRINT NSDD(….) commands give the correct outputs, but the detector viewer is not updated.

I am using the ZOS-API in C# with 4.8.1 framework using Zemax OpticStudio 2024 R1.02 and getting an error message when running the Local Optimization tool.The error message returned from running the tool is “Input settings are invalid”.This occurs only when I load from an Archive File (.ZAR).   If I load from a model file (.ZMX) then the Local Optimization tool works as expected.For the fields that I set, there are only 2; Algorithm = DampedLeastSquares and Cycles = AutomaticIt’s weird and I can’t understand the difference between accessing the model from an Archive would create this issue. NOTE, that I did load the ZAR file from the actual Zemax application and Optimization worked fine. If anyone has any ideas as to the issue then please let me know ThanksB.

The ray density of the spot diagram is not being updated as expected; I have tried two different methods: # spot diagramspot = TheSystem.Analyses.New_StandardSpot()spot.GetSettings.RayDensity = 15spot.ApplyAndWaitForCompletion() newSpot = TheSystem.Analyses.New_StandardSpot()print("Spot has analysis specific settings? ", newSpot.HasAnalysisSpecificSettings) # True; no ModifySettingsnewSettings = newSpot.GetSettings()newSettings.RayDensity = 15newSpot.ApplyAndWaitForCompletion() However, after being run the ray density of the spot diagram does not update as expected - any ideas?

API support for the Cross-Section, 3D Layout, and Shaded Models is added to the OpticStudio API.  The support allow users to change the settings via the API and retrieve a static image.  Layouts in both sequential and non-sequential mode are supported. Some toolbar buttons, such as automatically setting camera viewpoints, will also be accessible via the API. Please download the following Python Standalone codes, including:PythonStandaloneApplication_SEQ_layout.py       (sequential mode and export 2D cross-section) TheSystem.Tools.OpenCrossSectionExport()   # the core command  PythonStandaloneApplication_SEQ_3DViewer.py (sequential mode and export 3D viewer) TheSystem.Tools.Open3DViewerExport() PythonStandaloneApplication_SEQ_ShadedModel.py (sequential mode and export shaded model) TheSystem.Tools.OpenShadedModelExport

Hello everyone,I can't connect Zemax and Matlab since I installed the new version of zemax 2025 R1.01. I am using Matalb version 2019a Updates 9 and it worked with previous versions of zemax.The error in question Unable to load one or more of the required types.My two applications are installed in 64bits I've already tried uninstalling and reinstalling the applications. Thanks for your help 

Hello fellow optics enthusiasts,I’m currently working on a task where I need to ignore multiple surfaces in a Zemax optical system using the ZOS-API. At the moment, I’m using the following loop:for i in range(150, 160): surface = TheSystem.LDE.GetSurfaceAt(i) surface.TypeData.IgnoreSurface = TrueHowever, this approach seems to be quite slow. Has anyone found a more efficient way to ignore multiple surfaces at once?Any insights or suggestions would be greatly appreciated!Thanks in advance,Sebastián

Hello Everyone,What is the best way to create sag on a lens surface (one of the two surfaces would be the beginning, and then I would move to both surfaces) and parametrize it using python so that i can create wavefront maps and the changes in the wavefront maps based on the localized changed in the sag?Here is what I want to do:Create sag on a lens surface that can be parametrized (conic constant and the other asphere constants can be varied) For each combination of these parameters, evaluate the wavefront mapSo far, the knowledgebase articles show how to use a .dat file to induce sag on surfaces, but there is nothing about parameterization.Is there a Python example that does something similar?Or is there any other method that would make more sense? Thank you for your insights.Amit

Is there a way to access the properties of a coating in the ZOS-API? The article below shows how to access the name of the coating, but does not show how to get the properties of the coating.I’m not finding any handles that give the actual coating information. Thanks!