raytracing and lens design framework
Optics design (lenses, cavities, gaussian optics, lasers). Geometric, paraxial, and gaussian ray tracing.
Install like any usual Python package using pip, easy_install, or plain setup.py. Anaconda packages from three operating systems and three current Python versions are available through Anaconda. Install with:
conda install -c https://conda.anaconda.org/jordens/channel/ci rayopt
The distribution already contains all materials from http://refractiveindex.info/.
More materials and lenses catalogs can be obtained from the freely available versions of Oslo and Zemax, copied to catalog/ and then parsed using rayopt/library.py (see there for details on where the files are expected):
get and install http://www.lambdares.com/images/OSLO/OSLO662_EDU_Installer.exe get and install http://downloads.radiantsourcemodels.com/Downloads/Zemax_2015-03-03_x32.exe $ python -m rayopt.library \ Users/Public/Documents/OSLO66\ EDU/bin/lmo \ Users/Public/Documents/OSLO66\ EDU/bin/glc \ Users/$USER/My\ Documents/Zemax/Glasscat \ Users/$USER/My\ Documents/Zemax/Stockcat
The choice of prescription specification is a little different from most other lens design and ray tracing programs. RayOpt associates with an element (surface):
Ray data are given at (ray intercepts) or just after (direction cosines, paraxial slopes) the respective element unless stated otherwise (e.g. incidence angles).
The choice of associating the “distance to” and not the “thickness after” with a surface has several advantages: shifts, offsets, tolerances can be implemented in a more straight forward manner, ray propagation becomes more natural and efficient (transfer, intercept, refraction), ray data at the surfaces’ apex planes does not need to be tracked. The “thickness after” does not have much meaning in ray trace data as it can only be used later when tracing toward the next element and its direction is typically ill defined. Compared to most other programs the distance data is the thickness data shifted by one element towards the object.
Object and image are located at the first (index 0) and last (index -1) surface respectively. This naturally allows tracking their positions, material and shape data and supports curved objects and images naturally. Further data like pupils data are maintained in the two Conjugate s of the System.
Therefore, a minimal system of a single lens consists of fours surfaces: object, the two lens surfaces (one of which can be the aperture stop) and the image surface. The offset data of the first (object) surface does play a role in ray tracing but it can be useful as it locates the global coordinate system’s origin. The material of the last (image) surface is used as it can cause incident rays to be evanescent at the image surface. This can also be compared to other programs where the thickness of the image surface is never relevant or the material in object space and the position of the lens has to be tracked somewhere else depending on the implementation.