Hi Jose,

Is there a particular reason you want the Python code to execute from the macro? Cause, in my mind, the most straight-forward way is perhaps to create a standalone ZOS-API application, such that OpticStudio runs within your Python code.

Otherwise, you might want to have a read at that article from Michael Humphreys.

Take care,

David

Hi Jose,

In my personal opinion, ZOS-API is the way forward. The learning curve is steeper, but I think its worth the time thanks to the possibilities offered by the Python environment, or any other ZOS-API langage.

You can call a macro from ZOS-API, but its a bit glitchy. To the best of my knowledge, you have to make the macro as a solve, and return a dummy value. Otherwise, if time permits, you can translate your macro to ZOS-API entirely.

I will try to prepare an example following your requirements.

Take care,

David

Hi David, 

Thank you very much for the great help. I will carefully review the material you've sent and see if I can get a simple example to work.

I will then let you know if I have some difficulties. 

Cheers,

Jose

Hi Jose,

This is a really good resource actually, thanks for sharing that.

I would suggest the following snippet, but it is not currently working.

The idea is to run a Tolerance Data Analysis with a single MC run multiple times, save the Tolerance Data in a text file (*.ZTD) at each step and read the MF value from the text file.

I had mainly two problems.

1. The *.ZTD file saves in a weird encoding from OpticStudio (I tried changing Setup..Project Preferences..General..TXT File Encoding without success) and I have troubles reading them with Python. Maybe you can have a go and tell me what you think.

2. To verify that having a single MC run was working, I saved the Best/Worst MC runs, and opened it. Unfortunately, for me, the file did not contain the coordinate breaks. So, it might not be possible to run a single MC.

Alternatively, one could save the Best MC run, open it, and evaluate its MF, but reading it from the *.ZTD file sounds like a better idea.

I hope this can help a bit, and maybe someone from Zemax can jump in :)

Take care,

David

Hi Jose,

Maybe I misunderstood what you intended to do in the first place.

UDOC is a good idea, what I would suggest is translate your Python code to C++/C# and embed it into the UDOC. It'll be so much faster as opposed to the UDOC calling an executable built on Python.

This is a good article to get started, and here you have another example of a UDOC I made to help someone else on the forum.

Let me know if this helps, and how you are getting along.

Take care,

David

I was just thinking that it could be difficult to re-write the python code with all the calculations - I don't have experience with C#

How about running the Python script from the csharp boiler plate code using IronPython. Still slow?

Hi David, 

Thanks for your answer and previous help. 

I finally managed to make a UDOC in Csharp that runs a Python program to calculate the operand result (see attached code).

• The Csharp code changes settings of a POP analysis and saves a few .txt files that the Python code uses for calculations.
• Csharp can read the values printed by Python and updates the operand result

The problem is that it only works to update the Merit Function. Once you ask OpticStudio to run the Montecarlo, the process somehow cannot keep up and one gets results like the one in the pic below. Some values are calculated but then they repeat, and sometimes there is some problem in the program (0 values).

I could test that this “synchronisation” problem is the due to the saving text file part from the command   

POPDef.ToFile("xxx.txt");

If one comments the line, the problem is not there (except for that I always get the same result since I read the same files...)

I have tried adding a pause in different places of the code without success

Any ideas on how to solve this?

Cheers,

Jose

Hi David, 

I know your approach would be more efficient, but I would like to have this tool that can use the Python code for calculations also in the future, since we use Python routinely. Also the calculations are long to translate to Csharp.

I feel that this problem should ideally have a simple solution, but it is being quite hard to find the way to synchronize the process. Also I am so close to the end now with this approach.

Cheers,

Jose

Hi David, 

I had a call with Zemax support and they figured out what the problem was :) 

One has to select only 1 core to do the tolerancing-then everything magically works. I had selected 12 cores by default, but  the task cannot be solved in parallel (at least with my code). 

I tried previously the polling you suggested, but that was not the problem. I also checked the polling is not needed when one selects 1 core. I did add some code to delete the files after I call the python code.  

Thanks for your advice and hope you also learned something ;)

Jose