The download contains 3 Python scripts:a script to read / parse a ZRD (Zemax Ray Database) file a script to read / parse a Binary ZBF (Zemax Beam File) file a script to read / parse a Binary DAT / SDF Source File  Click here to download Date Version OpticStudio Version Comment 2022/01/01 1.0 - Creation

Title. I can easily get the entry/exit points into a GRIN lens via tracing rays to a surface using SingleRayNormUnpol() and BatchRayTrace.However, this only gives me the entry/exit points into a surface. Is there a way to get information out about the beam path within a GRIN optic via ZOS-API?As an additional note, the GRIN optic is modelled via a custom *.dll extension I developed (not a ZEMAX Gradient 1-12 surface).My alternative is to write my own GRIN raytracer for the intermediate steps.

Hello guys, I have a multimode fiber of 1mm core (1000 um) of 0.22 NA. I will be using this fiber to deliver my laser beam of wavelength either 450 nm or 530 nm. The beam after the fiber will be collimated and then will be refocused. The final goal to have a spot size of 50 - 60 um at the focus. I am beginer in zemax and any help would be appreciated. If any of you had done similar project in the past it would be helpful if you could share the file and i could use it as starting point. Thanks a lot.

Hello everyone,I'm trying to extract the combined Huygens Point Spread Function (PSF) of a multiconfiguration system using either ZPL or the ZOS-API. In OpticStudio, I can achieve this directly by selecting "All" in the configuration button under the Huygens PSF settings, which provides the result I need. However, I'm having trouble replicating this setting in ZPL or ZOS-API, as I haven't been able to find an equivalent command or setting to retrieve the combined PSF programmatically.Has anyone here managed to access this setting through ZPL or ZOS-API, or is there an alternative approach to obtaining the combined Huygens PSF across configurations?Thanks in advance for any guidance or examples you might be able to provide!Cheers!

Question 1: what de Ex and Ey mean? I cannot find answers in user manuQuestion 2: non-sequential mode launches rays in a partial random manner, how Hx, Hy, Px, Py work for random rays? 

I wrote a macro to do this but it is slow (line by line).  Is there a build-in method to do this?  I can’t find it in the user manual. Thanks! sub clear_all_lenses    num_s = nsur()    if (num_s > 2)        for i, num_s-1, 1, -1            !print "delete surface ",i            delete i        next    endifreturn

We recently implemented the Geometric Image Analysis in ZOSPy 1.30. While doing so, we noticed that the setting PlotScale seems not to exposed in the ZOS-API for this analysis. Is that correct?

I searched in the help files but didn’t find one.  Thanks.

Need help to run through the ZOS-API C++ sample.  In zosapi.h:#import "C:\\Users\\gangs\\OneDrive - kochind.com\\Documents\\Zemax\\ZOS-API\\Libraries\\ZOSAPII.tlb"#import "C:\\Users\\gangs\\OneDrive - kochind.com\\Documents\\Zemax\\ZOS-API\\Libraries\\ZOSAPI.tlb"// Note - .tlh files will be generated from the .tlb files (above) once the project is compiled.// Visual Studio will incorrectly continue to report IntelliSense error messages however until it is restarted.But the *.tlb files were not generated after build and restart the Visual Studio, and can’t proceed.Thanks,

This DLL models a Vortex Phase Plate. It is useful in laser applications to convert a Gaussian laser beam into a donut-shaped energy ring. For more information, check the following links:https://www.holoor.co.il/wp-content/uploads/2017/11/vortex_zemax_tutorial.pdfhttps://www.holoor.co.il/application/optical-vortex-phase-plate-application-notes/https://www.holoor.co.il/optical-calculator/vortex-lenses/ The Vortex phase plate is a phase surface:   Click here to download Date Version OpticStudio Version Comment 2021/03/20 1.0 - Creation  

Hi Everyone,I would like to ask how to use zbftilt? The help document reads a bit confusing: This keyword requires the name of the ZBF file and four numbers. The phase of the beam is modified by a phase angle given by θ = ( x – cx )tx + ( y – cy )ty . The cx and cy values are the center of the phase tilt, and tx and ty are the slopes of the tilt in units of radians per lens unit length. The coordinates x and y refer to positions within the beam file, with the center coordinate (x = 0, y = 0) being at the point (nx/2 + 1, ny/2 + 1) where nx and ny are the number of points in the x and y directions. The length units in the ZBF file are converted automatically to the current lens units. The resulting data is written back to the same file name. If I want to rotate an elliptical beam mode by 90°, how should I write it?Thanks!Di

I have created a custom object based on the sample of the HalfCylinder.DLL object. So far, this works. I would like to return a value directly to the non-sequential component editor. E.g. for the half cylinder, add a field volume and return the current volume. This way during optimization, I can control the volume of the cylinder without using extra scripts to use the volume. I tried to use an extra field, and then attribute a value inside the code:in the given half cylinder, in line 64 (just before the switch(code)):data[104] = volume;but the volume field in zemax’ non-sequential component editor is not updated.I hope to get along the idea of I want to do. For the volume, I could use a script in zemax, but imagine it is value that I calculate in cpp anyway, it would be more efficient to reuse this. Is this possible?

In OpticStudio, currently we only support one dimensional grating. However, it's not difficult to simulate 2D grating. Here we will show an example using diffractive DLL.You may compile it with the instructions or use the DLL file attached to this article. Before we start, here are some articles for required background knowledge that we will not repeat in this forum post. How diffractive surfaces are modeled in OpticStudio (KBA) How diffraction ray-tracing is calculated | Zemax Community(forum post) Custom DLLs in OpticStudio: An overview of user-defined surfaces, objects, and other DLL types (KBA) How to compile a User-Defined DLL (KBA) Let's simply open the attached cpp file and observe how it works in non-sequential mode.This example is mainly modified from the built-in sample \Documents\Zemax\DLL\Diffractive\diff_samp_1.c To compile the program as C++ code. We package the functions with extern 'C'.  In this example, we only want to return diffraction ray direction and its rel

The attached ZPL will calculate the air space gaps between all elements and then will place the annotation text on the Windows clipboard.  After you run the script, simply open the Edit Annotation window, paste the text and click the Use Annotations checkbox: For the Double Gauss 28 degree field.zmx, the 3D Layout will look like:and for the Cooke 40 degree field.zmx: Limitations:You have to use the 3D Layout and not the 2d Layout.  The 3D Layout uses global coordinates for annotations while the Layout uses “window” units, meaning the values for LINE and TEXT would change based on the current zoom position. For complete control, you should use LINE3D and TEXT3D (this would allow you to place things like Comment, Radius, or Material on the plot as well.  For this simple example of air spaces, we will use MEASURE3D which is slightly easier to implement. Since we're only looking at air spaces, you need to consider when you “enter” a cemented element (doublet, triplet, etc) and when you “ex

Hi, Is there a way to change variable from float to integer?I want to use it to write list of polygons in loop:for i:n:polygon_name 1.pobpolygon_name 2.pobpolygon_name 3.pob….In other words, i dont want something like that: Thanks,Nadav….. 

can I calculate and get operand IMAE without adding it to MF with python api?IMAE work as geometric image analysis? what if I need “geometric bitmap image analysis”?they have different settings and from it different efficiency values. 

Hi I am working on to create a multifocal IOL. I don’t know how much add power is in the FFT through focus MTF. It shows the focus shift. how to convert t the focus shift into diopters or is there any option in the zemax for conversion. Regards,C.Karthick

I have used User-defined DLL (Source DLL) by myself with compiling CPP to DLL. It is working well in 2023 R2 but it can’t be loaded in 2024 R1. Is there some difference in loading DLL? Please let me know if there is someone who has experience. Thank you. Best Regards,Munseok

I’m working on a pair of DLL files. The sag of the second DLL depends on the parameters of the first DLL, plus a few other parameters. What’s the best way to share information between these two user-defined surfaces? Do I need to add pickups for every parameter (manually or via script)? Or is there some way to pass the entire 1st surface as a parameter/argument to the 2nd surface?

The program in the following file assigns random values ​​to the specified Zernike terms. This ZPL works in non-sequential mode but not in sequential mode.Where do I need to modify it to make it work in sequential mode?Lens data is attached in another file.

There is minor typo in the current help file for Zemax OpticStudio. I caught it in the PDF for 2024 R1; however, it is present in the online help file from Ansys as well discussing Numeric Functions.In the description of the obselete STDD() tag for ZPL programming, it references SRPO which does not exist. It meant to reference SPRO.Confirmation that SPRO is correct can be found in @Katsumoto Ikeda’s post here. 

This User-Defined Surface DLL provides a realistic model of relief-type diffractive lenses based on zone-decomposition. Using zone-decomposition, diffraction into multiple orders can be accurately considered at once, and this method inherently accounts for wavelength dispersion and diffraction efficiency by modelling the actual shape of the diffractive element.Application examples include the creation of advanced intraocular lens models, where the different orders are designed to provide sharp vision for multiple viewing distances, thereby substituting accommodation of the natural crystalline lens.This application is discussed in detail in the following knowledgebase article:Realistic modeling of relief-type diffractive intraocular lenses using User-Defined Surface DLLs – Knowledgebase (zemax.com)  Click here to download Date Version OpticStudio Version Comment 2022/07/15 1.0 - Creation  

This Source DLL models an Astigmatic Gaussian Source.  It is based on rays but the statistical distribution of rays gives a picture of a diffracting Gaussian beam. It is valid for small angles (paraxial approximation) and when propagating in free space. So clipping at apertures and aberrations will give incorrect results.w0x, w0y are the real beam waist radii (defined at the 1/e2 intensity point) in the XZ and YZ planes. They includes M^2. z0x, z0y are the positions of the beam waist in the XZ and YZ planes. z0<0: in propagation direction if the waist is located before source. M^2x, M^2y are the quality factors in the XZ and YZ planes.For more information, see "Representation of a Gaussian beam by rays" by P. P. Crooker, W. B. Colson, and J. Blau - Physics Department, Naval Postgraduate School, Monterey, California 93943Authors:Steffen Erhard and @Dirk Broemme    Click here to download Date Version OpticStudio Version Comment 2020/05/06 1.0 21.1.2 Creation 2023/0

Hello Everyone! During the discussions with the Zemax staff, we came across something that might be useful for everyone. This has to do with working in Python with the ZOS-API. As it is generally known, Python does not have IntelliSense in the same sense as Matlab does. The standard workaround (https://my.zemax.com/en-US/Knowledge-Base/kb-article/?ka=KA-01620 ) has been inserting break points and debugging your code to see the functions and the properties. Below is a different way that can enhance the working speed in Python. However, I should note the following. At the moment of writing this, the method works only with Python 3.8 (Tested on Python 3.8.1). The precise reason for why it doesn’t work in, say 3.7, is not clear to me, but maybe Zemax staff can provide some feedback on this? Anyway, in order to get the method to work, I required the following. As an IDE - the Visual Studio Code from Microsoft: https://code.visualstudio.com/ . Tutorial on getting started with Python

Fellow ZPL programmers,I want to share some of the tools that I use for editing ZPL scripts and code.I use Microsoft Visual Code Studio to edit the ZPL files.I also use an extension from Hiiragi that enables support for ZPL in VS Code. It provides syntax highlighting and some code completion through IntelliSense.For IntelliSense, I would disable the option “Editor>Suggest: Match On Word Start Only”. This allows you to type “MERIT” and pull up all the tags that contain “MERIT”.Option to enable “Fuzzy Search”Example of Code Completion,Example of Code Completion with DEFAULTMERITExample of Sanjay’s PLOT_TEST.ZPL script with indentations provided by me to enable code folding.Example of Sanjay’s Code in VS Code without Code Folding Example of Sanjay’s Code in VS Code with Code FoldingHiiragi supports and requests community contribution to the repository. Please consider supporting the project and providing feedback to Hiiragi, forking the repository, etc.