Hello Community, I am working on making a macro and would like to know how I can set the object type, for example, Source Two Angle.There is only one example that Standard Lens to be described as “NSC_SLEN” in the ZEMAX Manual and I cannot find the information for other objects.Your support would be greatly appreciated.Thank you. Kind  regards,Ryo

How does one do a bulk raytrace in ZPL, similar to pressing the “Ray Trace” button in regular, non-sequential mode. From the help files, it looks like RAYTRACE and RAYTRACEX only traces one particular ray, which is not useful for determining the total illumination on a detector. Thanks!

Hello,I would like to get Tolerance Sensitivity Data in Tolerance Data Viewer through Python-API.I know how to get Criterion Value in Python-API, but I don’t know how to get COMP Value in each row. ZOSAPI.Tools.Tolerancing.ISensitivityData.GetCompensator(index) treate just statistics value, not each comp value in Tolerance Operand.Do you know how to get comp column data in Python-API?Thank you Hideki Nishioka  

I am trying to tilt a surface by ZPL command 'SURP 10, 63, 5' to tilt the lens by 5 degree (10 is the surface number). But the lens is not tilted. Could anyone give me the clue why? Thanks!

Hi everyone, When specifying custom boundary constraints, I was using the Default Merit Function as a template, moving the default boundary constraints above DMFS and making my edits there.I created a simple user-extension to speed up this process. This user-extension creates default boundary constraints at the top of a sequential Merit Function. It uses the default values (Min: 0 | Max: 1e+03 | Edge Thickness: 0) and only creates the relevant operands. If it is an air space it only creates MNCA, MXCA, and MNEA. If it is a glass space it only creates MNCG, MXCG, and MNEG.Small update: it only adds boundary constraints to thicknesses that are variable.Maybe this can be useful for someone else.Take care, David

I recently upgraded to version 21.1.2 and started getting this error when I am trying to run the code I had no issued runnign previously. Is there a new licensing model in place?

Hi All, how can I read the Centroid-X/Centroid-Y value from the Detectorviewer in ZPL?Thanks in advanceJannis

DescriptionOutput of the macro with some additional post-processing in ExcelThis macro may be used as a basis for gathering field-by-field ray data in equal steps across the pupil. In this macro, the angle of incidence on a surface is reported but the operand may be changed to any that uses normalized ray coordinates.  LanguageZPLDownload    Click here to download the ZPL version Click here to download the Excel API version Date Version OpticStudio Version Comment 2019/12/10 1.0 19.8 Creation 2020/09/20 1.1 20.2 Updates for OpticsTalk+Envision. Cleaning up the output. Additionally, a reformatted version has been made available which splits the calculation into child/parents macros.  

DescriptionThis macro allows users to apply the "Make Thermal" tool to already-generated Monte Carlo files. The amount of MC files is hard coded into the code. This will apply five Multi-Configuration operands per surface: CRVT, THIC, SDIA, CHZN, MCSD. MC operands for extra data parameters are not included for all surface types.LanguageZPLDownload    Click here to download Date Version OpticStudio Version Comment 2019/10/15 1.0 19.4SP2 Creation 2020/08/18 2.0 20.2 - Updates to formatting - Addition of option to choose not to clear the MCE before applying the Make Thermal tool - Addition of a loop which will check for the Even Asphere type. This will add parameters to the MCE which correspond to the asphere’s extra data parameters

Hi, I tried to trace some ray in C++ through a simple test lens file with two surfaces after the lens and the IMAGE surface (see file).I create a batch with CreateDirectunpol() function but I noticed two behaviors that seemed strange to me : when I set  toSurface  parameter to a negative number (CreateDirectUnpol(1000, RaysType_Paraxial, 0, -1)  for example), no error are thrown, and the function does not return nullptr. Even more strange, I could add rays, trace them and read output result. Obviously, rays were unchanged. when I set toSurface parameter to TheSystem->LDE->NumberOfSurfaces, I have the exact same output as TheSystem->LDE->NumberOfSurfaces - 1.Do you have any explanation for these behaviors ?Thanks 

An Interactive Extension was created that will automatically save flux/area data of all Detector Rectangles to TIF images having double data type. This follows a post from David Nguyen and support feedback from Sandrine Auriol and Alexandra Culler,Script was tested with Samples\Short course\Illumination & Stray Light\Double Gauss for Sun Shield.zos. The images "Double Gauss for Sun Shield, Field 1, D11.tif" and "Double Gauss for Sun Shield, Field 1, D12.tif" were created, then opened using ImageJ.  The images will be uninteresting unless rays are traced before the extension is run.LoopOverAndSaveDDRs(TheSystem) is in a separate file from the Interactive Extension boilerplate so that it could also be used from a Standalone Application, though this has not yet been tested.Language: Python   Click here to download Date Version OpticStudio Version Comment 2021/11/01 1.0 - Creation

Hello,I was wondering, if there is a ways using the API to reload the zemax file to its default.Every single time, I am using the API, I need to start a new instance of OpticStudio. However, it would be nice, to simply reload the file, that I am working on, in order to save some time. Is there a way to do something like this? 

 This macro reads the RMS spot X and RMS spot Y as computed in the Standard Spot Diagram and returns it.The argument Hx can be used to give the number of fields.To be able to use it as a ZPLM, change the name to ZPL13.ZPL

Sometimes, we may design the system starting from the 'image' back to the 'object'. For example, this is often the case for those systems that are designed to be viewed by eye, like AR/VR, HUD. In this case, normally, if we want to check the relative illumination, we need to reverse the system to check because the tool 'Relative Illumination' only calculates that on last surface in the system.Here we will provide another way to calculate it using a macro so that you don't need to reverse the system.Note here we at the same time is also demoing how you can verify the calculation theory of the RI. RI is actually much easier to calculate if the system is reversely designed! First, by reading the following forum post, we know that relative illumination at each field is exactly linearly dependent to the area of the beam in cosine space in image space.So, here is the plan. We want to write a macro to calculate the beam area in cosine space for each field, normalize it, and then get the the R

Set customize ribbon (File>Options) to enable Developer tab in Excel Open VBA through Developer> Visual Basic It is required to load the ZOS-API assembly at the beginning. The macros can be checked from VBAProject> Modules  Open the linked Excel file (with macro included), the Connect button and Surface Data button are linked to different macros.   Click Interactive Extension, then the connect button. A message box will pop up and show the connected message.   7. Click Surface Data button, LDE and FDE data of the current active lens file will be extracted 8. Click any surface button from the generated surface button list, incident angles of rays on the target surface that tracing across the whole pupil from specific field will be retrieved and displayed on a newly opened sheet.    Find the files here on the Code Exchange here: ZPL Macro: Read optimization operand across pupil | Zemax Community  

 This tool calculate radiance or luminance (brightness) of objects seen by human eyes.Language: CS    Click here to download Date Version OpticStudio Version Comment 2021/05/27 1.0 21.2 Creation 2021/06/03 1.1 21.2 Add function to export text files 2021/06/11 1.2 21.2 Bug fix 2022/04/16 1.3 22.1 Bug fix when showing luminance data 2022/04/19 1.4 22.1 Bug fix. Now the extension file name is no restricted to lower case.

I’d like to programmatically adjust the value of a Parameter cell in the Non-Sequential Editor, something like:TheSystem.NCE.GetObjectAt(obj_num).GetObjectCell(cell_num).DoubleValue = value;However, GetObjectCell only takes a ObjectColumn enum as an argument, and the ObjectColumn enum does not seem to accept assignment from an integer.  I can write a lengthy switch block that returns the appropriate ObjectColumn enum based on an integer input, but that seems like an ugly solution, when (according to the manual), the enum value for the Parameter columns is the parameter number plus 10, i.e. the following should work:TheSystem.NCE.GetObjectAt(obj_num).GetObjectCell(param_num + 10).DoubleValue = value;However, this generates an error.  I tried using cast, e.g.param_col = cast(param_num + 10, ‘ZOSAPI.Editiors.NCE.ObjectColumn’);but this generates an error.Any suggestions appreciated.

This Zemax User-Extension displays the envelope of a Gaussian Beam. The Gaussian Beam characteristics are calculated by the Paraxial Gaussian Beam calculator. The extension adds a Non-Sequential Component at the bottom of the sequential editor. A Freeform Z object is added to the Non-Sequential Component Editor. It is formed with the different sizes of the beam calculated by the Paraxial Gaussian BeamLanguage: CS   Click here to download Date Version OpticStudio Version Comment 2020/03/24 1.0 20.1.1 Creation

Hi,I would like to calculate the coupling efficincy into different few mode fibers. For this I would need the complete E and H vectorial fields from POP. Is obtainng the [Ex(X,Y), Ey(X,Y), Ez(X,Y)] and [Hx(X,Y), Hy(X,Y), Hz(X,Y)] of a field possible in zemax? If so what is the best aproach? Thank you.  

Regarding the SETVAR ZLP keyword, want to use a variable to define the ‘Pn for parameter n’. I need to concatenate “P” with my index variable i. How do I accomplish this?Thank you,John 

In the optimization process, we usually have to set a suitable space between two lenses to avoid overlapping lenses. However, the current merit function operands don’t support the lenses with coordinate break. A possible solution is to use ZPLM to get the minimum distance between two surfaces with coordinate break.How to use it:The parameter Hx: the surface number of surface  ①.The parameter Hy: the surface number of surface ②.Data=0: Get the minimum distance between two surfaces along the surface ① local z axis.Data=1: Get the maximum distance between two surfaces along the surface ① local z axis. Limitation of this ZPLM:The minimum distance between two surfaces means the distance is along the surface ① local z axis. In the code, the reference of global coordinate surface is temporary set as the surface ①, and then restore to the original setting after calculation. Only the yellow overlapping area in the figure below will be considered, beyond the range will not be considered. In the

This ZPL operand (ZPL30) computes the top and bottom edge thickness of a Doublet at the Semi-Diameter. It also computes the difference. By default, OpticStudio measures the edge thickness at the lens semi-diameter or mechanical semi-diameter.Language: ZPL  Click here to download Date Version OpticStudio Version Comment 2019/01/01 1.0 - Creation  

Hi guys I have a very simple POB object which is just a wedge, and I’m trying to see how the angle between the internal and external reflective surfaces change with tilt angle rotation around x. I can do this fine in OpticsStudio, by altering the TiltAroundX in the non-sequential component editor. Screenshot of simple designI then made a C# standalone app, so that I could control what I wanted programmatically.  I open up the file, no problems: IOpticalSystem TheSystem = TheApplication.PrimarySystem;            // Add your custom code here...            ///open relevant file            bool SuccessfulFileOpen = TheSystem.LoadFile(FQP,                saveIfNeeded: false            );            Console.WriteLine("File succesfully opened: " + SuccessfulFileOpen);            Console.WriteLine(FQP); I then access the object to make sure it’s thr right one:INonSeqEditor NCE = TheSystem.NCE;            INCERow Object_n = NCE.GetObjectAt(ObjectNumber: 1);            Console.WriteLine("Object

All,What is the ZPL command to execute the ‘Convert to NSC Group’ function available via the GUI? I want to convert and save many (Monte Carlo) files in a loop.

This Matlab code shows the possibility to export optical components by using ZOS-API. In this example Matlab code exporting optical components from Layout of sample file Double Gauss 28 degree field.zmx. The final results exported as 3D figure in Matlab .Limitations: Unable to fetch the rays from the Layout and shaded Model.You will need modify the Line 32 Path : TheSystem.LoadFile('FilePath\OpticStudioFile', false);Language : Matlab   Click here to download Date Version OpticStudio Version Comment 2021/09/03 1.0 - Creation