Hi Jaren,

This worked for me on Windows (path) with an Interactive Extension, let me know if it gives you what you need. I forgot to mention, it should create the text file in your sample directiory as defined in the OpticStudio settings.

Take care, David

Thank you for this discussion.  Is there a way to access the data from the pupil map directly without creating a separate text file?  For example, could I just take the results and then create a numpy array with the pupil location and electric fields and phase.  Or do I need to create a text file and then load this into python to create the array?

Hi Scott,

Last time I checked, the Polarization Pupil Map wasn’t fully implemented into the ZOS-API. Therefore, you have to create the intermediate text file. Some analysis are partially implemented, meaning you can read an array directly, or edit the settings directly from the ZOS-API, some analysis are fully implemented, meaning you can do everything from within the ZOS-API. The developers are constantly implementing theses features, but I guess they prioritze the most utilized analysis features first.

If you want to know more about what status is a particular analysis, have a look at this article. Although, I wasn’t able to run the code as it is documented now (I think it uses an old boilerplate template), the method described there are generally valid (in some rare instances, an analysis, like RMS vs Field, might return a DataGrid or DataSeries although it is empty...).

Take care,

David