Hi,

I stumbled on that problem a few weeks ago. Here is what I found, if you want to change your python code:

At the end of the float section, 2 doubles (64 bits) and what looks like 2 integers (2* 32 bits) have been added. Comparing ZRD file reader between an old and a new opticstudio (and also the release notes), the two doubles are “Optical Path Length in Waves” and “Optical Path Length in Lens Units”. For the last 2 integers, I don’t know, but they do not not look like a double, although they are located in the float section. Could be related to the diffraction orders or perhaps the sensor size. So you can e.g., skip 3 doubles from each segment to be able to read format 2003.

A few hours ago I also found that there is a 24 Bytes offset at the end of each segment.
Adding this offset in the read does the job. Good to know, that you found what the data is.

Still it is a little anoying that the file format changed, while the documentation is unchanged.

For reference, here is the release notes post which help to identify the new entries. This release also has a much improved path analysis.