I followed the instruction for converting ray files to dat files using Visual Studio. But I can not open the file that I would like to convert using “Shift+Alt+F5!

The tool provided in this post is part of a workflow to simulate the CMOS sensor response. The workflow includes 3 steps. (1) Analyze chief and marginal rays information for the target lens data system in OpticStudio.(2) Calculate the conversion efficiency from incident optical power to output electric power in Lumerical.(3) Utilize the data of conversion efficiency and the irradiance from optical simulation in Speos to get the final electric power map. In this post, the tool for first step is introduced. By running this tool with a given lens system, we calculate and export the data of chief and marginal rays’ angle for different position on the image surface. For step 2 and step 3, the information will be updated soon in following two articles:CMOS Sensor Camera - Sensor Charact

We have created a public repository called https://github.com/ansys/optical-automation. We are hoping to gradually move our solutions to this Ansys open project on GitHub.How to use Ansys optical-automationAnsys optical-automation comes with a documentation: https://ansys-internal.github.io/optical-automation/This section shows how to clone the GitHub repository and run the code in Visual Studio. Note the Visual Studio is not absolutely required. Users can use their preferred tool to sync the GIT repository and preferred IDE tool to run the Python project. Here we simply use Visual Studio as an example. Visual Studio installationUsers can download and install the latest Visual Studio in the follow

I’m writing a script to do a lot of automation and has a lot of inputs for different configurations.  I’m trying to combine multiple .ZBF, each with a different field position.  This means I need to use ZBFRESAMPLE to shift the images to match their offsets compared to the on-axis field.  This is quite handy since I can use physical units to shift the image rather than try and figure out how many pixels I need to shift by.The only other option I can think of is to have the API run a macro, however, I think I would need to have the ability to have the API input variables into a macro which I don’t think is possible.Does anyone know if it’s possible to call just one ZPL function in API or do I need to figure out how to mix API and ZPL?

I created a user analysis in ZOS API that works well when opened manually in the GUI. But i wonder if there is an option how I can programmatically open this analysis in ZOS API.

Hello,It seems that the number of inputs for order efficiency is limited when using Diff2DSample.dll. The image below shows inputs missing orders above 2,-2. Is there any workaround for this? I’m on Zemax OpticStudio 23.1, PremiumThank you,John

So I’m trying to optimize a design in Zemax non-sequential. However I’m noticing that there is a discrepancy between what the MF editor reports, and what I see from running ray trace and running detector viewer. My MF looks like the following: And I see that the total flux (line 7) is 0.619 out of .75. This is a very good number. So then I cancel the optimization, and perform a ray trace, and when I take a look at the detector viewer, I get the following:How can the MF editor be displaying 0.619, yet the total power, which I think is the same metric on the detector viewer is indicating 0.422?

 According to Zemax’s online help https://support.zemax.com/hc/en-us/articles/1500005578722-Simulating-diffraction-efficiency-of-surface-relief-grating-using-the-RCWA-method, for the particular diffraction grating that we are trying to model,  we need to increase the Max Order parameter.In the help on “simulating diffraction efficiency  of a surface relief grating using the RCWA method” authored by Michael Cheng and updated on April 28, 2023 under the subsection Max Order it is stated“This is currently limited to 10 (totally 21 harmonics). When the number is larger than 10, it’s modified to 10 in the DLL. Contact support team to increase the limitation.”What is the procedure to increase the limitation?

While analyzing the results of batch ray traces, I noticed that some rays seemed to be transmitted through the system that I did not believe should have made it. To test this, I set up a series of ray traces, all with the same set of input ray positions and direction cosines (no difference whatever). The only parameter I let vary between the traces was the final surface of the ray trace. In other words, my setup contained this line:RayTraceData = raytrace.CreateDirectPol(total_rays_in_both_axes, ZOSAPI.Tools.RayTrace.RaysType.Real, 0,0,0,0,startSurface,endSurface);where only endSurface was allowed to vary. I stepped endSurface through every surface and recorded the vignetteCode value of every ray. Plotting the results, I have found a few instances where a subset of the rays that vignette at the nth surface are not listed as vignetting at the n+1st surface. For example (see attached), the plot for surface 18 shows rays that were listed as vignetting at surfaces 7, 8, an

Hi, I’m trying to use ZPL to run a couple of loops and save geometric image analysis. This loops aim to change the field and wavelength in the settings of the image, but I cannot make it work. If I go for the text-only saving option, it doesn’t change either. To guide you into the code, first I define the x and y of the fields:DECLARE setxfields, DOUBLE, 1, 9DECLARE setyfields, DOUBLE, 1, 9setxfields(1) = 0.0setxfields(2)=9.68938        …setyfields(1)=-0.0    setyfields(2)=-0.034… Then define the folders and filenames and then start the loopFOR wave2, 1, 9, 1    FOR field, 1, 9, 1    field_x = setxfields(field)    field_y = setyfields(field)    SETSYSTEMPROPERTY 101, 9    SYSP 102, 1, FLDX(field)    SYSP 103, 1, FLDY(field)    SYSP 202,1,WAVL(wave2)    window=WINL()    OPENANALYSISWINDOW "IMA"    UPDATE ALL    filename$ = arm$+

HiI am  using Zemax to simulate images of scenes through customized imaging setups. However, I am unable to simulate images of scene with sufficient resolution.My current imaging setup convolves a complex PSF with the observed scene. Extracting actual scene information requires deconvolution of the image to obtain a meaningful image. This means that I cannot resort to the classical MTF procedure using the FFT of the simulated PSF, as it would only give me the MTF of the convoluted image.I have therefore tried to proceed by scene analysis to extract MTF, i.e. simulate with Zemax the image of classic checkerboard patterns seen through my custom design and then in a second stage extract the MTF using image processing software. The core issue is that the resolution of images obtained after deconvolution are insufficient for image analysis and MTF extraction by slanted edge method.Is there any way to get more

In particular, I’m using the Python API. I would like to be able to look for objects by name to make the scripts more reusable.

Hello,I’m trying to convert the following C# code snippet:var hpsf =TheSystem.Analyses.New_Analysis(AnalysisIDM.HuygensPsfCrossSection);var hpsf_settings = hpsf.GetSettings() as IAS_HuygensPsfCrossSection;hpsf_settings.PupilSampleSize = (SampleSizes)(_pupilSampling + 1);hpsf_settings.ImageSampleSize = (SampleSizes)(_imageSampling + 1);hpsf_settings.ImageDelta = 0;into Python:hpsf= TheSystem.Analyses.New_Analysis(ZOSAPI.Analysis.AnalysisIDM.HuygensPsfCrossSection)hpsf_setting=hpsf.GetSettings()hpsf_settings.ImageDelta = 0but I got error messageAttributeError: 'IAS_' object has no attribute 'ImageDeltHow can I cast  hpsf_setting returned by GetSettings() into a HuygensPsfCrossSection specific object?Thank you very much! lin

Hi all,is there a way to access the contents of the Ray Database Viewer via the ZOS-API? I did not find any example. I am not even sure whether it is possible since there does not seem to exist an interface for this analysis type in ZOS-API. I found a knowledge base article which explains how to read the contents of .ZRD files (Batch Processing of Ray Trace Data using ZOS-API in MATLAB or Python – Knowledgebase (zemax.com)). However, I have no idea how much effort is required to recreate the content of the Ray Database Viewer from the .ZRD file.Best regardsBenjamin

In a simple exercise where a paraxial lens is used to collimate a beam from a diode source, I use a rectangle detector to monitor the output of the lens.Using the function GetAllDetectorDataSafe(det_id, x) or other, is it possible to retrieve the detector data in the angular space? I would like to extract the angular RMS to conduct an optimization of the lens position that results in a collimated beam. Kind regards

Hi all, I am writing a ZPL macro which calculates phase patterns and imports the phase into Grid Phase Surface automatically. (There is a typo in title. I’m using a Grid Phase Surface) I found a way to import the grid phase using IMPORTEXTRADATA keywords in a below questionMacro import of .dat file onto a Grid Phase surface | Zemax CommunityBut it requires “reading” .dat files; so, I should firstly generate .dat file for the calculated phase profiles, and after that I could read again the phase from those .dat files to import. It seems to be very inefficient method and takes too long time to write and read my phase profile.  Is there any way to import phase data directly from another data types in ZPL (like array or vec) instead of writing and reading .dat files? Wit

Hello,I am trying to develop a ZPL macro that will be used in my merit function so that different wavelengths and different fields will all share the same MTF. I am currently getting very good results with my code, but it is a little bit slow at roughly 8 seconds per cycle which is worrisome as I am currently only doing 1 field with 3 wavelengths. I was wondering how GETMTF actually works since it seems like it is calculating the entire MTF and only extracts the value for a single specified frequency when GETMTF is ran. For my purpose, it would be more efficient to calculate the entire MTF once for each wavelength/field, and then I could just grab the values directly from the MTF rather than having to run a loop combined with GETMTF to get the values I need to calculate MSE.  Please let me know if you have any suggestions on making my code more efficient or any alternative methods to solve this problem.

For both radiometric analysis (for example determining the power incident on a detector) and optimization, the best choice for a source is almost always a pseudo-random source such as a Source Ellipse, with enough analysis rays to provide for smooth statistics. Frequently, this means tens of thousands to millions of rays. For visualization, OpticStudio provides the capability to designate a lesser number of Layout Rays to appear in layout plots. These layout rays are still randomly distributed. If only a few rays are used, they generally do not well represent the design. If enough rays are used to visualize the extent of the volume occupied by rays, then the plot can become crowded.As a solution to this problem, the accompanying DLL files provide the ability to generate, in non-sequential mode, uniform fans and rings of rays similar to those which can be displayed in sequential mode layouts. They are compiled for a Windows 64-bit platform.YFAN.DLL is a source dll which

Hello,So I’ve been trying to alter the number of cores through a macro by using “SYSP 901, []”. However, each time I run the ray trace (NSTR 1, 0, 0, 0, 0, 0, 0), the number of cores resets to its maximum value.To attempt to identify why, I re-used the code proposed HERE, adding a “print SYPR(901)”, and I get the following.The elapsed time varies somewhat, but stays close enough to one another to conclude that the NSTR is somehow resetting the # of core before running the ray trace.-The duration is coherent with 20 cores (~7.8s) if I run it using the Ray Trace Control window; the time at 1 core is ~40s, 16 cores 7.4 s-I’ve tried using the advanced options in the sys

Hi everyone! Long time lurker, first time posting. I have been using Zemax for the past couple of months, and have been getting familiar with the backend, C# ZOS-API. As I’ve been getting more familiar with the ZOS-API, I’ve tried to more and more exciting things, which eventually lead me to use the batch ray tracing function. I can do this successfully and actually get quite a good representation of my input picture at the output image side, using CreateDirectUnpol and AddRays. However, I am trying to get a feel for intensity on the imaging plane, and the only output I get when using ReadNextResult is intensity = 1, even though my system has various elements with different non-100% coatings on them. However, I am using black-box lenses from Thorlabs, and I’m wondering if this causes Zemax not to give out the intensity values? If not, what could I be doing wrong?Attached is the relevant code I use which gives me 1 for intensity output:

I´ve a simple simulation with a diode source followed by a gaussian diffuser and then a polar or rectangle detectors. I would like to see how the gaussian diffuser parameters (e.g. sigma parameter) affect the angular parameters of the output field.I´m having difficulties extracting the data both from the polar and rectangle detectors when using the ZOS-API. For the rectangle detector i´ve used the following sample code adapted from the Zemax repository:DetObj = 12obj = TheSystem.NCE.GetObjectAt(DetObj);numXPixels = obj.ObjectData.NumberXPixels;numYPixels = obj.ObjectData.NumberYPixels;pltWidth = 2 * obj.ObjectData.XHalfWidth;pltHeight = 2 * obj.ObjectData.YHalfWidth;pix = 0# Get detector datadetectorData = [[0 for x in range(numYPixels)] for x in range(numXPixels)]for x in range(0,numYPixels,1): for y in range(0,numXPixels,1): ret, pixel_val = TheNCE.GetDetectorData(DetObj, pix, 1, 0) pix += 1 if ret == 1:

I have a (n x m) array of diode sources. My optical simulation includes a sweep of n and m. However within the ZOS-API (python) i don´t seem to find this attribute in the diode source object.Does someone know how to access these variables?

While running the unit tests for ZOSPy, I discovered that calling Application.GetSystemAt(0) throws a System.ArgumentOutOfRangeException . This is rather weird, since the primary system should always be present. Upon further inspection, Application.NumberOfOpticalSystems turned out to be 0.I tried to reproduce this problem in C#, and succeeded. The problem also occurs in this example:bool isInitialized = ZOSAPI_Initializer.Initialize();var connection = new ZOSAPI_Connection();var application = connection.ConnectAsExtension(0);Console.WriteLine(application.NumberOfOpticalSystems); // --> 0var systemZero = application.GetSystemAt(0); // --> Throws ArgumentOutOfRangeExceptionBut not in this one, while the new surface added at the end doesn't appear in the

Hi guys, I am new to learning ZPL. I have a list of macros that I am tasked to write at work. Here are the list below with their purpose. I was hoping anyone have written similar macro, p[lease share or give me tips on how to write them. Thanks.Compute the paraxial ABCD matrix between 2 surfaces. Bend a lens. Given one radius, compute the other radius to maintain the focal length. Macro to plot and optionally list the distortion over the full image format Calculate relative or absolute dn/dT values based on the Schott equations Draw the aperture(s) associated with a surface. Define a macro function to compute the clearance between two surfaces, including the sags of the two surfaces Compute the angular boresight error in object space of the system due to the decentration of a surface or a group of surfaces. Compute the edge thickness between two surfaces at a specified x,y location Pl

Hello, I want to push into my model an input file with data regarding new position/ parameters.When I execute the ZPL code through the GUI (Programing>Edit/Run, F9) it works just fine, but when I try to execute it through the merit function with a ZPLM row it seems that the SETNSCPARAMETER/ SETNSCPOSITION just isn’t working.I know the MFE is executing the ZPLM since I made a debug output which looks just fine, feels like I’m missing something very basic.Code snippet:OPEN INPUT_FILENAMEOUTPUT OUTPUT_FILENAMEREAD NUM_OF_PARAMS NUM_OBJPRINT NUM_OF_PARAMS, " ", NUM_OBJFOR II, 1, NUM_OF_PARAMS, 1 READ PARAM_NUMBER PARAM_VALUE PRINT PARAM_NUMBER, " ", PARAM_VALUE SETNSCPARAMETER 1, NUM_OBJ, PARAM_NUMBER, PARAM_VALUENEXTCLOSE An input/output example of the code above:## INPUT ##3 181