Skip to main content

One year ago, ​@Xianglei wrote a topic (thanks a lot!) about:

Since its been quite painful to generate such plots with ZPL (thanks to ​@Erin.Elliott, we might get a fix in 2025 🤞):

I’ve been using the ZOS-API option more and more to create animations. It is more stable, but currently lacks a couple of options. Since we’re approaching the Christmas period 🎅, this is my wish list to improve the ZOS-API Layout Exports feature (in order of importance):

  1. As far as I understand, we cannot specify the file type of the export. I’ve tried to use multiple extensions in OutputFileName (.JPG, .PNG, ...etc.) but the file size remains the same. Based on the file size, which is rather small (for a given image size), I’m assuming the export is made in .JPG regardless of the extension specified. Can the file type be added to the ZOS-API?
  2. Could we get a vector graphics file type?
  3. Although there’s a property RaysLineThickness, for me, it doesn’t seem to have an effect. If someone is anyway going to look at this, would it be possible to have a line width (integer) property instead?
  4. Could you also add a property to disable the RGB axis at the bottom-left corner of the layout?

Thanks a lot,

 

David

Hi, David.  1 and 3 sound like possible bugs.  Could you work with Support, so they can check those and submit, if needed?

Thanks ​@Erin.Elliott. Does the ZEMAX support address still work? Because I have an academic license and last time I checked I couldn’t login support tickets.

Take care,


David

Hi ​@David.Nguyen, thanks for the post here and the questions. We’re looking into the points 1 and 3 mentioned by Erin. Looking at 3., it does indeed have an effect for me, same as the Layout plots in the GUI. We are taking a closer look at 1 as well.

To speak to the question of support, in general, academic license questions indeed need to go through our forums (see the section Academic Support in the link). For OpticStudio questions, at the moment we are monitoring questions here on community.zemax.com, but questions can also be asked at our Ansys Learning Forums.

That said, if bug-related issues arise and there is a need to hand-off confidential data to investigate the bug, we can open a discussion separately (that is, not public) to preserve proprietary/sensitive information.

Regarding your issue with the rays thickness not changing, how are you accessing the ZOS-API -- Python, MATLAB, etc.? I checked with Python and it seemed to work fine, so checking in your language would be the next thing I should do.

Thanks, and looking forward to hearing back!

Hi ​@Angel Morales, good to hear from you.

 

Regarding 3. I’m actually using ZOSPy, and I don’t want to add to the confusion by sharing my code here (unless necessary). I tested again today, and you are right that RaysLineThickness works. Its just that the difference between thickest and thinnest isn’t obvious (zoomed-in screenshots below).

Ray Line Thickness = Thickest
Ray Line Thickness = Thinnest

I’m using pixel width/height of 3840/2160. There is no bug in that sense, but if we could have a bit more control over the thickness of the rays that would be awesome 😃

Take care,


David

Reply


Community Posting GuidelinesCookie settings


Zemax Community

Need more help?

To Chinese users:

Do not provide any information or data that is restricted by applicable law, including by the People’s Republic of China’s Cybersecurity and Data Security Laws ( e.g., Important Data, National Core Data, etc.).


不要提供任何受适用法律，包括中华人民共和国的网络安全和数据安全法限制的信息或数据（如重要数据、国家核心数据等）。



Privacy policy   License Agreements    Terms of use    Cookie Policy   Zemax Account Licensing Policies