An example of tracing 2 rays by using the following method.OpenBatchRayTrace

Hello!I’m attempting to use the `zosapi` package with @MichaelH ‘s RayTrace.dll for fast batch ray tracing in Python. It works just fine when I call Python scripts from some terminal, but am having some difficulty using it in Jupyter/IPython notebooks.Below shows where the kernel crashes, without giving me a stack trace to try and diagnose why the kernel is crashing. Has anyone encountered this problem before? 

Is it possible to save and load .fld files in the Field Data Editor using the ZOS-API method?

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.

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, and 9, which are no

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 accurate scene imaging through simulation with my setup? Or is there another metho

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 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: // Set up Batch Ray Trace

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: detectorData[y][x] = pixel_val else

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 GUI (indicating it is not interacting with the primary system):bool isInitialized = ZOSAPI_Initializer.Initialize();var connection = new ZOSAPI_Connection();var application = connection.ConnectAsExtension(0);Console.WriteLine(appli

I am writing some python code using PyCharm to generate a non-sequential file from scratch. I’ve used the Zemax API extensively in the past for similar projects which either add or modify lots of rows in sequence, but I haven’t run any of those since before the Ansys merger. Now I’m starting to see some strange behavior as I debug. I have commands which I know and can verify work, even simple ones like:TheNCE.AddObject()While the program is running, it has no issues with these lines. If I save the file and open it, I can see everything is being added, comments are being set, colors are being set, etc. etc. The code works. But once I reach a break point and start debugging, I start getting this error, even when I run these commands that again, I have confirmed work as expected:System.Runtime.Remoting.RemotingException: Failed to write to an IPC Port: The pipe is being closed.I did some Googling and while I see some issues relating to server communication, I don’t see any references to Z

I am using zos api at pythonThe api is very good interface to expand my works.But, there are some questions.I want general information of the lens from prescriptionReport.I find a way to get the data from the code below. prescriptionReport = TheSystem.Analyses.New_Analysis(ZOSAPI.Analysis.AnalysisIDM.PrescriptionDataSettings)    prescriptionReport.ApplyAndWaitForCompletion()    prescriptionResults = prescriptionReport.GetResults() However, i cannot find extract data from the “prescriptionResults.”The only way i know is export the prescriptionResults to a text file and read it.i want some way to access the results of prescriptionResults . I am calculating Hygens PSF. It was not difficult to caluculate PSF map form zos-apiThere are important data in header to utilze the PSF.I used “headdata=result.get_HeaderData()”, but headdata does not have any data.I want headerdata of PSF. Thank you all  

Hi all, I am looking to build an API in MATLAB to perform image simulations in Zemax. I am having trouble with the basic case.My MATLAB Standalone Application:function [] = BeginApplication(TheApplication, filename)import ZOSAPI.*;TheSystem = TheApplication.PrimarySystem;TheSystem.LoadFile(filename, false);% Create analysisim_analysis = TheSystem.Analyses.New_ImageSimulation();im_settings = im_analysis.GetSettings();im_settings.OutputFile = 'testfinal.BMP';im_analysis.ApplyAndWaitForCompletion();end If I run this on the “Double Gauss 5 degree field.zmx” sample file, I get an image generated that simply [0,0,0]  pixels.I can run the simulation on the same .zmx file in OpticsStudio without issue. Any ideas what I am doing wrong?  

I use a cylinder volume with a scatter model (gaussian) in the front face to implement a generic diffuser.Among other parameters, the scatter model is adjusted through the sigma value.Using the following code does not result in the sigma value being updated:o11 = TheSystem.NCE.GetObjectAt(11)coat_scatter = o11.get_CoatScatterData()coat_scatter.GetFaceData(1).CurrentScatterModelSettings.set_Sigma(1.2)Alternatively, using the following code also does not update sigma:coat_scatter_face_1.CurrentScatterModelSettings.Sigma = 1.5 Does anyone had a similar experience? How to address this problem? Kind regards!

% Set up primary optical systemTheSystem = TheApplication.PrimarySystem;TheSystem.MakeNonSequential();sampleDir = TheApplication.SamplesDir;…Solves the with purely non-sequential models.

Could anyone help troubleshoot an error when running the NSC RayTrace in Interactive Extension mode from Matlab - ‘Unrecognized field name "ClearDetectors".’?The code always runs the first time through, and then the second time through the below routine, either in the same program execution or after stopping and starting again, it hangs up on NSCRayTrace.ClearDetectors(0);                                      % Ray Trace                        % Create ray trace                        NSCRayTrace = TheSystem.Tools.OpenNSCRayTrace();                        NSCRayTrace.SplitNSCRays = false;                        NSCRayTrace.ScatterNSCRays = false;                        NSCRayTrace.UsePolarization = true;                        NSCRayTrace.IgnoreErrors = true;                        NSCRayTrace.SaveRays = false;                        NSCRayTrace.SavePaths = true;                        NSCRayTrace.SavePathsFile = 'Simulation_temp.PAF';                        NSCRayTrace.ClearDetectors(

I am trying to run a boilerplate script to communicate with ZOS-API using MATLAB but I run into some errors during initialization. The path returned by winqueryreg() is valid and added to the Matlab path, but the Helper DLL doesn’t load correctly. Why might be the reason for this error?  Thanks!

Hello,Python's latest version 3.10 was released a few days back. Our ZOSAPI- Python User updated Python's older version to 3.10 which is not recommendable for Python Interactive and Standalone ZOSAPI -Python. The Pythonnet library which connects CLR of ZOS API dll to Python has not been updated for Python 3.10. So, if you find customers using Python 3.10 or Python 3.9. It would be better to use python 3.7 or Python3.8. As Pythonnet works well with these versions.As you can see after installing Pythonnet getting Attribute error Addrefrence.Attribute ErrorThanksSahil

How do I set a field position (say field coordinate X) to a variable using ZOS-API in Python?I am accessing the Fields information usingFields = TheSystem.SystemData.FieldsIt seems like the methods within the Fields object are slightly different to the MCE or LDE editors, as I can get a single field doing Fields.GetField(2) but I cannot find a method like SetSolveData(solve), which would work in the MCE.Any idea on how to set a field coordinate to a variable?Thanks.

In Non-sequential mode, there is no feature to make the detector result iso-line. Therefore, if ZOS-API functions such as Python or Matlab are used, iso-line mapping is possible using detector data. This is where the first community post about iso-line comes from Displaying IsoLux Lines | Zemax Community#Define detector object numberdetnum=3# get number of pixels in X, Ydims_bool_return, X_detectorDims, Y_detectorDims = TheNCE.GetDetectorDimensions(detnum, 0, 0)# Create array to store flux data for each pixelpix = []length = pix.__len__()while pix.__len__() < X_detectorDims * Y_detectorDims: # loop through pixels, store value in pix length += 1 pix_bool, value = TheNCE.GetDetectorData(detnum, length, 1, 0) pix.append(value)# get size of the detectorXlength = TheNCE.GetObjectAt(detnum).GetObjectCell(ZOSAPI.Editors.NCE.ObjectColumn.Par1).DoubleValueYlength = TheNCE.GetObjectAt(detnum).GetObjectCell(ZOSAPI.Editors.NCE.ObjectColumn.Par2).DoubleValue# make a pixel array to 2D d