This macro applies incremental changes to a compensator in Monte Carlo files, then reports the updated criterion. It will cycle through Monte Carlo files and apply a discretely-valued compensator to a particular surface. Then, the criterion will be analyzed and reported. (Note, the report could use some formatting updates). This code may be used to represent step-wise compensation tools. For example, a mirror's tilt may be applied as a compensator to a change in the system. However, it may be the case that the mirror's housing makes it so that the mirror is only allowed to tilt in increments of 2 degrees. This macro will cycle through the MC files, apply the incremented compensation up to a particular boundary, and will report the result. The changes to each file are NOT saved.Language: ZPL 

How i can  connect to microsoft excel with zemax?

I'm having trouble to read detector pixels using a ZPL. The syntax should be NSCDetectorData,surface,object,pixel,data However, I get error message and do not know how to solve. Can somebody provide me with a example of a piece of ZPL code to get the job done. Ideally reading the detector into a 2D array But I'm already happy with a single statement reading out say the 6th pixel iof the 5th row Hope somebody can help me Pascal 

Hello, we're currently working on parallelizing a raytracing program in Python that uses the ZOS-API for a connection to Zemax. We didn't write the code, we're tasked with bugfixing and optimisation, so we don't fully understand the code. The problem we identified is that the code needs to do a 2nd Trace. By default, the OPD gets normed to a centroid of some sort, because of this we need to retrace every ray to get rid of this norm as the purpose of the code is to simulate interferometry, which is why we need the OPD values unnormed. Is there any way to stop Zemax from norming these values (perhap some get merit function?)? A different approach might be do incorporate Python multiprocessing, whoever we are unsure how to incorporate the bellow OPD function into Python multiprocessing. Below is the snippet of the code that creates the major slowdown, the OpdItr=... part takes up approx. 80%+ of the Runtime (which is bad, total code ru

Hi, I made a ZPL macro that uses GETPSF to retrieve a PSF to a vector and then saves the vector to a file with a FOR loop on the vector elements. The saving part is extremely low! Is there a better way to save the results? I tried doing the same thing with GETTEXTFILE but the speed is similar, and I lose control on file format and can't seem to find a file to set the parameters such as sampling size. Any help really appreciated! Thanks, Paolo

I tried to change surface setting in spot diagram by ZOSAPI MATLAB and get spot position info by the following commands in MATLAB:  spot.ApplyAndWaitForCompletion();  spot_results = spot.GetResults();   spot_results.SpotData.GetReferenceCoordinate_X_For (2,1) spot_results.SpotData.GetReferenceCoordinate_Y_For (2,1) Which command should I use to fulfil this task??   

Hi, I am writing a macro to modify some surface properties and I can't figure out how to define a pickup... Here is what I am trying to do: SRFn (actually a coordinate break) : I use SETVAR to set the parameter #1 to variable SRFn+3 (I want to make it a coordinate break return): I would like to set parameter #1 of this srf by pickup the one of SRFn but I can't find the right ZPL keyword to do that.   Any help is welcome.

Currently I use a Macro in optic studio where I read through a Ray Database Viewer window, where I tick 'Expand Into Branches'. I want now to achieve the same funtionality using the ZOS-API with Python. I started by looking at example 5 'PythonStandalone_05_Read_ZRD_File.py' where we loop over the segments of each ray. How can I instead turn on  'Expand Into Branches'  and easily loop over each branch per ray individually?

Hi,  Something strange has happened. I had previously a code that worked and now it doesn't (I have updated ZEMAX since then).  The code I am having issues with, is changing an angle to 'Ray Rotator' in Par 3 or Par 4 (column 3 or 4 from Material on the editor list), which in this case is the angle of the rotationZ and rotationY. The problem is that I am getting error message:  Unable to use a value of type ZOSAPI.Editors.NCE.ObjectColumn as an index. Error in GetAngle_Cond3_v2>writeTiltAboutY (line 142)         NCEObj.GetObjectCell(ZOSAPI.Editors.NCE.ObjectColumn.Par4).DoubleValue = y; Error in GetAngle_Cond3_v2>BeginApplication (line 70)         writeTiltAboutY(o23, angleY); Error in GetAngle_Cond3_v2 (line 14)     &n

Hi all!  I have done user defined dll surface and want to check its accuracy. For this, I did a lens with such surface on one side and plane on the other in SolidWorks and opened it like .STEP file as a non-sequential component. In the second Zemax file, I opened my user-defined dll. All dimensions, apertures the same. Also, I can see that rays go through the lens in almost the same way. Spot diagrams look very similar. But I want to compare the wavefront map and here I have a huge difference also ray fan very different and I cant understand the reason. It's my first time with non-sequential mode, maybe someone can help me with good advice? Thank you a lot 

Hi  I have a question about the Henyey Greenstein model in Zemax. I am now using the Henyey-Greenstein (HG) model in combination with the wavelength shift to simulate the Raman scattering. Because the mean free path is wavelength-dependent in the same tissue, my question is that, in the multiple scattering, if the input photon is altered in wavelength, will its mean free path be changed too in the next scattering event? From the HG source code, it seems like the mean free path is a constant to all wavelengths. Furthermore, I also found from your HG source code that you didn't really consider the light absorption while in scattering events, right? Thanks in advance!  

Hello, I have sequential rays that  enter a non-sequential component. In this element there are two sets of dffraction gratings helps rays to couple into the the medium and extract from the medium for analysis. However, the rays I sent only diffract  along the set primary diffraction order. Can Optistudio simultaneously trace multiple diffraction orders NS components?  Thanks,  

If I have several versions of ZOS installed on PC how can I specify in ZOS-API tool (Python) what version should be used?

I am looking for a way to annotate analysis windows programmatically with the ZPL script language. I would like to change the title but failing that just add some text to the window. Is there some way to do this?

Need to convert from codeV to Zemax. Can you please provide the latest CodeV to opticsStudioConverter.ZPL macro. The current file is working properly. Following error 0098    SCC C6 0 No mapping for command SCC 0098    Nothing to convert   ! Version: 2.06.4 ! August 28, 2019 ! NOTE: This Macro constructs Zemax OS Optical system using Code V seq file   1333    PIK   SCO S14 Z2 C8 SCO S14 Z1 C8 1.00162632102796 No mapping for command PIK 1333    Nothing to convert 1334    PIK   SCO S14 Z2 C9 SCO S14 Z1 C9 1.00162632102796 No mapping for command PIK 1334    Nothing to convert 1335    PIK   SCO S14 Z2 C10 SCO S14 Z1 C10 1.00162632102796 No mapping for command PIK 1335    Nothing to convert 1336    PIK   SCO S14 Z2 C11 SCO S14 Z1 C11 1.00162632102796

Add buttons to Tolerance Data Editor and Multi-Configuration Editor to delete all rows. This exists for Merit Function Editor.  Likewise, add the ALL option to the keywords DELETEMCO and DELETETOL similar to DELETEMFO.

How I can add spectral sensetivity to detector in NSC mode?  Can I make DLL detector with this feature?

Is there is a way to build an image simulator in Matlab from zemax ?  

Hi This Shayne from Clouldight, Vincent's colleague. I would like to know how to use operand of ZPL 'SPRO' . Is it same as SETSURFACEPROPERTY, SURP? Thanks! Sincerely, Shayne

We had an idea to optimize shapes parameterized by low-degree polynomials (or other shapes: ellipsoids, etc.). We want to maximize irradiance across a complex mesh detector (STL) by modifying another complex, not-radially-symmetric, surface. From what I saw, the TrueFreeForm object isn't supported in non-sequential mode, and the Freeform-Z object limits the shape to a cylinder-like shape that varies in diameter. Can we accomplish our goal using built-in OpticStudio stuff that I haven't seen yet? Or will we need to write our own stuff that generates meshes and runs the optimization? We have the means I think, I just didn't want to jump in if you had already solved this problem :)

Hi,  I try to write a ZOS-API pyhton script that for a parameter change computed the POPD coupling integral. I looked in the API of ZOSAPI.Analysis.PhysicalOptics.IAS_PhysicalOpticsPropagation and could find a function that does it. I tried also to retrieve it via the merit function using the POPD operand value(when Data is set to zero). I found the founction that does that, but each time I change the parameter I need to update the merit function. I tried the ZOSAPI.Editors.MFE.IMeritFunctionEditor.CalculateMeritFunction() command but then I get 'TypeError: not enough arguments' error message. In the API no input arguments are described.    I would appericate if someone can advise me about a proper way to get the POPD fiber coupling value   Thanks, Leonid

I am attempting to write a User defined operand that calculates reflections off of optical elements. I have been told by someone else very knowledgeable in these sorts of things that the GPIM operand does something similar, in that it “hacks” a double pass calculation in OpticStudio without actually requiring the user to have a double pass system set up. I would like to be able to do the same thing in my user defined operand, but am unsure how to do it like GPIM does it. Would it be possible for somebody to shed some light on how to “hack” a double pass computation like GPIM, and if it is even possible to do through the zos-api syntax? Thanks!

Hello, I need to create a new surface lens array DLL. Lens parameter changes through array according to some formula (In Zemax  DLL all lenses are identical). Looking for someone who has experience with developing new surface DLL and interested to develop it. Please apply to my personal mail directly.  

I am trying to set the Index Data via the ZOS-API in Python (in standalone mode-I am using the boilerplate code of the PythonStandaloneApplication() class). I want to define a GRIN DLL model, specifically the grin1.DLL. I've written    stack = TheSystem.NCE.GetObjectAt(1) IndexData = stack.IndexData.ModelSettings._S_GRIN IndexData.DLL = 'grin1.DLL'   But IndexData returns a NoneType object. I had used similar syntax for the VolumePhysicsData data in the past and it had worked. Actually, up until stack.IndexData.ModelSettings it seems to return what it's supposed to. The _S_GRIN seems to be problematic. Can anyone suggest why this is happening? Thank you   Edit: I've tried the VolumePhysicsData just for the fun of it. And again up until ModelSettings it returns sth, but then it becames None  

Why did Malwarebytes flag and quarantine RIHWSTY31.DLL as malware?  See attached screensnap.  Is it a valid DLL or did malware somehow get attached to OpticStudio?  Need to know whether to keep in quarantine or release it. Thanks, Mike