Hello everyone, I tried to use the “Voxel Maker.ZPL” macro provided in the following article: How to show Detector Volume data in 3-D, but even though no errors appear, it doesn’t create any imported CAD. Is there any new version I can use?Thank you! 

.

Hello, I am using code in ZPL which include exporting of objects (non-sequential mode) to CAD files-created by Zemax community:SUB export  IF PureNSmode == 1    start_number = num_objects + 1    end_number = new_object - 1  ELSE    start_number = surf_no    end_number = surf_no  ENDIF# Export the solid objects as CAD files  VEC1(1) = ext           # CAD file type  VEC2(2) = 8             # spline segments  VEC1(3) = start_number  # start surface  VEC1(4) = end_number    # end surface  VEC1(5) = 1             # ray data layer  VEC1(6) = 0             # lens data layer  VEC1(7) = 0             # do not export dummy surfaces  VEC1(8) = 0             # do not export surfaces as solids  VEC1(9) = 5             # ray pattern NONE  VEC1(10) = 0            # number of rays = 0  VEC1(11) = 0            # wavenumber  VEC1(12) = 0            # field number  VEC1(13) = 0            # do not 'delete vignetted'  VEC1(14) = 1            # dummy thickness      VEC1(15) = 0            # do not split ra

Hello,I have a question about NSC by Python program optimization.The program must iteratively run the local optimization defined by Zemax.However, after running some local optimizations, the optimization becomes very slow.How to speed up the optimization of Zemax NSC through Python programs?

Hi,How do I know where my macro files are stored? are they in the general Zemax/macro directory or in the local project? After assuming its local, when reopening the file (after closing Zemax) it went to the general one instead. Is there a way to control this? Thanks

Hello, I am very new to ZOSAPI - python programming. I am simply following the article - https://support.zemax.com/hc/en-us/articles/1500005489681-Connect-to-OpticStudio-from-Python-with-the-ZOS-API-Interactive-ExtensionI am using pycharm IDE and running pythonZOSconnection6.py from it (as suggested, in running this in python console). Upto this point, everything seems to be working fine. I see the prompt in optics studio (given below) with the status : connected. OpticsStudio Connection made  All the variable are also loaded : Variables Defined  However, I don’t see this feature “It means that there is an “Intellisense” when working with the Interactive Extension” .Missing Intellisense That is, none of the methods of ZOSAPI are loaded. And if I try running the example code (as suggested in the article), I am getting an error, “ModuleNotFoundError: No module named 'ZOSAPI'” . ModuleNotFound ErrorI have already installed Pythonnet package, which helped to make the first connection with

That example is a Python script to convert source file between Zemax and SPEOS. To learn more about that converter, check our article: https://support.zemax.com/hc/en-us/articles/4416068530579-SPEOS-and-Zemax-Source-file-converterDownloadFor more information about Ansys optical_automation, click here. TroubleshootingIt’s possible that we get an error message:Non binary files not supported.This happens when the file is not stored in form of ones and zeros, or in some other binary (two-state) sequence.Zemax source fileFor Zemax source file, the extension SDF is recommended, and DAT is supported only for backward compatibility. The file format may be either text or binary. This is mentioned in The Setup Tab > Editors Group (Setup Tab) > Non-sequential Component Editor > Non-sequential Sources > Source File. You can put a detector close to this source file and save the ray tracing data as new source file to convert the non-binary source to a binary one.Speos source fileAs for S

Hi, I have a Zemax OpticStudio version 16.I'd like run Python in this version. Could anyone know how to start it?Best Regards

Hi, I run a Python program in Zemax OpticStudio version 16. But it show as following error. How do I fix it?    aKey = winreg.OpenKey(winreg.ConnectRegistry(None, winreg.HKEY_CURRENT_USER), r"Software\Zemax", 0, winreg.KEY_READ) 

This Surface Scatter DLL models a Lambertian scattering and contains a depolarization fraction parameter to depolarize part of the scattered rays. That DLL is a good example to demonstrate how to control the electric field and how to implement importance sampling. The code is based on "{Zemax}\DLL\SurfaceScatter\Lambertian.DLL".  Click here to download Date Version OpticStudio Version Comment 2019-01-13 1.0 - Creation  

Hi, I used Rust to build a very simple DLL, inspired by the examples in C and C++ provided with Zemax. The source code can be found here. I compiled it from Windows and a Unix machine with cross compiling. Both versions were as fast as the C alternative I wrote. The compilation method is pretty straightforward and documented in the repo README.It was quite easy to implement similar workflows and structures for some of the other types of DLLs used in Zemax.Yet, I would like to do the same with the 2D version of the diffraction grating. I could only find mentions to the 1D grating in the Zemax docs. The provided code sample covers only a portion of the elements of the pointer and not all of them are fully documented. Does anyone have that piece of information?

Hi, Is there any one know that how to change the target file in the NSC Bitmap Wizard of merit function editor by using Python?

Hi all, I’m not going to create a repository for this, but if you quickly need a modulo operator in your Merit Function, there you have it. Hx and Hy are the operand numbers (integer) that will be used as the numerator and denominator respectively.The relevant part of the code is self-explanatory (hopefully):int numerator = (int)TheApplication.OperandArgument1;int denominator = (int)TheApplication.OperandArgument2;...double numerator_value = TheSystem.MFE.GetOperandAt(numerator).Value;double denominator_value = TheSystem.MFE.GetOperandAt(denominator).Value;operandResults[0] = numerator_value % denominator_value;To install, download the ZIP file, extract it, and move UDOC12.exe to yourDocuments/Zemax/ZOS-API/Operandsfolder. Then, in the MFE you can do:The rest of the division of 5.00 by 2.00 is 1.00.In case you are wondering why I made this. I needed to have a linear polarization without caring about the orientation. I noticed that using CODA with data=110 (phase difference), some linea

Hello,A comment on ZOSPy. I did already spent countless hours on my own python wrapper and I am very happy to see a team of skilled programmers working on that. Just getting rid of tons of boilerplate code is worth the effort!Getting connected to Zemax from my jupyter-lab to zemax as “Interactive Extension” works with ZOSPy or with the pasting several lines of boilerplate and directly acessing ZOS-API via pythonnet 3.x.Via ZOSPy I can add lenses, changes become visible in zemax. So I assume there is no general problem with library loading, connecting, etc..However, I cannot figure how to run a FFT MTF using ZOSPy.  With the bare pythonnet this looks like this (Boilerplat-part from example 04 skipped)# Create analysisTheAnalyses = TheSystem.AnalysesnewWin = TheAnalyses.New_FftMtf()# SettingsnewWin_Settings = newWin.GetSettings()newWin_Settings.MaximumFrequency = 50newWin_Settings.SampleSize = ZOSAPI.Analysis.SampleSizes.S_256x256FFT MFT Window appears.And afterwards# Run AnalysisnewWin.

I was just testing a macro when I noticed something strange. The number shown in the Edit/Run UI does not match the actual line number in the ZPL macro editor. I grabbed this image while the UPDATE ALL line was running, but the Status indicates line 5 is currently running. Line 5 is just a comment. It appears the lines with “!” are being ignored by the status indicator. For reference, I am using Zemax OpticStudio 23.2.1  

I am trying to write a custom GRIN *.dll file for non sequential mode that will allow me to limit refractive index above or below a certain value and just set it to a constant. However, I am having a hard time defining the derivatives to return as required in the GRIN *.dll files. As an example, if my refractive index looks something like below: I would like to cut everything off above and below a certain threshold, even if my n(x,y,z) function gives me a value thats within it. I have currently been doing this with just a merit function and limiting index that way, but would like to be able to just programmatically restrict it. I also tried a variant where I set the derivatives to 0 or ignored them, but had errors tracing the rays. Anyone have a good solution? Happy to provide any files needed.

In OpticStudio, We can load any spectrum file from our   \Objects\Sources\Spectrum Files Folder .Here is the available code for Matlab and Python. You can use this code in Standalone or Interactive Extension.-Copy the code in your file .-Change the path of testfileMatlab Code: import ZOSAPI.*;TheSystem = TheApplication.PrimarySystem;sampleDir = TheApplication.SamplesDir;testFile = System.String.Concat("C:\test\ZPO\Diode sample.ZMX");   NSCE = TheSystem.NCE;Obj1 = NSCE.GetObjectAt(1);  Source_Color=Obj1.SourcesData.SourceColor;Source_Color=ZOSAPI.Editors.NCE.SourceColorMode.SpectrumFile;filesAvailable = Obj1.SourcesData.SourceColorSettings.GetAvailableSpectrumFiles();FileToSelect=filesAvailable(6);Obj1.SourcesData.SourceColorSettings.SpectrumFile=FileToSelect;    Matlab Interactive Extension Python Code:testFile = r"C:\test\ZPO\Diode sample.ZMX"TheSystem.LoadFile(testFile, False)print(TheSystem.SystemFile)NSCE = TheSystem.NCEObj1 = NSCE.GetObjectAt(1) Source_Color=Obj1.SourcesData.Sourc

Hello! I am trying to extract the data for a non-sequential volume detector for intensity at each X and Y coordinate along a Z slice for each Z slice. The intention is to eventually make an interactive python plot with a cross section, but I am struggling on actually extracting the detector data using the python API? Anyone have any tips? Thanks :)

Hi everyone,I would like to change the surface properties with Python ZOS-API.How can I change the follow parameter from “Explicit” to “ Reverse Thhis Surface”?Thanks for help.

Hi community, I am using Python API to perform local optimisation and wanted to display the number of cycles taken for optimising a design. I tried the following code and print the value for LocalOpt.Cycles, but the output was zero:Code:# Local optimisation till completion    print('... Running Local Optimization ...')    LocalOpt = TheSystem.Tools.OpenLocalOptimization()    LocalOpt.Algorithm = ZOSAPI.Tools.Optimization.OptimizationAlgorithm.DampedLeastSquares    LocalOpt.Cycles = ZOSAPI.Tools.Optimization.OptimizationCycles.Automatic    LocalOpt.NumberOfCores = 8    print('Initial Merit Function:', LocalOpt.InitialMeritFunction)    t = time.time()    LocalOpt.RunAndWaitForCompletion()    print('Final Merit Function:', LocalOpt.CurrentMeritFunction)    print('Cycles:', LocalOpt.Cycles)    # Get the elapsed time.    elapsed = time.time() - t    print('Time elapsed: ' + str(round(elapsed,3)) + 's') Output... Running Local Optimization ...Initial Merit Function: 3.6106045608778228Final M

Dear all:I'd like to run a program organized by python. But it can only be executed once as following.In [1]: runfile('D:/untitled1.py', wdir='D:')In [2]: runfile('D:/untitled1.py', wdir='D:')Reloaded modules: CLR, clr, ZOSAPI_NetHelper, ZOSAPITraceback (most recent call last):  File "D:\untitled1.py", line 139, in <module>    zos = PythonStandaloneApplication()  File "D:\untitled1.py", line 20, in __init__    clr.AddReference(NetHelper)AttributeError: module 'clr' has no attribute 'AddReference'I use the anaconda 64 bits with spyder 5.3.3.I have installed the pythonnet by pip install pythonnetAnd it seems working normally so the program can be run once. But it cannot be run more than twice.Does anyone encounter this problem before? 

Hi, I followed the sample script and extract the mtf data usingxRaw = data.XData.DatayRaw = data.YData.Data and what I realized is that the MTF is not given in integer location. instead of report the MTF at 50lp/mm it’s reporting MTF at 49.9136879lp/mm. is there any way to get the MTF right at the rounded location? Thanks,Yu

I've tried running the example file PythonStandalone_02_NSC_ray_trace.py and realized that it fails when trying to read out ObjectData:numXPixels = obj.ObjectData.NumberXPixels;Result: AttributeError: 'IObject' object has no attribute 'NumberXPixels'.The code runs flawlessly, except when reading ObjectData. I have spent a full day trying to debug this error without success.I have also tried the methods outlined in PPG example not working | Zemax CommunityandZOS-API Python: How to deal with AttributeError and apply the correct enumeration | Zemax Communitywithout success. Does anyone know how to continue debugging?Note: using Zemax OpticStudio 22.2.1

Hi, I have read this knowledgebase article on how to use pythonnet with ZOS-API. It suggests using Python 3.4 to 3.8. Yet, 3.4 to 3.6 have reached end of life, 3.7 will in 3 months and 3.8 next year. Also, pythonnet 2.5 is no longer maintained. The only active development is focused on version 3+.I would like to use ZOS-API work with modern versions of Python, 3.10+. The only pythonnet version compatible with them is 3+. Under these versions, quite a few ZOS-API calls are broken. For example, IZRDReaderResults.ReadNextSegmentFullraises an exception due to how pythonnet 3+ handles the conversion of int32 and Enum between .NET<->Python.Is there any way to use ZOS-API with these modern and maintained versions? Note that I don’t believe that using Python 3.8 or 3.9 with pythonnet 2.5.2 is a good solution, because pythonnet 2.5.2 is not actively maintained. The pythonnet team has stated multiple times that features/bugs would only be added/fixed in 3+ (for example here). Thank you,Tho

Hi community,I experienced some unexpected behaviour with ZOS-API (Zemax 2024 R1.00) and Python (3.11).I tried to set the surface opacity of a surface in a sequential system via ZOS-API, but it did not work; the surface opacity maintained its default value of 100 %. The following codeapp = ZOSAPI.ZOSAPI_Connection().CreateNewApplication()lde = app.PrimarySystem.LDElde.InsertNewSurfaceAt(2)surface2 = lde.GetSurfaceAt(2)surface2.TypeData.SurfaceOpacity = ZOSAPI.Common.ZemaxOpacity.P50print(str(surface2.TypeData.SurfaceOpacity))yields “P100”, indicating that the surface opacity was not affected.When I tried to find the source of the problem I noticed that the surface opacity is somehow affected by the setting of the surface color. To investigate, I set all possible combinations of surface color and surface opacity and subsequently read the actual values color_get and opacity_get (full code at end of post): color_set color_get opacity_set opacity_get0 Default Default P00