</PRE></P><P><A name = "Census"><H2>Census</H2></A><PRE>  <a href = "#Census">Census</a> Script  This script and report tabulates the status of all the m-files in the MZDDE directory.  Usage : census    See Also : <a href = "#docgen">docgen</a></PRE></P><P><A name = "DoublePass"><H2>DoublePass</H2></A><PRE>  <a href = "#DoublePass">DoublePass</a> - Put a lens into double pass.   Usage : Status = DoublePass(j, k)   Takes a series of surfaces (j thru k) and puts them into double pass,  mainly with the help of pickups.  Surface k will typically be a mirror surface. If not, the ray path is  merely reversed. Note the following ...  1) Inserts surfaces k+1 to 2k-j. This is a total of k-j surfaces.  2) Inserts pickups of thickness, radius, conic constant, glass, semi-diameter     and all lens data parameters. Coatings are copied to the new surfaces.  3) Radii, conic constant and parameter pickups are inserted without a sign     change.  4) Thickness pickups are inserted with sign change.  5) Coordinate break surfaces are forced to a reverse order with a pickup      having a scale factor of -1 and an offset of 1 for the mode flag. This      only works properly if you use a mode of 0 or 1 to indicate the order.  6) Folds or other z reversals may not be handled correctly in all cases,     but seem to work in simple cases.  7) Many cases seem to be handled correctly, but check your model     carefully. A sensitive test is to put the     system into double pass without a mirror. Any ray should be exactly     reversed through the system.  8) User-defined apertures are not dealt with. Other apertures are kind of     fudged by copying some stuff and picking up other stuff.  9) Non-sequentials ? You are right out of luck. Why would you want that ?  10) This function should leave all existing surfaces untouched except surface k.      Otherwise only newly inserted surfaces are      meddled with. Suggest you save the lens before doing this.  11) If there are multi-configuration parameters applicable to the image      surface, and k is the image surface      you will probably not get what you want. Other multi-configuration      systems should come through ok.  12) The image surface can be a mirror surface, and this is useful when      going into double pass, if only to      put the mirror in automatically where the path reverses.   The following surfaces types are explicitly handled or often work  correctly. Others may also work.  STANDARD, EVENASPH, ODDASPHE, COORDBRK, PARAXIAL, PARAX_XY, TILTSURF,  TOROIDAL  Surfaces requiring extra data will not work.    The returned Status is an integer which has the following meaning   0 - Everything seems to have gone OK.  1 - Final surface (k) exceeds the number of surfaces - k assumed to be the image surface.  2 - First surface (j) coincident or beyond last surface (k) - you have been ignored.  3 - A surface type which is not explicitly supported was encountered - check your results. </PRE></P><P><A name = "IntSphere"><H2>IntSphere</H2></A><PRE>  Compute the spectral radiance of an integrating sphere.    Usage : SpectralRadiance = IntSphere(SpectralFlux, SphereDia, PortAreas, InitialReflectance, PortReflectance, SphereReflectance, Wavelengths, Interp)   SpectralRadiance is the spectral radiance of the sphere in units of watts per steradian per square centimetre per micron of wavelength.  SpectralFlux is the radiant spectral flux injected into the sphere in units of Watts per micron of wavelength.  SphereDia is the diameter of the sphere in cm.  PortAreas is a row vector of the areas of the input and output ports in square cm.  InitialReflectance is the spectral reflectance of the surface which diffuses the flux into the sphere (possibly the inner sphere surface itself).  PortReflectance is an array (one column per port) of port reflectances for all input and output ports in the same order as  in the PortAreas vector.  SphereReflectance is the spectral reflectance of the general interior of the sphere. If SphereReflectance has a single row,  then the relectance is assumed to have this value across the entire spectral band.  Wavelength is a column vector of wavelengths at which to compute SpectralRadiance given in microns.  Interp is the method to use for interpolation of values. The options are   'nearest' - Nearest neighbor interpolation  'linear' - Linear interpolation (default)  'spline' - Cubic spline interpolation  'pchip' - Piecewise cubic Hermite interpolation  'cubic' - (Same as 'pchip')  'v5cubic' - Cubic interpolation used in MATLAB 5  See interp1.   Except for PortAreas, all input parameters must be supplied with associated wavelength data in microns in the first column.  All wavelength data must be monotonically increasing.    The output data will be computed at the wavelengths given in the Wavelengths vector, which must be a column vector.  The wavelength data for all input parameters must span the range of the output Wavelengths, otherwise an error is  generated.   Reference : Integrating Sphere Radiometry and Photometry, Labsphere Corporation, http://www.labsphere.com</PRE></P><P><A name = "LSF"><H2>LSF</H2></A><PRE>  LSF(Wavelengths, Focal_Ratio, X-Coordinates)   Computes the monochromatic diffraction-limited line spread function at  the given wavelengths (rows) at the coordinates given by x.  x must be monotonic upward and equi-spaced.   The <a href = "#LSF">LSF</a> is computed using a fast fourier transform technique on the <a href = "#MTF">MTF</a>  computed from a closed-form expression. </PRE></P><P><A name = "MTF"><H2>MTF</H2></A><PRE>  MTF(Wavelengths, Focal_Ratio, Frequencies)   Returns the diffraction limited monochromatic <a href = "#MTF">MTF</a> for each of the wavelengths given (rows)  and for each of the frequencies given (columns).    If the frequencies are given in cycles per millimetre, the wavelengths should also be in mm. </PRE></P><P><A name = "NarcWiz"><H2>NarcWiz</H2></A><PRE>  <a href = "#NarcWiz">NarcWiz</a> - Narcissus analysis wizard   Usage : NarcOut = <a href = "#NarcWiz">NarcWiz</a>      % NarcOut is case sensitive          report narcissus   Takes the user through a narcissus analysis of the lens in the ZEMAX DDE server. NarcOut is a  structure containing various items required for the report generator, so the function must be  called exactly as shown above. The report will be generated in rich text format (.rtf) and  displayed in MS Word.   The general restrictions and assumptions are as follows :  1) The lens model to be analysed is for a 3rd generation thermal imager using a cooled detector     which has a cold stop. The cold stop is assumed to be at the surface before the image surface     and the detector window is assumed to come before the cold stop. Clear apertures of these     objects must be set correctly.  2) The inside of the dewar has emissivity of 1 all over and across the spectral band.  3) The side of the cold stop facing outward has a user-defined emissivity and the same temperature     as the inside of the dewar right out to the clear aperture of the dewar window.  4) Emissions and reflections of thermal radiation by non-optical surfaces are lambertian.  5) Lens must be single configuration. Save and analyse each configuration seperately, taking     special care to ensure that the apertures are as they would be for the system as-built. It is     particularly important that the clear aperture of the dewar window is correctly set from     mechanical drawings of the dewar.  6) Only rotationally symmetrical lenses are currently handled - mainly a     retriction of the ZEMAX functions used for the computation. The whole     approach to the problem would have to change significantly to cater     for non-symmetrical systems.   The general functions performed are as follows :  1) Create a directory named after the lens to be analysed in which all results will be saved. The     directory name will have the .Narcissus extension.  2) Ensure that the system is correctly set up, has clear apertures and coatings defined. Currently this is     done by appealing to the users's sense of thoroughness.  3) Compute system transmission, YNI contributions and uniformity of image illumination.  4) Reverse the lens and create single bounce ghost reflection models for each optical surface.  5) Compute the Narcissus-Induced Delta T contributions for each surface.  6) Plot total NITD, NITD per surface and overall image irradiance uniformity per configuration.  7) Generate subjective images of image non-uniformity.  8) Rank surfaces in order of contribution to NITD and tabulate with YNI contributions.  9) Compute maximum slope of total NITD and overall image non-uniformity. This gives an indication     of the local visibility of the image non-uniformities.  10) If the user gives the command 'report narcissus', a report will be generated in MS Word,      containing all of the outputs.   Possible return values for <a href = "#NarcWiz">NarcWiz</a> are   0 - Everything seems to be OK  -1 - ZEMAX not running and could not start ZEMAX.  -2 - The lens you wanted to analyse cannot be raytraced.  -3 - Lens has fewer than 6 surfaces. Detector + cold stop + window + 2 additional lens surfaces is       six at least.  -4 - Lens does not operate primarily in a thermal band.  -5 - Lens is multi-config. Currently we only do single config. Save and analyse each config       seperately.  -6 - User cancelled wizard.  -7 - Double bounce ghost lenses were encountered - restart analysis.  -8 - Lens has wrong field type. Change to "real image height".</PRE></P><P><A name = "Onion"><H2>Onion</H2></A><PRE>  <a href = "#Onion">Onion</a> - Splits a lens into a number of layers for the purpose of analysing the effect of an axial  temperature gradient.   Usage : Status = Onion(Surface, Layers, T1, T2)   Where Surface is the surface to split up, Layers is the number of layers to use, T1 is the temperature at  the given surface and T2 is the temperature at the following surface. Currently, only standard surfaces are  handled correctly. There must be sufficient MOFF operands in the multi-configuration editor to accommodate  the new TEMP and GLSS operands i.e. there must be at least (Layers + 1) * 2 operands of type MOFF. These   MOFF operands must appear at the start of the list. The reason for this is that there is currently no way   to insert multicon operands from the DDE interface.   Note : To correcly evaluate the thermal effect, the "Use Temperature and Pressure" box on the general  settings dialog must be checked.   Status is the return status.   0 indicates success.  -1 indicates that ZEMAX is not running.  -2 indicates that the lens could not be updated.  -3 indicates an invalid surface number.  -4 indicates the surface is too thick (INFINITY).  -5 indicates the surface has zero thickness.  -6 indicates that there are insufficient MOFF operands at the start of the multicon editor.</PRE></P><P><A name = "PMTF"><H2>PMTF</H2></A><PRE>