Use this space to learn more about your software!
RMS Wavefront Error from Monte Carlo doesn't match Wavefront map
Hi all, I think I'm stuck on a problem of interpretation of results, and maybe someone can illuminate me. After performing a tolerance analysis with RMS wavefront, if I open the MC_XXX.zmx file and compare the results at the Wavefront map, the value shown for RMS Wavefront Error does not match the estimated value at the tolerance summary tab. Let's take for example MC_Worst, which in my case is run # 254, which has a value of 6.312 waves: Then, when opening MC_0254.zmx, and going to the Wavefront Map, I get 0.2353 waves, as show in the following screencap: Notice that for the tolerance analysis the TWAV operand is set at 0.6328, and I'm using the same wavelength at the wavefront map. Is there any conversion between the RMS wavefront of the tolerance analysis and the RMS value from the Wavefront Map? Could it be an incorrect setting of the tolerance analysis? I appreciate your comments on this. Thanks, José
Path analysis and bulk scattering with wavelength shift
Hello, I'm using Zemax OpticStudio 18.4.1 Premium in the non-sequential mode. My optical system consists of a light source (source radial) with 2 wavelengths and 1e5 beams, 2 detectors (rectangular) and a bulk scatterer (volume physics -> angle scattering) with wavelength shift. So far it is working as I would expect it. But when it comes to ray analysis there are some, at least to me, miraculous things happening. I saved a ray file (polarization, scattering and ray splitting on) and tried to use filter strings in the path analysis window. At first sight it seemed to work but only on the first sight. For example, I tried to get only the beams with wavelength shift. So I used 'X_WAVESHIFT(1,2)' and I got a result. In addition I tried 'X_WAVESHIFT(1,2) & H9' (Object 9 is the one with the bulk scattering properties; the only one in the system) and I got a different result (smaller power). How is that possible? The same thing happens if I use the strings directly in the detector wi
Using more than 1 TOLR operands?
Hello, I am currently optimizing a camera lens for as-built performance, and this has required me to use the TOLR operand for optimizing for as-built performance. However, I am wondering if more than one TOLR operand can be used? As of now, I have been optimizing with the TOLR Data = 2 (estimated as-built performance), and the TOLR value right now is 0.100 RMS WFE, with the nominal WFE being 0.058. If I were to add a second TOLR operand with Data = 0 (estimated change in RMS WFE) to use concurrently with the first with the same weighting as the first TOLR operand, would this help at all with reducing both the total as-built estimate and the estimated change, thereby improving production yield? Or would it just give OpticStudio more to compute and not work as intended? Thanks!
Interpolated Pupil with Zemax
The attached file shows a wavefront with 'spiders' from a telescope. These spiders require a very high pupil resolution for a well converging PSF calculation. But I need to calculate a huge number of PSFs and have to restrict the pupil sampling because of computing time. Is there a possibility for 'Edge Smoothing' in Zemax? I mean a kind of 'apodization' of the spiders that yields a smooth transition from bright to dark that improves the convergence? Additionally: The spiders and the inner obscuration are (as usual in telescopes) not in the plain of the aperture stop. Is the Zemax PSF calculation (FFT or Huygens) still valid?
Why does Zemax (and no other applications) freeze when a remote desktop session is interrupted?
Dear Zemax Community, I'm currently working from home using Zemax ia VPN and Microsoftr Remote Desktop (RDP). Whether RDP is interrupted by a lapse in internet, or is closed manunally, Zemax enters a state of high CPU and GPU utilization in which it is completely non-responsive to mouse or keyboard input. I must force-close and redo actions like Monte Carlo simulations. Other applications on the much faster computer located at work continue to run, and allow me to use them when I return from the RDP interruption. Has anyone else in this forum experienced this? And is there a known fix? Note: I'm running Zemax OpticStudio version 20.1 with a hardkey license.
Ray file in other format
Hi all, I work for Bitron and I use OS in non-sequential environment to simulate illumination on visible switch on cockpit, etc. Many LED manufacturers supply Ray files in formats other than the Zemax Optic Studio format. Can anyone direct me to converters or practices to get usable ray files from OPticStudio? Thanks
MTFS and MTFT computation
I would appreciate some help on how to use the MTF operands. In the 'Optimizing for MTF' help page I can read the following: Note that if you use both MTFT and MTFS (or GMTT and GMTS) for the same field and wavelength data, they should be placed on adjacent lines in the editor; otherwise, the MTF is computed twice. which does not mention 'same frequency' as requirement for ZOS to compute the MTF only once for adjacent lines. But in the 'MTF Data' help page (MTFA operand description) I can find the following: Because only a single spatial frequency is required, the method of computation used by the MTF operands is different, and generally much faster, than the algorithm used by the analysis feature. which makes me believe the 'adjacent lines' trick works only if the adjacent operands are computed at the same frequency. Please can you clarify this to me? Thank you. Furthermore on this topic, is there a way to retrieve the MTFT value from the MECT value? I'm optimizing for co
Upgraded to 20.2.2 and how software wants my license and activation code.
I recently upgraded from 20.2.1 to 20.2.2. When I restarted OpticStudio, the license manager wants me to enter my license number and activation code, as if this is a new installation. I was able to log in to zemax.com and retrieve my license number, but why an activation code and where do I get it? Thanks, -dave
Zemax OpticStudio causeing network problem
Network problems occured as soon as Zemax OpticStudio 20.2.1 Premium was launched, reflected in not being able to access the internet or the default gateway (timeout). And within 1 minute after exiting OpticStudio, network was recovered and everything turned normal. Had tried for 5 times, and things above were reproduced 100%. Please solve the strange problem as soon as possible. Thank you!
aperture type - EPD
Usually, the system aperture is the first parameter defined when starting a new design. The system aperture not only defines the size of the beam which ZEMAX will trace through the optical system, but it also determines the initial direction cosines of the rays launched from each field point in the Object plane. Entrance Pupil Diameter is perhaps the most commonly used system aperture type. In ZEMAX, the EPD is defined as the diameter of the pupil in lens units as seen from object space. That is, axial rays at the object appears to enter the system entrance pupil.
NSC modelling deformed mirror
Hi there, I am thinking of modeling a specific deformation on a mirror in my set up to help develope a pass/fail criteria. I have an interferogram (Zygo image) but I cannot make it into a Zernike model (it is rectangular), I will have to estimate and approximate the shape of the mirror by the data given. Attached an example. I can convert the profile cross-section (marked with red arrow) from fringes to microns, that should not be a problem. My question is: what non sequential object would you recommend that I’ll use for the mirror? Thanks!
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.