I’m converting ZPL macros to ZOS API using C#I’ve having a hard time finding the corresponding API for the macro SPRO(surf, code) with Code = 18From the macro documentation, code 18 will return the Glass Number (an integer?) for a Surface.Does anyone know the corresponding   ZOS API code? I currently use OpticalSystem.LDE.GetGlass() to get the glass name. How about accessing the glass number? 

NSCRayTrace = TheSystem.Tools.OpenNSCRayTrace(); NSCRayTrace.ClearDetectors(0); NSCRayTrace.SplitNSCRays = true; NSCRayTrace.ScatterNSCRays = false; NSCRayTrace.UsePolarization = true; NSCRayTrace.IgnoreErrors = true; NSCRayTrace.SaveRays = true; NSCRayTrace.SaveRaysFile = 'Digital_projector_flys_eye_homogenizer.ZRD'; NSCRayTrace.RunAndWaitForCompletion(); NSCRayTrace.Close(); Run NSC ray trace Logic = {'False', 'True'}; ZRDReader = TheSystem.Tools.OpenRayDatabaseReader(); prefix=TheSystem.SystemFile.TrimEnd('.ZMX'); ZRDReader.ZRDFile = System.String.Concat(prefix,'.ZRD') ; ZRDReader.RunAndWaitForCompletion(); if ZRDReader.Succeeded == 0 disp('Raytracing failed!\n\n') disp(ZRDReader.ErrorMessage) else disp('Raytracing completed!\n\n') end ZRDResult = ZRDReader.GetResults(); [success_NextResult, rayNumber, waveIndex, wlUM, numSegments] = ZRDResult.ReadNextResult(); while success_NextResult == 1 fprintf('\n\nsuccess_NextResult: %s, rayNumber: %d, waveInd

Hi, I’m a bit confused that when I run the quickfocus command in ZPL, Zemax doesn’t always give me the same value, somehow I had to run my macro twice to get to the correct back focal length (my macro also changed wavelength and field setting). Is it normal to have this? Also, what would be a solution to fix this in the macro? I tried having quickfocus command twice inside the macro but it doesn’t help. Thank you very much.[Mod note: moved to more appropriate forum for ZPL related discussions.] 

hi,it’s easy to make a DLL working as dichroic filter in the surface scatter way, by just changing the specular ray direction according to its wavelength in the DLL. however, it seems it only works in a 2D surface, and when it goes to a volume surface with different refraction index from the air, especially when the ray needs to reflect at the surface inside the volume, it can no longer work normally. examples illustrated as follows:I analyzed the cause through ray tracing and ray database viewer, and found that if the ray made reflective mandatorily inside a volume via the DLL  by one of its surfaces, zemax has no way to know the reflected ray by the surface is still inside the volume,  as it seems zemax does not provide such an interface in the function “UserScatterDefinition” .I hope to consult zemax development engineers and also guys with related experience, how to solve this? thx in advance!and I also wondering why zemax does not provide the incident ray direction cosines and why

Hello,This sample code demonstrates how to set solves from Excel API.The example below applies an F# solve:Dim Surface_Last As ILDERowSet Surface_Last = TheLDE.GetSurfaceAt(TheLDE.NumberOfSurfaces - 2)Dim Solver As ISolveDataDim SolveFNumber As ISolveFNumberSet Solver = Surface_Last.RadiusCell.CreateSolveType(SolveType_FNumber)Set SolveFNumber = Solver.[_S_FNumber]SolveFNumber.FNumber = 3.1Surface_Last.RadiusCell.SetSolveData SolverFor further examples about how to use the Excel API, please take a look at these sample files:ZOS-API and Excel | Zemax Community

 Hello,This sample code demonstrates how to change the settings and then run an analysis from Excel API.The example below uses the Single Ray Trace:Dim SRT As IA_Dim SRT_settings As IAS_RayTraceSet SRT = TheSystem.Analyses.New_RayTrace()Set SRT_settings = SRT.GetSettingsSRT_settings.Px = 0.5SRT_settings.Py = 0.5SRT_settings.Wavelength.SetWavelengthNumber (2)SRT_settings.Field.SetFieldNumber (2)SRT.ApplyAndWaitForCompletion 

Attached please find several files in a zip folder. The primary file is a Mathematica notebook initially intended as a knowledge base article.  It could also be a post in the Code Exchange forum. I have included a draft readme file in case you feel that is the best use. If you think it’s worth sharing, please use it as you think best.Please feel free to request edits.The files in the folder are:   The notebook: “An introduction to interfacing to OpticStudio from Mathematica 1_1.nb”   A PDF of the same: ” An introduction to interfacing to OpticStudio from Mathematica 1_1.pdf”   The readme draft: “ReadMe.docx”

I’m interested in modeling an OLED display that’s displaying the letter P.  The brute way to do this would be a series of lambertian point sources that form that shape.  Is there a better way?  Maybe with a dll or a CAD object? Thanks!Donna

I have a very simple question. How could I define a source Gaussian out from a single mode fiber, which core size is 4 micro, NA =0.12. I know the beam size (diameter) should be set to be MFD, how to put the parameter for position? should I put the parameter of the position as  Rayleigh distance Zr? or should I use MFD/(2*NA)? Thanks for your answer in advance.  

In this post, it’s introduced how to simulate realistic grid wire polarizer with RCWA function that comes with OpticStudio 20.2.(Source: https://www.thorlabs.com/newgrouppage9.cfm?objectgroup_id=5510) Note there are many different types of polarizerFor polarizer based on birefringent crystal, check the following article: How to design birefringent polarizers For polarizer based on coating, there is no an article specific to introduction, but users can refer to the following article to know how to set up a coating and assign to object for beam splitting: How to model a dichroic beam splitter Then it’s also worth to note the existence of a build-in ideal coating “PASS_P”. This coating allows P polarization to pass and reflect light with S polarization. Note the coating method can only work for obliquely incident beam. Usually this kind of polarizer is made as a cube or a plate oblique placed in the system. More information can be found in this forum post: 'Pass_P' coating fail for the mo

I have a custom FilePath that I pass into the above method and I am trying to check to see if it is valid so I can alert the user if OpticStudio was found on the local machine or not.  However, when I pass anything to the method the bool is true and only the HandleError() method in BeginStandAloneApplication() catches the incorrect FilePath input.  Can someone point out my error or offer any advise as to what is going on?  Thanks in advance.The method StartZos is the only method I have changed so far.TypePath is hardcoded to always be as 0 or 1.The solution compiles and works as designed expect for the bool issue.There is an XAML GUI calling the Program class.namespace CSharpStandaloneApplication{ public class Program { public static void Main() { } public static string StartZos(int TypePath, string FilePath) { bool isInitialized = false; if (TypePath == 0) { //Find the installed version of opticstudio automatic

I am looking at the ZOS-API Help file, but I’m not able to find a way to get the row number of the DMFS operand.My final goal is to programmatically build a DMF at that location. Should I scan the MFE rows 1 by 1 in a for loop, until i find that operand type?

Good morning, I’m trying to connect Zemax with Python and I know that ZOS API and PyZDDE are possible options to use. Now I wonder if it is possible to use PyZDDE with the latest version of Zemax OpticStudio or if some functionalities are not supported with this connection. 

Hello everyone,I was trying to find a simple way to remove pickups and variables for when I want to integrate a non-sequential system into another file. In the ZOS-API documentation I’ve found only a global removal for variables so far:TheLDE = TheSystem.LDEtools = TheSystem.Toolstools.RemoveAllVariables()Unfortunately, I was not able to find something similar for pickup-solves.So, I’ve written a very small python-file based on the boilerplate code that removes pickups and variables from a nonsequential Zemax-File which I’d like to share to the community. The code only changes the solve types: variables and pickups to fixed solve types to preserve other solve types (for example the solve type “model” for materials). Best regards,Sven  

Hello,I’m new in OpticStudio and I’m trying to use the macro Mapping Function Resolution created by OpticStudio that we can find here and implement it in my OpticStudio simulation.The modified code is the following: ! Calculate Mapping Function and Resolution! Lorenz Martin, 4 Feb 2020! Get number of system wavelengthsnum_wav = SYPR(201)! Define wavelength rangemin_wav = WAVL(1)max_wav = WAVL(num_wav)delta_wav = 0.01num_wav_steps = INTE((max_wav - min_wav)/delta_wav) + 1! Define variablesDECLARE wavelengths, double, 1, num_wav_steps + 1DECLARE y_positions, double, 1, num_wav_steps + 1DECLARE wavelengths_for_d, double, 1, num_wav_stepsDECLARE d_wavelengths, double, 1, num_wav_stepsDECLARE d_y_positions, double, 1, num_wav_stepsDECLARE resolution, double, 1, num_wav_steps! Set MC operand to change Wavelength 1SETMCOPERAND 1, 0, "WAVE", 0! Loop to go through wavelength range and find position of beam on detector with respect to central wavelengthFOR i, 0, num_wav_steps, 1 wavelength = min

Hello everyone, What would be an elegant way of computing the path length (for every ray) from a direct unpolarized (sequential) batch ray trace in the ZOS API (since I don’t think it is returned by this tool, but correct me if I’m wrong)?I was thinking of going surface by surface, each time finding the intercepts in X and Y, and computing the path length based on the Thickness between the two corresponding surfaces, but this requires a ray trace for each surface, and before I go in this direction I wanted to hear from other people’s experience.Thanks for your help, and take care, David

I am totally new to OpticStudio, and I am trying to follow the PPG example to get started. However I am encountering this error when try to run the script:Traceback (most recent call last):  File ".\PPGsimulation.py", line 230, in <module>    volPhysData.ModelSettings._S_DLLDefinedScattering.MeanPath = meanPathAttributeError: 'NoneType' object has no attribute 'MeanPath'I am experienced in Python, but don’t know the inside of the API, so it’s difficult for me to debug. I would appreciate if you can give me a pointer.OpticStudio Pro Ver 22.2Python 3.8 (Conda environment)Windows 10 (virtual machine, fresh install)

Hello everybody,I am Nuclear Physicist and I’m newer of OpticStudio. I’m following the official OpticStudio guide in order to build a Spectometer UV that can work in the range 250-300 nm.A little remark about the project: How i said the source is in the range 250-300 nm and the light passes through the first lens and cuvette and exits through the second lens.Bearing in mind that I have as sensor a 2.8 cm SiPM row with 50 um cells, in order to obtain a resolution of 1 nm, which focal length should I choose for these two lenses in order to obtain an Airy disk on the sensor < 50 um?After this second lens, the light is focused towards a hole so as to inhibit the passage of unwanted light, after the spot the light is collected by another lens and the parallel beam hits a grating.Same question: in order to obtain a resolution of 1 nm, which focal length should I choose for this lense in order to obtain an Airy Disk in the sensor < 50 um? Of course I also want lower aberration.After whi

Hi, I am  trying to calculate multimode fiber coupling efficiency by using Geometric Image Analysis through GETTEXTFILE, and I want to do this for different fields and wavelengths. I am trying to change field# and wavelength# by MODIFYSETTINGS, but looks like these two parameters are not allowed to be changed. Following is the list of parameters that MODIFYSETTINGS provides:  I wonder if anyone knows how to make the changes so I can do this calculation using ZPL. Thanks!Jizuo

Hello,I would like to know how can I create a diffractive lens in a sequential mode using a dll ?  Thank you. 

We can use ZOS API Python to create and run the ZPL Macro Solve. Let’s have an example of ZPL Macro Solve. Applying ZPL Macro Solve in Multi Configuration Editor.  Now we create this Test_config.ZPL from Python program and run in for loop for all 3 configuration.We can use ZPL Command as string in Python Program and write in the text file. Then save the file as ZPL in ZPL Macro folder. If we use forloop then we can create and run multiple ZPL Macro solve. As in Multi-configuration, for each configuration need seperate ZPL Macro Solve file.  Python Code :NumberOfConfigurations = list(range(TheMCE.NumberOfConfigurations))# print(NumberOfConfigurations)ZPLFolder=r"C:\Users\s.rajan\OneDrive - Zemax LLC\Documents\Zemax\Macros"data=[]files=[]fg=[]for i in range(len(NumberOfConfigurations)):    filename="Test_config"+format(i+1)+".ZPL"     fg.append("Test_config"+format(i+1))    file= open(os.path.join(ZPLFolder, filename), 'w')  # Create ZPL file    data.append(str("x_APMN=MCOP(1,")+ format(

For wide angle system, it can be interesting to visualize the position and the size of a real entrance pupil in different field angles. This macro will compute with real ray tracing real entrance pupil information for different field angles. It then adds the entrance pupil as a dummy surface and each “field” entrance pupil is defined into a configuration. The macro assumes axial-symmetric, only y field and the field angle in object is positive. Ray-Aiming should be turned on to correctly run this macro. It may only work with field type Angle and Object Height.How to use:  Just run the macro, and open 3D Layout with showing central field and all configs.  Click here to download Date Version OpticStudio Version Comment 2018-02-26 2.0 - Fixed some issues by calculate the pupil points before adding any config or surface (Michael Cheng) 2018-02-03 1.0 - Creation

A simple question but I am unsure.  Currently I’m using a macro that I have to edit in manually the last surface index every time.  Something like index = -1 but this didn’t work.  Thanks!

In the OpenBatchRayTrace tool, for AddRay it appears Hx, Hy, Px, Py can be arrays.  But when I pass the same arrays to GetDirectFieldCoordinates, it gives an error: No method 'GetDirectFieldCoordinates' with matching signature found for class 'ZemaxUI.ZOSAPI.Tools.BatchRayTraceTool'.  It runs fine if I pass single values to Hx, Hy, Px, Py. Can GetDirectFieldCoordinates take arrays, and if so what’s the format? Thanks

For those who want to work with ZOS-API using Excel, here are a few advice and sample codes. You can either work in standalone or interactive extension.Enable the communication between Excel and ZOS-APIThe communication between Excel and ZOS-API is pretty straightforward once the references are enabled in the VBA environment.  Click the Developer tab from Excel to access the VBA environment (if you don’t see it it has to be enabled in the Options): Once VBA is opened, simply click on Tools > References and then select ZOSAPI and ZOSAPI_Interfaces:Using ZOS-API with Excel: what is different?From here, create a new Module and subroutines.  There are a few caveats and cool things:Declare variable types with the Dim keyword (at the beginning of your Sub) For any method which is not assigned to a variable, treat it like a ZPL keyword where you don’t use the parenthesis to pass in the arguments (see wavelengths & fields in the example) Use the intellisenseInheritance: When a child cla