​@ma-sunde 

Your intuition is correct, I also think it is a case for batch raytracing. You’ll save a lot of overhead that you’d have with the single raytrace.

​@Ali H wrote a nice section about batch raytracing in the Help File to get you started, also described here:

• New Help File Section on Batch Ray Tracing in Tracing Larger Number of Rays Section

​@MichaelH made a DLL to have fast access to the ray binary data in Python/MATLAB:

https://support.zemax.com/hc/en-us/articles/1500005576882-Batch-Processing-of-Ray-Trace-Data-using-ZOS-API-in-MATLAB-or-Python

If you prototype something and encounter any issues let us know.

Take care,

David

I’m currently using a Two Angle source in non-sequential mode but my challenge is that I didn’t find a way to find the OPL for specific rays simulated.

Looking at the RayTrace.dll I’m now wondering if i could continue to use the Two Angle source, run a non sequential ray-trace and store the zrd file for the raytrace? Using the IZRD Reader, would I be able to read the segments (and specific angular positions of each ray) and OPL from the zrd file? This would avoid using the batch raytracing if I’m not mistaken.

​@ma-sunde 

Indeed, the DLL is made to read ZRD files. Whether you generate them via batch raytracing in ZOSAPI or simply through the user interface shouldn’t matter. Let us know otherwise. And yes you should be able to read segment data as you expect.

EDIT: the DLL was posted in 2021, and there have been some changes in the ZRD format in between as ​@MichaelH  documented in this post:

• Matlab script to group rays from ZRD file to separate paths

Therefore, I’m not sure if the DLL is fully up-to-date, I’ll let you check.

Take care,

David