I would like to write the Macro script of ZPL about how to optimize the POP by merit function like as “POPD” optimized operand1.Set the one surface of Thickness or parameter 1,2,3… as the value of  0.5mm, 0.6mm , 0.7mm to run a loop2.Set the someone surface “Thickness or parameter 1,2,3…..” as variable factor. 3.Execute to optimize the MF as POPD to run 10,15 circles as you want 4.In the end, shows the final optimized value to 1st step different cases you setEx. Surface 3 thickness as 0.5mm, 0.6mm, 0.7mmOptimized the surface 7 of thickness as variable factor by using POPD MFto get value under surface 3 as 0.5mm, 0.6mm, 0.7mm respectively.  

I am looking for ZPL command which change NSQ parameter solve from pickup to fixed(off).There is command SOLVETYPE and code PF_p to remove pickup for sequential but this option not available for NSQ parameter pick up. Any suggestion how to do so?

I am simulating light propagation through an optical stack and analyzing the path of individual rays.Using the IBatchRayTrace interface is the only way I found to achieve reasonable performance, however when using IRayTraceNSCData, the NSCRayTraceOptions (e.g. in the AddRay function) are limited to either “UseSplitting” or “UseScattering” as enumerated objects. Ordinary NSC raytracing allows for both options to be toggled individually via booleans, however as I need to simulate a large number of rays with individually set properties, this quickly becomes infeasible performance-wise.Is there any way to activate both “UseSplitting” and “UseScattering” when using IBatchRayTrace?I would be grateful for any help/ideas/insight!

I want to use macro do automatic tolerance analysis, could i modify the tolerance script code in macro code. how to do it if could. thanks!

This user-defined surface can be used to model a tilted gradient 2 surface like a cleaved multi-mode fiber. Compared to the gradient 2 surface, this surface contains 2 additional parameters for the tilt.   Click here to download Date Version OpticStudio Version Comment 2021/12/09 1.0 - Creation

Hi all,I’m facing a problem of applying ‘Chief ray solve’ for multiple configurations inside the multi-configuration editor. I was trying to use ‘Chief ray solve’ for Decenter and Tilt to one configuration and let other configurations ‘pick up’ the value of the first one. However, the ‘Chief ray solve’ for Decenter and Tilt in multi-configuration is grayed out. So I was wondering whether it is possible to create a ZPLM solve that is identical to the ‘Chief ray solve’ used in the lens data editor and applies it into the multi-configruaton editor? If this is possible, can anyone shares the logic behind the implementation of  ‘Chief ray solve’ for decenter and tilt? ThanksBest wishes and Happy new year! Daoming

Question1: I use ZPLM+MACRO to calculation edge spread size, and tolerance script to get tolerance result for edge spread size variation. But CPU only use 10%, so the computation time is very long. Even I choose the max core in tolerance analysis. Is there any setting I miss for macro operation to make better use of CPU? Question2: When I open Zemax file, it become very slow and need to waiting a long time to see it full open already. Why this issue happen? It was open fast before, and I use the same Zemax file on same computer.

This Zemax User Analysis plots the transmission vs wavelength of different configurations and field points of an optical system. The transmission is calculated by sampling a grid of pupil points and then averaging their transmission. The settings may be saved in a configuration file by using the 'Save' button. This analysis comes with the software. The source code can be found under Download.Author: Alastair Humphrey    Click here to download Date Version OpticStudio Version Comment 2020/01/01 1.0 - Creation  

Hi, I found options to enable/disable GPU calculations in the ZOSAPI help (bool ZOSAPI.Preferences.IPreferencesGeneral.GetIsGPUEnabled() ), but I can’t find them in Project Preferences → General in OpticStudio nor in my standalone application.When I run a batch ray trace, I can see that the computation are done using the GPU.Thanks 

I had earlier posted a question as a follow up to Syntax help. Reposting here for the benefit of others and to go further with the topic. What I’m actually after is how to tilt an object in the Non-sequential Lens Data Editor, from Matlab. The Matlab connection is working (using the NSE Ray Trace example).Thanks,Josh David Nguyen has replied:Hi Josh, Assuming the Interactive Extension works for you, you’ll need those lines of code:TheObject = TheSystem.NCE.GetObjectAt(1)TheObject.TiltAboutX = 15The property TilteAboutX is read and write so you can access it directly. The same property exists for Y, and Z. GetObjectAt() will return the corresponding object from the NSC editor (it starts at 1).Let me know if that works for you.Take care,David Thanks David,It does seem like it’s working, thanks!Playing around with it more, it seems that Matlab just requests OpticStudio to open a file, do the manipulation, run a ray trace, return the values and does not interact with whatever may have been

I need to simulate a gaussian beam in non sequential mode, which has 850 nm wavelength, 15 degree diveregence angle (half angle) and the beam raduis of 2.563 mm at 10 mm which has the cross section of the beam profile shape as attached below, but when putting this values using the Gaussian source it doesnt give me the same results. By using the skewRaysCircular I cannot get the gaussain beam profile and it just shows me a ring, how can I get a gaussian beam profile in the output?

I was pleased to see the new NSC Source DLL 'SkewRaysCircular.dll' added in the May 19 release (OpticStudio 20.2).  We have immediate use for it in modeling our systems. It was inspired by the similar (sequential) User Defined Surface DLLs discussed in Paul Colbourne's webinar and KnowledgeBase Article KA-01772, which allows optimization of generally astigmatic Gaussian beams in Sequential mode. But I was disappointed to see that the new Non-Sequential Source DLL only models CIRCULAR Gaussian beams with no astigmatism, unlike the Sequential capabilities that were supplied by Dr. Colbourne, which accommodate general astigmatism! I suggest updating and replacing SkewRaysCircular.dll with a new, more general, Source DLL, renamed appropriately, e.g., SkewRaysGaussianXY.dll , that DOES support general astigmatism.  This would seem simple enough to implement starting from the existing SkewRaysCircular.dll:  add new pairs of parameters for WaistX, WaistY, (and/or SIzeX, Siz

Hi!When using a ZPL macro, is there the possibility of using a keyword that function like quickadjust? There is the keyword QUICKFOCUS but it works only on the last surface thickness

Hi,In a ZPL macro one can get the object number that’s calling the macro as solve with SOSO(1), but how do I get which column that’s calling the ZPL macro?I want to use the same macro for solving both the Z and the Y position of an object so I don’t need maintain two separate macros.Regards,Hans

Dear Zemax Community, When I try to use the BatchRayTrace tool from Python in an Interactive Extension, I get a RemotingException, which seem to be related to the use of the AddRay method in the IRayTraceNormUnpolData interface. To reproduce the issue, try making Example 23 into an Interactive Extension (instead of a Standalone Application). Alternatively, this is my code snippet for an Interactive Extension: from System import Enum, Int32, Double # Open the BatchRayTrace tool MyBatchRT = TheSystem.Tools.OpenBatchRayTrace() # Add an unpolarized-raytrace ToImageSurface = 3 MaxRays = 1 MyUnpolRT = MyBatchRT.CreateNormUnpol(MaxRays, ZOSAPI.Tools.RayTrace.RaysType.Real, ToImageSurface) WaveNumber = Int32(0) Hx = Double(0) Hy = Double(0) Px = Double(0) Py = Double(0) MyUnpolRT.AddRay(WaveNumber, Hx, Hy, Px, Py, Enum.Parse(ZOSAPI.Tools.RayTrace.OPDMode, 'None')) # Run the raytrace MyBatchRT.RunAndWaitForCompletion() # Close the BatchRayTrace tool MyBatchRT.Clos

Is it possible to increase the text size of the ZOS-API Syntax File? The text is so small I can hardly read it. I’ve tried to increase the Windows Font Size, look for zoom buttons, anything.. and seem to be stuck with miniature text size.. The font size will increase on everything except the useful text.. I’m an experienced computer use, so this shouldn’t be an issue.. Seems like a silly topic to post in the forums!  

Hello,I have a system with a non-circular aperture and therefore try to calculate its effective f number using the operand EFNO(effective f number). However, I get different results when using the operand EFNO, in comparison to the result given in the relative illumination analysis, despite the same setting is applied on both calculation. (wavelength 3 is 0.555µm, and field 1 corresponds to 0 y field)     As can be seen above, one gives a value of 4.13(EFNO), while the other gives a value of 3.85. I think the latter one should be correct, but the question is why does one get different results here, do these two use different algorithms for calculation? How can I calculate this value in a Zemax macro conveniently if the result provided by EFNO is not trustworthy….  Thanks a lot in advance! 

I am running OpticStudio Professional (19.4) using a black USB key with with support expiring in Decemeber.  When I try to connect using a Matlab ZOS interactive extension it fails the license check.  What can I do about this. I suppose I could run it standalone in debug mode...  Other ideas? Thanks.

Does anyone know the name of the FDTD software which can directly input the ray file for Zemax?

In Non-Sequential mode, is there a way to change the refractive index value of a model glass whithin ZPL? It seems that SETNSCPROPERTY doesn’t allow this, but only to change a glass chosing from the library. Thank youIari

Hi all,I’m trying to use ssag operand to obtain the surface sag in sequential mode. I’m ok with using it in the merit function editor, however, as I have a lot of sampling points, manually inserting ssag function is a real pain. Is there any method to use SSAG in the ZPL Marco where I can write my own loop? Best wishesDaoming

I have an application in which I would really like to have access to the raw spot diagram data, both with and without surface scattering.  This includes the ray spatial coordinates as well as their direction cosine coordinates.  Not sure why it is not available from the analysis window -- seems like a rather basic aspect.  In any event, it would be nice if the datagrids were exposed in the ZOS-API. On a related note, I can certainly trace rays to programmatically create a spot diagram (similar to Example 22), but with IBatchRayTrace, which mimics the old DDE Extensions for sequential batch ray tracing, there is no option to include surface scattering.  So, adding a boolean switch for scattering would also be helpful!

In OpticStudio interface, If the optical system has some error then just after opening we get the error messages in Zemax Error Message Box .As we can see in image below ,SK2 was excluded before user setting .In ZOS-API, there are some methods under the ZOSAPI.IOpticalSystem Interface Reference that allows to zemax error messages: The general workflow is to whatever operation will generate the message you need to call  TheSystem.GetCurrentStatus() .It will show the status of your optical setup .Here sample code for Matlab :import ZOSAPI.*; TheSystem = TheApplication.PrimarySystem;sampleDir = TheApplication.SamplesDir; testFile = System.String.Concat('C:\test\Double Gauss 28 degree field.zmx'); test = char(TheSystem.GetCurrentStatus()) Here’s sample code for Python  : # Insert Code Here# Setup testFile =r"C:\test\Double Gauss 28 degree field.zos"TheSystem.LoadFile(testFile,False)# To get the Error message test = str(TheSystem.GetCurrentStatus())print(test)I create a connection with the

HiI am trying to calculate the RMS slope of a surface with the DSLP operand in a macro.The surface is Zernike Standard Sag (generated from tolerance analysis) and the rms slope of this surface computed in the MF editor is like below I wrote the following to calculate the same value in a macro:>   print OPEV(OCOD("DSLP"),1,1,2,0,0,1)but this is obviously not correct as the output is 3.4456 (I was excpecting 4.913e-5).I can’t find the error, can you? :-)Thank you

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