This Matlab function imports a raw Zemax ray database stored in ZRD file, groups the rays into distinct paths based on i) the exact same sequence of objects hit AND ii) ray events (such as reflection, splitting etc.), and outputs this information in a form of graphs, human-readable variables and, most importantly, a summary table storing each path in descending total power, object sequence, total ray events and so on, which can be further processed either using Matlab's native capabilities, or exported and processed using Excel or a simple text editor.It DOES NOT need Zemax to be installed onto your system and does not use any API to connect to it. It is a completely standalone function.The need for this custom function came clear during one project at work as the native Zemax ray paths tool was insufficient. As per official documentation, it now groups it based on the sequence of FACES the rays hit.In contrast, this function retains a full low-level

I have a question about Zemax Macro. My macro outputs the results from 1 previous macro setting, even though I edit and save the new setting in the macro every time. I put the screenshot that explain this problem. I have no idea why it happens, so I would like to have any suggestion and comments.  

Hey, I’m very naïve to Zemax and ZOS-API. I just tried to find the setting and run the code, but I couldn’t see the results from the image simulation.I used the standalone application and here is my code.     # load local variables    ZOSAPI = zos.ZOSAPI    TheApplication = zos.TheApplication    TheSystem = zos.TheSystem        # Insert Code Here    file = "C:/2021/Zemax_Image_Simulation/test.zmx"    cfg = "C:/2021/Zemax_Image_Simulation/test.CFG"    TheSystem.LoadFile(file, False)    TheImageSimulation = TheSystem.Analyses.New_ImageSimulation()    analysisSettings = TheImageSimulation.GetSettings()        analysisSettings.ModifySettings(cfg, 'ISM_INPUTFILE', "Text_100p_3x3_2_g1196x1279_dist.png")    analysisSettings.ModifySettings(cfg, 'ISM_FIELDHEIGHT', '15')    analysisSettings.ModifySettings(cfg, 'ISM_FLIPIMAGE', '3')    analysisSettings.ModifySettings(cfg, 'ISM_

I have run both the “phases” macro to locate where the steps are for a binary 2 on an aspheric surface and the “DoeSag” macro. However, I get different results as the radius increases. Sometimes, the number of zones ends up different.Which one is correct? I’ve used the “phases” macro for a long time without much issue. Recently, we have had requests for the sag tables on a binary, but I’m not sure I can trust the DoeSag results as the number of zones and zone locations do not match.

Hi, I started working with ZOSAPI in Python. I am aware that since I am using clr.AddReference(<Module>) that means that they are dynamically being imported but is there a way to achieve autocomplete and error checking?

How to get FFT MTF, EFL values of Montecarlo runs when RMS wavefront is selected as criteria in tolerancing, any macro is available or can be done 

We recently implemented the Geometric Image Analysis in ZOSPy 1.30. While doing so, we noticed that IAR_DataGrid.MinY does not return the lower bound of the y-axis for the output (at least when compared to the output in OpticStudio itself). It seems to be returning either the upper bound or the abolute value. E.g., when the analysis is centered at (0,0), the x- an y-axes in OpticStudio start at -25 while the API returns -25 for MinX and 25 for MinY.  Could you elaborate on what MinY (and to an extend MinX) correspond to. So far, we thought the datagrids and their axes follow the normal matrix conventions, which was the case for all analyses we implemented and used. Is this not the case for Geometric Image Analysis, or is there an error in the API?

The usage of ZOSAPI.AnalysisSettings.IAS_Surface.UseObjectiveSurface() is not clearly documented. The only place where is appears is in the ZOSAPI introduction under “Changing Settings” to explain that an errormessage can be returned if it did not work. In contrast to ZOSAPI.AnalysisSettings.IAS_Surface.UseImageSurface(), which selects the image surface whenever available, it is unclear what UseObjectiveSurface() does. The only place where I have actually managed to get it to work is for the Start Surface in the PhysicalOpticsPropagation analysis, where it selects the Entrance Pupil. Is the intended use selecting surfaces that are not an actual surface within the model (such as the entrance pupil)?

I am implementing a fix for the incorrect MinY of the Geometric Image Analysis in Python, as discussed in this post. While doing so, I noticed an odd behavior. It is allowed to specify the Image Size as negative for the Geometric Image Analysis, but this causes problems with the resulting output. With the example Double Gauss 28 degrees field, I can create the following analyses using the API with slightly different settings:API output for 4 slightly different analyses Showing that the extent of the axis with a negative image size and the number of pixels set to 100 will always equal 100. First I thought this was an API proble

Hello to all,I read the topic about : “how to ignore Surface in API”. I tried to do something similar for non-sequential object but it is not working.         surf4 = TheSystem.NCE.GetObjectAt(4)        surf4.TypeData.IgnoreObjects = 1First TypeData.IgnoreObjects want a string but I don’t know what to write. Thank you very much in advance fir your answer. Clotilde 

Hi all,I am trying to run a simple standalone c++ application which gives  “Microsoft C++ exception: _com_error at memory location” The error is on line 29 // Create the initial connection classIZOSAPI_ConnectionPtr TheConnection(__uuidof(ZOSAPI_Connection)); Does someone have an idea on what could be the issue? I prefer to use C++ as I have to integrate other code with it. Thank you.

In some surface types, e.g. Paraxial XY or Grid Gradient, data entry for Radius and Conic is disabled (their cell value is returned to a blank after typing in a value).Can this behaviour be programmed in a UDS?

Hello All,how can I suppress writing UNDO files in an interactive zosAPI extension?This is important to speed up the process!Thanks!Hans-Jürgen

Hello,still can't we save polar detector data in eulumdat/ies files with ZOS-API? Is there an alternative solution? And most importantly, can we hope that it will be implemented?Thank you!

Is there a way to access the field 'Convert To' function in a ZPL macro?  If not, can this be added to the new features list? Thanks. Pat.

This python ZOS-API interactive extension creates a ray file based on batch ray tracing in a sequential system. This allows import of image-space ray data from a sequential model into NS mode and/or Speos, including black-boxed lens systems. For a user selected field coordinate, rays are randomly selected in the pupil and traced to the image plane. The image space ray data (intercept at a specified dummy surface) are saved as a ray file in both Zemax and Speos formats into the ...\Zemax\Objects\Sources\Source Files\ directory. Note that is merely intended as an example. The implementation this tool should be adapted and validated based on individual cases. Click here to Download

What is the best way to validate that the parameters input by the user are valid? For example, say that I have a parameter “n_rows” that needs to be an integer greater than zero. Should I check this upon initialization of the DLL (case 8)? If the input is invalid, should I then change the corresponding FD->param[i] it to be a valid value (e.g., if the user input 0 then change it to 1)? Or is this a bad idea? The example files state that the DLL should only modify FIXED_DATA in case 7, when Zemax is asking for safe data. Thanks

Hi everybody,I need your advice / help for using the API.I am currently trying to run my Zemax file over the interactive mode with python. So far, I have managed with the help of the ZOS-API Syntax help and the examples presented there, but I am not getting any further at this point. The Zemax file I want to control is a non-sequential system.I would like to create a Universal 1-D Plot where I plot the value of one operand (=NSDD) in my merit function in dependence of the tilt angle of an object in my system. In the image attached at the bottom you can see the settings I would like to set over python. I am struggling with setting the field “NSC Data” with python. In the documentation under KEYWORDS-->MODIFYSETTINGS I cannot find any setting for this option: UN1_CATEGORY: Use 0 for surface, 1 for system, 2 for config.  I tried 3 for “NSC data” without success. You can find th

溶液中に存在する粒子の吸光、散乱を評価できるようなモデルをノンシーケンシャル系で作成していて質問があります。Mie.1dllを使用し、光源、溶液、ディテクタの３つのオブジェクトで評価しているのですが、Particle Indexの設定時にわからないことがございます。シェードモデルで光線を確認しながらParticle indexを大きく（初期値から溶液の屈折率より上）していくと、散乱が発生する回数が増える事象が起きました。（光線を保存して光線データベースビューアで確認し、実際に代わっていることも確認しました）想定では屈折率が変わったときに散乱方向や散乱強度に影響はあるが、散乱回数は変わらないと思っていたのですが、こちらはどういった理由で起きているのでしょうか。 

Hi everyone,I am new here and trying to write a macro for a simple setup that I have. I have a beam at source with specific NA and goes through few optics and get focused on a surface with floating aperture. My inputs are relative position of source/object respect to image in X and Y and output is efficiency at “Geometric Image Analysis”. How can I write such a Macro? 

The Python code converts the Excel data into ZBF text format. The sample Excel is provided as ZBF_Example.xlsx.  Click here to download Date Version OpticStudio Version Comment 2025/01/26 1.0 - Creation  

I cannot find in the doc what are the names of the parameters in the API to change the field density and wavelength, especialy in the MODIFYSETTINGS which does not mention this type of analysisMaybe it is not implemented ?Also, the analysis results do not exihbit any data: print(analysis_results.NumberOfDataGrids)print(analysis_results.NumberOfDataGridsRgb)print(analysis_results.NumberOfDataScatterPoints)print(analysis_results.NumberOfDataScatterPointsRgb)print(analysis_results.NumberOfDataSeries)print(analysis_results.NumberOfDataSeriesRgb)print(analysis_results.NumberOfMessages)print(analysis_results.NumberOfRayData)all print 0, so is there a way to retrieve the results from this analysis ?

Hello Optics Team! I meet a question when writing ZPL. There is a mirror-reflected system and I would like to do the sensitivity analysis on some tolerances. When it comes to decenter, I found that it was difficult to pick up a surface’s ‘Before surface tilt/decenter’. There is a function of picking up ‘After surface tilt/decenter’ (SURP 66) but no such a function for ‘Before surface tilt/decenter’.Anyone have some experience about it? Thank you!

So far I haven't found a way to calculate many rays through to the image surface and read out the ray data on each surface.In ZPL, the "RAYTRACE hx, hy, px, py, wavelength" provides ray data on all surfaces (RAY*(surface)).Have I overlooked a solution using ZOS API?Many Thanks!Hans

Hi. I started to study ZOS-API with Matlab today. And I managed to set a specific material refractive index and get it to work without error. And My goal is to create code that can display PSF,MTF, Thorough Forcus Spot diagram and Zernike Standard Coefficients. Therfore, could you please give me some advice how to analyze them and receive their results in Matlab? import ZOSAPI.*;![endif]-->!--[if>% Set up primary optical systemTheSystem = TheApplication.PrimarySystem;![endif]-->!--[if>% AperturePupilDia = 8.0;TheSystemData = TheSystem.SystemData;TheSystemData.Aperture.ApertureValue = PupilDia / 2;![endif]-->!--[if>![endif]-->!--[if>% Lens dataTheLDE = TheSystem.LDE;% TheLDE.InsertNewSurfaceAt(2); % Surface_1 = TheLDE.GetSurfaceAt(1);Surface_2 = TheLDE.GetSurfaceAt(2);Surface_3 = TheLDE.GetSurfaceAt(3);![endif]-->!--[if>