Our great sponsors
-
prysm
physical optics: integrated modeling, phase retrieval, segmented systems, polynomials and fitting, sequential raytracing... (by brandondube)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
No, again, it's because the library you were using (whether it's Optix or a twin) has well optimized routines for limiting the number of surfaces considered for intersection. Finding the intersection between a ray and a mesh is strictly slower than finding the intersection of a ray and any of the basic geometries used in optics. A Zernike or Q-polynomial on base off axis conic surface might be slower because the math is awful. But for your basic surface types, you can find the surface intersection faster than you can eve lookup which simplex is most likely to intersect the ray.
Related posts
- How to generate realistic PSFs for camera lenses?
- Prysm is a Python 3.6 library for numerical optics
- Exascale integrated modeling of low-order wavefront sensing and control for the Roman Coronagraph instrument
- Reccomended textbooks/reading for learning Thin Films
- Options for free optical simulation?