Got a question?
Can't find the answer you need? Ask your peers!
- 2,344 Topics
- 6,458 Replies
I want to limit total lens lenght in optimization and I want to do that for left-most point of the lens and right-most point of the lens, irrespective if this point is in the center, on the mechanical edge or even in between. TTHI only gives center thickness. XXET only reports edge thickness on mechanica diameter location. If lens size limitation is on the axis or on the edge only, that works OK. But if i.e. leftmost side is limited on the axis, and righmost side on the edge (concave shape), then also SAG of first and last lens need to be used. I have checked SAGY, but its Description in help is different then what is actual status in MF editor. There is no 'mode' possibility for SAGY and result is given for clear semi-diameter only, but I need mechanical semi-diameter. SSAG allows what I need, but Y (or X) coordinate should be input manually, which does not help me in optimization. I did not find a way how to get SAG value on mechanical semi-diameter automatically. I checked also othe
I have a query During optimization process Zemax varies defined variables and tries to minimize the merit function (optimization). But still I dont know upto what decimal places Zemax varies the defined variables and tries to achieve the better solution. For eg: Suppose I have defined a variable of 'Radius of Curvature' having value 100mm. During optimization process upto what decimal places Zemax varies this value and tries to find the next best solution. Is this trying like new radius of curvature of 100.000001mm and computing the merit function, then next radius of curvature of 100.000002mm and computing new merit fuction etc.. Since my practical limitation is 0.01mm (10 micron) or 0.001mm (1micron), so whether I can tell Zemax to vary the given variables in minimum step size of 0.01mm or 0.001mm only, not finer than this. More fine computation beyond practical limit is wastage of computation energy and time. In short whethe
I am looking for a way to determine the camera calibration matrix using openCV or similar from a lens design in OpticsStudio. Points in 3D object space are trraced to 2D positions on the image sensor and you should know which 3D point corresponds to a 2D point. One method would be to trace one field point (using object height) at a time and read out the spot position from the footprint diagram and then make a short python or matlab program to move around the field point and also change object distance. Or is there a better/faster way? Can the grid distortion plot or similar be used for this somehow? Best regards, /Richard
Hi - I am seeking some information or answers regarding feasibility of modeling non-uniform refractive indicies in the following scenario. I have a cavity with fluid flowing through it at steady state; the beam passes through this cavity as well. The fluid flow analysis predicts variations in fluid properties throughout the cavity's volume and therefore variations in refractive indicies. So my question: Is it possible, in some way, to model the spatially dependent refractive indicies, which are somewhat irregular because they are not symmetric (e.g. rotationally) or easily characterized by a simple axial or radial equation. Essentially, I'm wondering if I can discretize the volume, like an FEM-type analysis. Is this feasible or practically possible? How about DLLs? Regards, Colin
Hello, I have a solidworks assembly file that contains subassemblies. I'ved tried bringing it into a non-seq model as a CAD Soldworks Assembly but get the following error: 'File must represent a SolidWorks assembly and end with the extension SLDASM.' My file is an solidworks assembly and does end with SLDASM. To avoid this error, I've saved it as a STEP file, and have loaded it that way. The CAD file looks as it should in the NSC Shaded Model view. However, when I highlight that object and explode the CAD, several of the parts are missing. The explode dialog box does get the correct number of parts but duplicates several parts while omit others entirely. Is there any way to import the assembly and then explode and edit parts? Thank you, Nick
Hello, I saw some help pages online that mentioned the Ray Trace Control (it is even in the Zemax Help System), but when I search for it in OpticStudio (20.3), the Ray Trace and Lightning Trace is greyed out and unable to be clicked. Did these features get removed recently or someting? I am using Zemax 20.3 Premium edition. Thanks, Jake
I frequently need to determine the MTF of a lens in object space rather than image space.  I would find it a big help to be able to have a check box for "object space, image space". It is easier to present to customers in object space because they can relate to the dimensions.  Also I often need to check the resolution over a focus range (in object space).  It's a bit tedious repeatedly working out the magnification at each focus range to scale the MTF into object space.
Trying to read topics in the Forum is almost pointless, because refreshing the thread list is excruciatingly slow. Why does that need to be the case? The old Forum prior to the MyZemax portal was much better and more like normal forums on the web.
Hi all, When I see a coherent phase in the detector rectangle, the detector viewer shows discontinuous wrapped phase data. I think it is not intuitive to check the phase whether it is right or not because it looks like noise. (But we can check continuous wavefront in SQ mode!) Because the phase is discontinuous, it is necessary for more numerous data relative to unwrapped(continuous) data to represent the complex phase. In this situation, how do you use this 'coherent phase' function in the detector viewer? Are there good examples to understand it? Can I see the spherical wave or plane wave data with a 'coherent phase' at the detector rectangle in the simple lens system? Thanks in advance.
I would like to use the Tolerancing feature on a system with a mirror that has a decentered aperture, to simulate an off-axis parabolic mirror. When tolerancing I would like to tilt that mirror using TETX or TSTX. Will these operands tilt the mirror around the off-axis mirror vertex or around the local axis? Thank you for your time!
Hello everyone, I am trying to create Emission Specturm for Photoluminescence simulation. I noticed that we are required to provide 'Normalized power /relative power of emission wavelengthes' to build the Emission Specturm. I am new in this field and would like to check: This normalized power is normalized with respect to which power? Is it normalized with respect to the Excitation light's power? Hope someone here can help to provide explanation soon. Thank you very much!
Hi fellows, When I insert a real lens to focus a light in a system, Is it a good practice to set its focal length to a variable for optimization purposes? In this image below, surface 2 contains the focal length of the lens in the 'thickness' which is the space to the detector where light is focused. If I optimize this variable and get a nice result, how do I approach this real lens in the market if I am looking for off-the-shelf lenses? Or should I request the manufacturer to make it for me to suit my design? Thank you very much. Naif
I will be sending Support a (proprietary) .ZAR file demonstrating these two issues I just encountered in OpticStudio 20.3 (haven't tried this before, so I don't know if these are new or not). Meanwhile, has anybody else encountered either of these 2 effects (in order of decreasing seriousness): (1) For a concave mirror, I wanted to use a pickup solve from a Thickness (in this case object thickness on Surface 0) to the Radius of the mirror (Surface 1). I wanted to set R = -2H where H is the Object Thickness in order to approximately collimate the light (i.e. set the focal length of the mirror to equal the object thickness, make it concave to the left using a negative Radius). Using a Solve Type: Pickup, I set From Surface: 0 (object) , Scale Factor: -2 (to make Radius = -2*H) and From Column: Thickness. The Radius came out 1/2 the thickness, not 2x !! To get what I needed, I had to set Scale Factor: -0.5 ...only then will Radius = -2.0*H. ??!! Could this have anythin
In OpticStudio 20.3 we implemented new CAD libraries that significantly improved the performance of systems containing imported CAD object. Unfortunately some important information regarding these changes was not included in the 20.3 Help Files documentation. We will be including updated documetation in the next service pack, but in the meantime we'll add the relevent content to this thread to illustrate where behaviour has changed.
Hello, I am trying to set up a model where an LED is inside a plastic cylinder. I would like to know the light distribution pattern that is exiting the outer surface of the plastic cylinder. My thought would be to use a cylinder detector sized a small amount over the OD of the plastic cylinder, but this type of detector is not available. Any thoughts on how to do this?
I was running very simple code in python:  TheMFE=TheSystem.MFE TheMFE.GetOperandAt(1).Value But I got error message:  AttributeError: '<win32com.gen_py.ZOSAPI_Interfaces.IMFERow instance at 0x1627391037392>' object has no attribute 'Value' l confirmed that the Property 'Value' exits when I checked ZOS-API Syntax Help: I also want to config DataType setting as StrehlRation for RMSField analysis, but I cannot make the enumeration correct with python.
Does anyone else have problems saving ZOS lens files across a VPN? It takes minutes to save a file. The same VPN works fine (a few seconds) for large MS application files and Z13 lens files. Other people using the same corporate VPN have the same issue. ZOS seems to work fine across a LAN, BTW..
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.