We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
Hi all, I’ve been modifying .zmx files using Python for a few years now and have been using my own module and PyZOS for a majority of it now. However, my current project has a bit of a road block I’m not sure how to get around. What I would like to do is take a surface from a file I’ve already created and have it be the exact same surface in a different file. I could have the code insert the surface, but if possible I’d like to avoid inserting and deleting surfaces as it may effect other parameters in the system (i.e. Merit Functions operands and whatnot). What I’m hoping to code is something like the following import zospy as zp zos = zp.ZOS() oss = zos.connect() oss.load(‘file1’) oss2 = zos.create_new_system() oss2.load(‘file2’) first_surface_file1 = oss.LDE.GetSurfaceAt(1) first_surface_file2 = oss2.LDE.GetSurfaceAt(1) #Modify somehow first_surface_file1 == first_surface_file2 #would like to be True I was thinking of somehow looping through the surface params but that’s proving diff
Hey everyone, I am going to teach an OpticStudio course at a university and they have an academic license for all Ansys products including OpticStudio. However, what surprised me is that as far as I understood it is not possible for students or me to install and use OpticStudio locally, without a remote connection to the university Ansys server. I distinctly remember that a few years ago I did an online course at a university and got an OpticStudio license which I could use without any problems fully locally. Did the policy change? Is it not possible anymore to just have OpticStudio run locally with an academic license on your private PC? Best regards, Mikayel.
I’m trying to create a curved surface within the zemax part designer. Whenever I expose a point on my 2D sketch the expose point parameter greys out on all the points in the sketch. I am unable to check or uncheck the box for any of the points. I would like to expose all 4 points in the 2D sketch. Any idea why I’m unable to expose all the points. *Here is an image of the sketch. The I cannot check the expose point. *Here shows a point that was exposed but I’m unable to uncheck the box.
Good day everyone, since ZPL is based on BASIC, I thought some of it generic functions could be used for converting variable types such as VAL(), INT() etc. Only $STR works, the other conversions are not recognized by ZPL. In particular, I want to define a single variable in my script (a particular detector number) and use it for both console output (with PRINT), non-sequential raytrace (with NSTR) and changing Detector Viewer settings (with MODIFYSETTINGS). I could define either a numerical variable and change it to string, but doing so outputs a floating point number (such as 5.000 for instance). Unfortunately, NSTR is having trouble with "h5.000” filter string. Then I thought I can define a string variable "5” and change it to numerical but no commands that I know seem to work. Is there a solution to my issue that would allow me to stay within ZPL script, not switching to ZOS-API?
Hello fellow Zemax-ers! As we continue our integration efforts into Ansys systems, the Zemax Community is preparing to migrate into the Ansys Learning Forum (ALF), found within the Ansys Innovation Space (AIS). With the move happening soon, we are closing the Zemax Community to new registrations starting next week, March 24th. I will post more details about the migration of the forums soon, but in the meantime, please find some prepared FAQs below. Let me know if you have other questions! Why ALF? The platform is already the home of the Lumerical and Speos forums, so now all of Ansys Optics will be in the same place! Also, posts within the ALF space are parsed into AnsysGPT alongside knowledgebase articles and online tutorials, making it easier for you to find the answers to your questions all in one place! Who can sign up for ALF? Anyone! Unlike ACSS (discussed here), AIS has no restrictions on who can sign up. All you need is an email address, though we recommend using your work/univ
Share your tips & tricks for efficiently using OpticStudio with the community! There are lots of little ways that we adapt our use of OpticStudio to streamline our work. These are usually learned over time, from colleagues, or from technical support, but they aren't typically found in other product education resources. You might have a favorite keyboard shortcut, saved settings for a particular analysis, a macro that automates 3 steps in your process tied to a hotkey, or a million other ideas. Help your fellow OpticStudio users and learn some new tricks yourself.
Hi, I would like to use the ZRDPLAYBACK function, but it doesn't seem to work, I think it doesn't take filters string into account. I have similar problem iy I use a function like NSTR 1, 1, 0, 0, 1, 1, 1, 1, A$ ,”W1”,2 Marc.
Dear Zemax community, I am building upon your 'How to design a Gaussian to Top Hat beam shaper' tutorial. Instaed of TOP HAT, my goal is to create a Uuniform Radial Distribution at distance of 1M from the beam shaper. i.e my goal is to create a uniform distribution on a sagment from a rolled screen. But the ZPL calculates the desired distribuion up on a flat wall, so what should be the distribution up on a “Flat screen” , so it generates a unifrom radial on a rolled sceen ? Any suggestions are welcome and appreciated. Thank you very much, Tali
when i use ZPL output to a text file , The output always stops halfway, and Zemax prompts "cannot open text file". Does anyone know why? For example, I plan to output 40,000 lines of data, but it stops at 10,000.
My codes (that were working with the 2024 version) do not work anymore with the 2025 release.This is the error I get: Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'ZemaxEngine.dll' or one of its dependencies. A dynamic link library (DLL) initialization routine failed. (Exception from HRESULT: 0x8007045A).
I have a sequential mode design that contains a black box component. I converted the sequential mode design to non-sequential mode, but the black box is not converted. The non-sequential component editor box does not have the black box. What can I do to have the black box insert into the non-sequential component editor box?
Hello everyone! I am trying to perform a study of tolerances in an optical system in which my criterion is the RMS Spot Size. If possible, I would like the GEO radius for one of the fields not to exceed a certain value (with reference: vertex). In any case, it is not possible for me to execute the tolerancing because of a problem that I show you here: “Nominal Criterion cannot be computed”. Do you have any suggestion? Thank you!
Ansys Zemax OpticStudio 2025 R1.00に先日アップデートしたところ、スポットダイアグラムが保存できない現象が出ております。エラーメッセージの画像を添付いたします。改善方法をご教示いただけないでしょうか?以下がわかったことです。 この現象はファイル依存性はなく、ZOSを立ち上げた際の初期ファイル(LENS.zmx)でも起こっています。 この現象はPC再起動をしても、ソフトを再起動しても改善できませんでした。 この現象はスポットダイアグラムの画像保存時には起こりますが、3Dレイアウトの画像保存時には起こっていません。 以上、どうぞよろしくお願いいたします。
In the IAS_ZernikeStandardCoefficients settings, there is a setting called : ReferenceOBDToVertex (not sure what OBD means) while in the GUI it is called: Reference OPD to vertex which makes more sense
Hello, Not quite sure this community is still active? I want to have a lens system which can form the image from infinity to a limited distance as show below. As you can see that the concave lens system will reduce the input field of view. How can I have a compact concave lens system which can form the image from infinity to a limited distance and keep the same field of view as the input. Can you have some suggestions or initial configuration for recommendation? Thank you ! BL
So I have a NSC system consisting in multiple mirrors and with 3 Detectors. I was using the ray trace tool with only 1 analysis ray and then optimizing with the Merit Function editor until some weird optimization started to happen. Then I read this sentence in the Help system: Note the segments NSRA is not listed in same order as in ZRD. For example, for a same ray, the segment with Seg# =17 in NSRA is not same to the 17th segment listed in ZRD. How can I know the number of the segment I want to optimize then for the NSRA operand? Regards
130 points
122 points
55 points
45 points
39 points
23173 points
14493 points
13087 points
11054 points
9986 points
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.