Got a question?
Can't find the answer you need? Ask your peers!
- 2,319 Topics
- 6,397 Replies
Hello,I am a new user of the OpticStudio software which arouses my curiosity!The wave propagation can be solved with several models and the software offers several possibilities. The model based on the astigmatic Gaussian beams (beamlets) is very well interesting.But, I found few years ago the relevant paper:Gosse L., James F., Convergence results for an inhomogeneous system arising in various high frequency approximations, Numer. Math. 90: 721–753 (2002).It is enough hard because the mathematics formulations are theoretic. However, the issue solving gives several possibilities to find the phase and the amplitude of the light wave together.Numerical values for the phase and the amplitude of the smooth wedge.Therefore, do we have this possibility with the OpticStudio? Compute the phase in order to see transparency images for instance?Thank you in advance for your answer.Benoît.
Hello, I need for my simulation source diode with circular instead of rectangular aperture (without the possibility to model arrays). Thus I would like to know if the DLL code of source diode is available, so that I can manipulate it for my purposes. Thanks and best regards Dirk
Hi everyone, Our lab is using a Zeiss 20X water immersion lens (Item no.: 421452-9800-000) in a custom light-sheet microscope, and I was trying to perform some simulations of the point spread function (PSF).I searched for the patent of this lens, and potentially found something relevant at the German patent office (Application No. 10 2005 051 025.6). In this patent, Table 3 describes a 20X water-immersion objective lens with a 1.0 NA and 2.149 mm working distance. I’m copying this table here for your reference:Surface number Radius Thickness Nd Vd 0 Water immersion 1 -9.039 4.80 1.519 64.0 2 -19.248 4.61 1.597 35.0 3 -9.576 0.40 4 -101.598 5.00 1.440 94.6 5 -14.227 0.10 6 64.011 5.50 1.440 94.6 7 -21.754 0.50 8 58.715 7.00 1.530 76.6 9 -15.181 1.50 1.641 42.2 10 14.227 6.80 1.440 94.6 11 -53.084 0.10 12 14.539 7.10 1.440 94.6 13 -68.788 1.77
Hello, I'm using the following knowledge base article to convert a lens design file (sequential) into it's non-sequential alternative: https://customers.zemax.com/os/resources/learn/knowledgebase/how-to-convert-sequential-surfaces-to-non-sequenti Does it also work on black box models? Thank you in advance!
I suspect the Stock Lens Matching tool does not test the stock lenses twice (both direct and flipped). Can you confirm this? I'm testing on a finite-conjugates system with two cemented doublets and it looks like the best result is not following the symmetry principle. Indeed, when I flip the first doublet I can reach far better results.
Hi Trying to set up a NS system with goal to achieve a uniform flat top rectangular light distribution at a distance. So far only achieve in one direction. Need someone to review my set up and merit function. I could not find a kb article on this subject except the article by Akash Arora “How to optimize NS optical system” which was helpful as a 1st step. Please see attached detailed description and question in ppt and .zar file Thanks.
Hi,Thanks for the (many) postings about the new 31.3 release. However, OS is still reporting that 21.22 is still the current version. When will the new release be available?On the new .ZOS file format, does it have any advantages over the old format? Like faster load times? Does it also replace the ZAR format?Mark
Dear all, I noticed that zemax gives the beam size and divergence at 1/e^2 FW (full width) (13.5% FW) but, I would like to have it at 10%. Does anyone know whether there is a way in zemax to get the beam size and divergence at other FW. My beam is not Gaussian so, I cannot simply convert the 13.5%, the zemax output, to 10% using the intensity distribution. Thanks in advance,Maryam
Hello, I have a very simple nonsequential model: Source Point: power=10 W, coherence length=0, linear polarized: Jx=Jy=1, collimated light: cone angle=0 Detector rectangle: placed behind source, normal incidence, number of pixels=1, polarization=2 for measuring power of y-polarized light Then I have a merit function: NSDD for clearing the detector NSTR for making the rey trace NSDC for measuring nonsquential coherent data I was expecting to get Ey (y-component of the E-field vector), if I take Pix=0, Data=2 as parameters for NSDC. But I got 1,581 as result. From my understanding the result should be Sqrt(10)*cos(45°)=2,236. What's wrong here? If I take Pix=0, Data=3 as parameters for NSDC I get 2,5 as result. Data=3 should calculate the power. Because power is proportional to amplitude of E-Field vector and 1,581^2=2,5 this is consistent. But according to Malus Law I was expecting to get 10W * (cos(45°))^2 = 5W. I would be very happy if someone can help me clarifying this
Dear Zemax team, I am calculating the Diffraction Encircle Energy (DEE) in my multi-configuration file, which has 42 configurations. I want to extract the data of DEE for each configuration, and plot all of them in the same chart. What I did for now are copy, paste, and then plot all the data within an Excel spreadsheet. It cost a lot of time. Below is one figure I did for one wavelength, and I have more wavelengths and more FOVs. I am wondering if anyone could give me any suggestions to make this calculation automaticlly. Thanks ahead!
I’ve just tested the new "Convert to Project Directory" feature with a design file using scripted tolerancing.I noticed the browsing dialog box (which appears to let the user select the project folder) does not let you create a new folder by simply inserting a new name. The user is forced to right-clic and create a new folder manually, then select it. the new project directory which is created misses some essential files: .MF , .TOP , .tsc
Hi, I’m getting started writing a video on Wide Angle Lenses for my YouTube Channel DesignOpticsFast. I have a couple of questions:For Zemax Support:I’m having trouble getting the ‘enhanced wide angle ray aiming’ to make any difference: What does it do? I’ve toggled all the (new) switches under Ray Aiming in System Explorer and I’ve not been able to see any changes at all, let alone improvements. Can you guys explain where and when this Feature Experiment is intended to be useful? Or offer some sample files that show what it can do?Also, I wanted to check that the Performance Test measures raytracing speed AFTER the ray-aiming, so it won’t be a useful guide to how well or badly the ray-aiming is going. Is that correct?For Zemax Community:I’m interested in problems that you have in designing wide angle lenses. I’m trying to write a How-To that gives a step-by-step guide to setting up a wide angle lens. One problem I have is that it works with 100% of the files I create, so I wonder if I
Bonjour à tous, J'espère que vous allez bien et que le projet avance. C'était un plaisir d'enseigner ce cours pour moi! Utilisons ce forum pour continuer à communiquer. Je conseil de vous inscrire à cette discussion pour en recevoir les notifications. Berenice&Manon Lampe frontale chirurgical How to create apertures in Non-Sequential Mode · MyZemax,Surgical lighting - Wikipedia Ageeth Lampe de bloc opératoire Surgical lighting - Wikipedia Benoit&Hubert Lampe de pupitre Chaimae Eclairage extérieur d'architecture Documents envoyés Emma Eclairage tableaux musée What scattering models are available in OpticStudio? · MyZemax,How to use multiple ABg profiles to define an object's surface scatter property · MyZemax Guillaume Guide d'onde rétroéclairage How to
Hi Zemax Team, I was pleased to see the new optimization routines in 21.1, but I have not yet succeeded in getting a better result (either in MF value or speed) with them than with the DLS optimizer. For example, in a typical imaging system design, optimizing for best RMS spot, I have a design with a starting MF of 0.02 with 12 variables, all thicknesses and radii. The results I get are: DLS: 0.0011 in 1.7 secs DLSx 0.0035 in 3.6 secs PSD 0.0035 in 3.6 secs For reference, Orthogonal Descent (which I know is not intended for this kind of optimization) gave 0.0037 in 2.9 secs. Can you give us some color on what kind of optimization problems these new algorithms are intended for? - Mark
For modelling laser diodes via 'source diode' the value of astigmatism matters. Data sheet of laser diodes typically don't show this value. I tried to derive this value from far field beam divergence in the slow axis plane. Slow-axis divergence @1/e2 points is typically slightly bigger than the FWHM value. Using far field divergence equation one derives the beam waist and using the beam diameter-as-a-function-of-distance 'z' equation one can back calculate the 'z' necessary to get the beam diameter equal to the emitting chip length (not cavity length) e.g. 50µm.. I am not sure if this is correct. Any other suggestion/experience would be welcome. I was also never sure if the source diode inputs 'X-divergence' and 'Y-divergence' (in fact 0.85 x FWHM values) refer to full angle or half-angle. Thanks, Dusan
What does this announcement on the front page of www.zemax.com mean for this community forum and knowledgebase?I hope the forum will stay open, but in the case it gets shut down, will there be an equivalent forum on the Ansys website? Will legacy Zemax users have access without a license for an Ansys product?
Hello,I am mostly running Zemax OS on my laptop, based on Intel i7 4 x 2.9Ghz 16GB RAM (Win 10 Enterprise, 64-Bit), to speed up simulations, I recently started using workstation with AMD Ryzen Threadripper 3970X 32-core 3.7Ghz 128GB RAM (Win 10 Enterprise, 64-Bit). Pure NSC raytracing is about 8 times faster on the workstation then on my laptop. However, on the same NSC optimization tasks I am getting longer optimization times on the workstation. For example, comparing with the results from the KA-01591 How to optimize non-sequential optical systems Intel Quad Core CPU (2.90 GHz) and 16GB of RAM (as stated in KB Article)Algorithm MF Value On-axis brightness (Cd) Time for optimizationDLS 6.69 238 4.4 minOD 6.68 254 6.5 min My laptop i7 4 x 2.9Ghz 16G
HiI try to make a BTDF data file to simulate a VDI roughness from air to glass or glass to air, but I don’t understand what is the reference for radial direction, it is indicated by the “angle of direct transmission” in article https://support.zemax.com/hc/en-us/articles/1500005486801-BSDF-Data-Interchange-file-format-specificationDo I have to take into account the refraction for this angle, which seem logical, or not ?Is it possible do use BTDF scattering between two media with a difference on refractive indexes?Marc
I'd like to point out some mandatory features which, in my humble opinion, the ISO Element drawing utility lacks. I'm probably referring to all well known issues, but still, I believe them to be of paramount relevance to be left unsolved over the years. 1) support for triplets. 2) xml file support for doublets/triplets. More on this, I report a sneaky behaviour of the current feature: if a doublet design is saved, no error is reported by OpticStudio and an empty xml file is saved instead, so that the average user can believe its manually inserted data are securely saved, but actually they are not. When opened, such xml file just reports the string 'XML output is not currently supported for doublets'. 3) drawings saving in a native vector format, such as pdf or svg. At the present time an external pdf printer sw is needed to do so, often with unpredictable results. The same request holds for every graphic output of OpticStudio (diagrams, histograms, plots,...). The cha
I’d like to save my OpticStudio files as .zmx by default to preserve compatibility with older versions of OpticStudio that my colleagues may be running. Manually saving .zos files as .zmx is functional but tedious - will the feature to change default save type ever be added? Thanks!
Hello I frequently use standard lenses in NSC modeling such as for imaging a light source onto a detector, fiber etc. Prior to optimizing them the lenses would be roughly 'created' in situ i.e. in the NSC Lens Editor. As an old school optical designer I need a feeling for magnification of the optical system I am setting up. It would help in determining the magnification if I knew the individual (paraxial) EFLs of the lenses in my setup. Any quick way? Thank you, Dusan
I am currently modeling light scattering inside of the human skin. The known mean path for human skin is 0.1 mm. In the knowledge base articlehttps://support.zemax.com/hc/en-us/articles/1500005577062-Using-the-Henyey-Greenstein-distribution-to-model-bulk-scattering I found that The Mean Path (mean free path) was set to 0.0001 mm, which is small relative to the 0.1 mm thickness of the volume. The measured OpticStudio values reproduce those results derived from the theoretical model within statistical error, as we would expect for a case in which each ray is only allowed to scatter once (the results will vary from ray trace to ray trace due to statistics, so you will get different – but very similar – numbers). I am a bit confused what mean path should I use in my model (there is very big difference in the results when using 0.1 mm and 0.0001 mm. May I get more detailed explanation how the reduction of the mean path compensates the single ray scattering approximation. I use the thickn
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.