Hi everybody, I would like to write a macro in which I determine the 100 largest and smallest pixel values on a detector. Only pixels in a certain region of interest should be considered. I have already successfully implemented the criterion of whether a pixel is within the ROI. I also have a solution in mind for determining the 100 largest and smallest values, which I think should already work. When I run the macro, the array with the values also fills up at first, but at some point it stops and no new values are added.Do you guys have an idea why this is not working? Could there be some kind of buffer overflow or so? Or do I have a fundamental error in my macro? I added my macro and an exemplary result below Thanks for any help or hint :) Best, Matteo ! Calculates the max and min intensity (from the 100 largest and lowest pixels) in a circle centered in the detector plane! Calculates the uniformity = min/max from the in that circle detector = 28size = 51max_radius = 25center = 26tota

I see that Ansys is going to do away with this zemax.com site. Has anyone figured out how to effectively get information on the new Ansys site? As an example, I tried today on the simple topic of “fluorescent microscope” and I can’t find the article (which exists in the zemax.com ) It appears all Lumerical and Speos articles are mixed in with Zemax, not that I can tell for certain. Any hints would be appreciated. Thanks for your time. John

I have a model for which the image simulation outputs an overall greenish/blueish image when polarization is used, while I could not find any reason for why the red component would have lower power. Here is the image with no aberration and no polariztion (with wavelength 1+2+3): And here is the result when polariztaion is enabled (still no aberration) : On the other hand, I could not find any anyslis that shows a wavelength dependency ; relative illumination is the same for all wavelength, across all field transmission vs wavlength is the same for all surfaces Is there a way to investigate further the wavelength dependency of the image simulation/polariztion of the design ?

I have a zemax file that seems to do no change in the lens data when I try to use the Quick Adjust tool. I set the tool to the right surface number and use thickness to optimize the Spot Size Radial at the image plane, but it does not modify the surface’s thickness, even though it is not at an optimal value (I handedly modified it to be a bit off) I’m guessing something is limiting the computation, but I get no error or no message, the system just stays the same Note that using the Quick Focus does change the second-to-last surface thickness. Also note that the surface I’m trying to tune the thickness through the Quick Adjust tool is the “back” of a black box model.

Hi, I am trying to optimize a simple lens that focuses and couples a Gaussian beam into two different fibers. I want to optimize a lens that will yield the best combined coupling efficiency for both fibers. Just to clarify, the beam will be coupled into one fiber at a time, but the same lens will be used to couple a Gaussian beam into both fibers. The fibers are represented by .zbf files which are loaded in the Fiber Data tab in Physical Optics. Right now, I’ve written two ZPL macros that will each open a different .zbf, and they are called in the MFE using two separate ZPLM operands. Each ZPLM operand is immediately followed by a POPD operand to get the coupling efficiency which is then optimized, as shown below. I am not sure if this works as intended. When optimizing, are the operands in the MFE cycled in a loop, so to speak? Also is there a more elegant way of doing this, other than using ZOS-API, or should I use ZOS? Thank you, Sam

The documentation about Image Simulation on the “Apply fixed apertures” is : Apply Fixed Apertures If checked, all surfaces with optical power that have no aperture defined are modified for this computation to have a circular aperture at the current clear semi-diameter or semi-diameter value. Without this change in the aperture definition, rays may pass the surface beyond the listed clear semi-diameter or semi-diameter, especially if the Field Height exceeds the field of view defined by the field points. This leads to misleading illumination, typically at the edges of the image. I’m kinda confused by the vocabulary here, probably just by lack of knowledge on my side. In the first sentence, “… have no aperture defined...” refers to the surface’s Aperture data ? so that means “for surfaces whose Aperture data is None for Pickup From and Aperture Type” ? - like so : Then, “to have a circular aperture at the current clear semi-diameter” : from what I understnd, with “Clear Semi-Diameter” s

Hi, I’m currently trying to trace a large amount (~1 million) of rays with very specific output position and trace their path length it takes them to reach a detector and then output the position as well as the specific path length of that beam. Currently not using scattering, but in future, I would like to extend this to scattering as well. My first thought was to create a loop that would create single rays, trace them, return the OPL through a Merit Function and then output in the end, but I assume that this would take forever to compute. Any idea how this would be done more efficiently? I’ve seen that batch ray trace might be an option, but I don’t know enough about it or other alternatives to evaluate correctly. Thank you for any help!

I don’t understand how I should set the Filter and RayDatabaseFile of the DetectorViewer in non-sequential mode. SHould I use : DetectorView = zos.system.Analyses.New_DetectorViewer() or : DetectorView = zos.system.Analyses.New_Analysis(zos.ZOSAPI.Analysis.AnalysisIDM.DetectorViewer) Then should I use : settings = DetectorView.GetSettings() and/or ? settings = zos.ZOSAPI.Analysis.Settings.RayTracing.IAS_DetectorViewer(settings) Then using : settings.RayDatabaseFilename = db_file settings.Filter = "h9" Those seems to make the analysis fail

EDIT TITLE: How to setup boundary constraints for custom Compensator Surface in LDE/MFE. Hello: I am having trouble understand how to constraint a compensator surface. Setup: I am using Surface7 as a compensator as shown below defined by MNCA, MXCA, PMGT and PMLT operands to control the boundary limits of this compensator surface variables (thickness, Decenters X&Y, Tilts in XYZ). For test: I apply a DecenterX of -0.002mm on Surface3. When I execute optimization; I notice that the Optimizer can change the Compensator thickness value to go beyond the set boundary limits. Why does this occur? How can I strictly limit the Optimizer to limit itself within the boundary limits I specify? Thanks - Asuku

I want to overlay a pair of greyscale Huygens PSFs from the same source field, but two different wavelengths. It’s a spectometer, so the image locations are different. SOLVED! the Huygens PSF plots are showing the different wavelengths at the correct locations. Not sure why it didn’t seem to be working last night.

I want to create a universal plot of Huygens PSF FWHM vs wavelength or field. Is there an operand that would make this possible or do I need to write a script to (or manually) extract the FWHM from the Huygens plot data? This is for a spectrometer. I’d also like to get the local dispersion around a number of central wavelengths. If you can think of any built-in tools or shortcuts for doing this, please let me know. Thanks!

I used global optimization on a 2-lens imaging system with each lens having dual even asphere surface. The merit function improved a lot but now the diffraction MTF seems too good compared to how the rays look focusing in the 3D layout and how they look in the spot diagram. The only thing I can think is that since I have rather steep slopes to my lenses (due some high conic constants and one surface have high r^8 coefficient) that maybe there is some sampling issue. I did increase the ray density for the spot diagram and it does improve, but I am still concerned about the accuracy of the results I am getting. Any advice would be helpful -- Dan

I’m trying to export CAD for someone who can’t read STEP 242, but can read STEP 214. Is there a way to do this in Zemax? Thanks!

Hi Everyone, I would like to ask for help with an assignment that addresses the topics of polarization and absorption? I will try to introduce you to the problem at the beginning. Unpolarized light at a small angle of incidence reaches the front surface of the cell (a 1mm window of MgF2), and then passes through a cell filled with absorption gas. During propagation, the gas absorbs 99% of the P-polarized light and transmits 100% of the S-polarized light. At the end of the cell is another MgF2 window through which the beam passes. The axis of the crystal is parallel to the optical axis. I expect that because of this residual p-polarized light, the total polarization state will change (probably not much) but I would like to quantify the final polarization state. I don't quite know how to model in Zemax the absorption coefficients k as a function of wavelength for different polarization components and in turn determine the final polarization state. I tried to use the Birefringece In/Out s

Hi all, I am trying to make an illumination system where the input are plane waves (-10,10 fields, right in the figure-laser with fixed beam size of 1 mm), and the output are divergent cones of -10 to 10 degree (small in the figure), something like that: Should I start from obejct space by using angles from -10 to 10 and force the image to have divergent cone of -10,10? If so what operands can I use? Working the otherway around by forcing the objects to have diverging cone (object cone angle )of -10,10 degree? Maybe working in non sequential mode? What operands to use? Many thanks, Nadav

Hello Using Interference Example 1- A Simple Interferometer from SAMPLES folder I created a simple setup to test a right-angle prism with pyramidal error. At the end I wanted to save the file but OS just froze and didn’t react any more - even after a longer time. I ended the program in Task Manager and opened it again without problem. The file to-be-saved before seemed to have saved well and it was possible to continue the work. I tried to save again and OS froze again. And so many times… In my last trial I wanted to check Preferences and after some time in Preferences OS froze again. All other sequential and non-sequential files that I have behave normally. What could be the reason. Attached is the screenshot of the file. Thanks, Dusan

In reference to this KB article, “Single-Mode Fiber Coupling in OpticStudio”. The receiving fiber is a Single-Mode. A SM fiber has fiber-core size = φ9.0 micron. Therefore, I added a φ9 micron aperture at the Image plane. This resulted in a drastic drop in Coupling Efficiency: 0.99% to 0.72%. Why is that? In a Laser fiber-coupling applications, doesn't the laser beam have to couple into the φ9.0μm dia. core? Or is it truly not the case, and the beams are much larger than the fiber core? Please help understand the reason behind this. Thanks -Asuku

This looks like a bug in ZOS API : when calling FindMaterialCatalog on a row of a non-sequential model with ABSORB as mateial, it returns the first catalog in the available catalog listI would except this call to return None or “”

I’m new to tolerancing in Zemax. Does anyone know of resources on how to tolerance irregularity on cylindrical/acylindrical lenses used as diode laser slow axis collimators (SAC)? What are some good merit figures to use for a cylinder? Is it typical to tolerance the power and nonpower axes separately? Thanks!

In non-sequential mode, I am trying to automate the process of reviewing any input data that is spectral. The idea is to review how all models (in the wide sense) behave wrt wavelength in a quick way to make sure there’s nothing shady happening, using the ZOS API. For now I’m trying to review : - all coatings used, and their spectral response wrt incidence angle and wavelength - all materials used and their refractive index and extinction response wrt wavelength because given the complexity of a NSC model, the complexity of coatings definitions/catalogs, material definition/catalogs, a mistake can happen quickly. For now the idea is to review those spectral model dependencies only in a “passive” manner, using the NCE - without running a raytrace specifiicaly. If anyone has ideas or guideline on this process, feel free to comment ! :)

Hello all: Is it possible to create a UDA on Image Plane such as shown below? I am looking at an array of beams falling on the Image Plane, where each beam is to be coupled back into a given SM fiber. Basically I want to model the image plane as an array of SM fibers. Problem: When I do a optimization on the rest of the system, the beam array can fall anywhere on the Image plane. Therefore, I would like it to restrict the array of beams falling on the Image plane with apertures as illustrated below. Any ideas on how to do this is appreciated. Cheers - Asuku

Hi all, I am trying to use ZOS API to assign the diffraction-based dll for the User Defined Object in Non-sequential mode. I have tried normal ‘Diffraction Grating’ object and it works good, however, for the User Defined Object, it did not work. Could anybody share some insights for me? Thank you! Part of the code for normal ‘Diffraction Grating’ object: (This works!) TheNCE.InsertNewObjectAt(1); o1 = TheNCE.GetObjectAt(1); o1.ChangeType(o1.GetObjectTypeSettings(ZOSAPI.Editors.NCE.ObjectType.DiffractionGrating)); o1.DiffractionData.Split=ZOSAPI.Editors.NCE.DiffractionSplitType.SplitByDLL; o1.DiffractionData.DLL='srg_trapezoid_RCWA.DLL'; o1.DiffractionData.StartOrder=-1; o1.DiffractionData.StopOrder=1; Part of the code for ‘User Defined Object’: (This does not work!) TheNCE.InsertNewObjectAt(1); o1 = TheNCE.GetObjectAt(1); o1.ChangeType(o1.GetObjectTypeSettings(ZOSAPI.Editors.NCE.ObjectType.UserDefinedObject)); o1.Comment = 'DiffractionGrating.DLL'; o1.DiffractionData.Split=ZOSAPI.Edito

Hello all: I am modeling a system where the object is pivoted about Point A - lens surface-2 center. I would like to calculate the position the OBJECT such that the refracted light is normal incident at the center of surface-2 that (Point-A). How to calculate the Object Y-Decenter and Tilt-Y required to bring the Chief Ray position from B → A? Zemax setup (Thanks to ​@Jeff.Wilde for his help on how to model launch ray from angled facet fiber). Here in order to demonstrate the effect of refraction, I’ve used a high n_d value. Thanks - Asuku

I would like to study the tolerance of my optical system. I want to evaluate the RMS Sport and the RMS wavefront error at the same time in the same tolerance simulation. However, we can choose only one of the two criteria during a tolerance run. Do you know if it's possible to evaluate both criteria at the same time, and if so, how? Thank you very much.

Following, Feature Request: ZOS-API Layouts Exports Completion | Zemax Community, I’d also advocate for making the 3 cutting plane tools from the NSC Shaded model available in ZOS API. Those cutting tools are quite efficient in visualisation, and sometimes even absolutely necessary. Now that we can export the shaded model to png easily, it’d be great to be able to enable/disable those cutting planes as well. In the same manner, having access to the Camera View would be nice: