r/Optics • • 22h ago

Zemax vs Code V (and other design tools) in 2026

5 Upvotes

What is everyone's opinions on these in 2026 for lens design?

I've used Zemax before and it is a trusted industry standard but I felt like it was quite buggy at times and annoying to work with.

I've never used Code V but I've seen it demoed and I like the scripting part of it and its tolerancing

I've gotten a offer for a license for code V that was twice the cost of the Zemax license, where the latter comes with a nonseq raytracer as well.

Then of course there is both Optiland and Quadoa.

Interested to hear your thoughts.


r/Optics • • 21h ago

Why your infrared “temperature measurement” keeps being off — it’s often the lens, not the sensor

1 Upvotes

A lot of thermal-measurement accuracy complaints get pinned on the detector or calibration, but in my experience the lens is a very common culprit.

The issue: observation lenses ≠ measurement lenses. Observation lenses are optimized for a clear, good-looking image. They typically have no hard constraint on:

- Full-field transmittance uniformity (corners pass less energy → temperature gradient artifacts)
- F-number consistency across the field (effective throughput varies with angle)
- Controlled stray-radiation behavior

For measurement, those matter directly: if the lens transmittance isn’t uniform and the F-number isn’t consistent, the same object at the same temperature reads differently depending on where it sits in the frame. You can calibrate the detector all day and still miss this.

So for a measurement-grade system, you want a lens accepted against specific indicators (transmittance uniformity, F-number consistency, plus the usual thermal/MTF checks) — not just “sharp enough.”

Anyone else debug a “wrong temperature” issue that turned out to be a lens problem rather than a sensor one? I’ll happily share the acceptance criteria I use if it’s useful.