Calendar
Introduction to CODE V
October 18-22, 2010
Munich, Germany
Contact OEC
Advanced Topics in CODE V
October 18-22, 2010
Munich, Germany
Contact OEC
SPIE Photonics West
January 22-27, 2011
San Francisco, California
SPIE website
Introduction to CODE V
March 14-18, 2011
Pasadena, California
More information
Advanced Topics in CODE V
March 21-25, 2011
Pasadena, California
More information
For a complete list of CODE V events worldwide, visit our Web site:
|
|
CODE V 10.2 Service Release 3 (SR3) Is Now Available for Download
We are pleased to announce the availability of CODE V 10.2 SR3. This service release patch requires that CODE V 10.2 has already been installed on your PC.
CODE V 10.2 SR3 contains fixes to a number of customer-reported bugs, as well as glass catalog updates, as described below.
Issues Resolved Include:
- In Beam Synthesis Propagation (BSP), the Gaussian beam fitting (GFT command) sometimes gave incorrect results for beam radii (X-Rad, Y-Rad) and coordinates of the Gaussian peak (X-Shift, Y-Shift).
- Ray trace errors occurred in lens systems with an interferogram assigned to the exit pupil, when the image space index of refraction was not 1.0.
- Ray trace errors sometimes occurred when surface deformation data (SUR INT) was assigned to a surface in a non-sequential range.
- Optical path difference (OPD) magnitudes were incorrectly calculated when surface or wavefront deformation data (SUR INT, WFR INT) was applied to a refractive interface in a non-sequential surface range.
- Plots generated by the Gaussian Beam Trace (BEA) option displayed incorrectly when A4 paper size was specified (PPS A4 command).
- Zoomed UD1 and UD3 surface coefficients were handled incorrectly when the lens system was dezoomed.
- CODE V crashed when more than 990 surfaces were inserted into a lens system.
- CODE V sometimes crashed when optimizing systems containing Zernike polynomial interferogram files.
- In systems with non-sequential ranges, the OPD calculated from a ray trace was not stored as a database item.
In addition to resolving customer reported bugs, CODE V 10.2 SR3 includes major updates to the CODE V glass catalog including the Schott, Ohara, Hoya, Hikari, and CDGM manufacturers' catalogs. Click here for more details on the glasses affected by this update.
CODE V Tip – Running MATLAB from CODE V
Like most optical engineers, your job probably requires a suite of tools, not just CODE V. Integrating these tools can help increase your productivity. A member of the ORA Engineering team recently developed a way to better integrate CODE V output with MATLAB. The method he developed uses a CODE V User-Defined Subroutine (USR) and supporting CODE V macro to launch MATLAB and send native MATLAB commands to it from the CODE V prompt. This provides users with quick access to the matrix math and graphics engine of MATLAB for post processing of CODE V data.
The animated .gif below (click on the image to see the animation) is an example of using PMA data produced by CODE V to create a brief movie showing the fringe shift as seen using a phase-shifting interferometer.
Caption (click to see animation)
The CODE V USR and macro needed to support communications with MATLAB, as well as other examples and supporting files, are available for download from ORA’s Customer Service Portal, http://support.opticalres.com, under CODE V Support > Macro and User-defined Feature Downloads.
|
