Skip to main content
Solved

Where is the nominal criterion value in my tolerance output coming from?

  • April 24, 2019
  • 1 reply
  • 481 views

Allie
Zemax Staff
Forum|alt.badge.img+2
  • Zemax Staff
  • 337 replies

Why is the nominal criterion value different from my Merit Function value in some cases? Is there a different analysis feature in OpticStudio that the nominal criterion is supposed to match up to? If not, then how is it being computed?

Best answer by Allie

There are a few reasons why the reported nominal criterion from the tolerancer may be different from that of the value reported elsewhere in OpticStudio:
 

  1. When computing the nominal criterion in the tolerance analysis, OpticStudio considers any compensators which are defined. This means that OpticStudio optimizes for the best criterion value using the defined compensators as variables. The Merit Function or any other analysis feature in OpticStudio on the other hand, is evaluated without any compensator adjustment.
     
  2. Sampling methods and sampling sizes may be different. In constructing physically significant Merit Functions for a selected criterion, OpticStudio uses Gaussian Quadrature pupil sampling. Some analysis features in OpticStudio use Rectangular Array sampling, which may result in a slightly different value than that determined using the GQ method. Theoretically, as the sampling size of both methods increases, the calculated results will approach equality. Similarly, even if the same sampling method is used, sampling size can have an effect on the outcome of a calculated value. Make sure that the sampling size is sufficient in either calculation before making a comparison of the results.
     
  3. By default, OpticStudio reports a single criterion value which is the root-mean-square (RMS) across multiple wavelengths, fields and/or configurations. The results may be separated by field and configuration, but make sure that when comparing a value from a specific analysis feature vs. that of the nominal criterion, the data corresponds to a single field or the RMS across all defined fields and/or configurations.
View original
Did this topic help you find an answer to your question?

1 reply

Allie
Zemax Staff
Forum|alt.badge.img+2
  • Author
  • Zemax Staff
  • 337 replies
  • Answer
  • April 24, 2019

There are a few reasons why the reported nominal criterion from the tolerancer may be different from that of the value reported elsewhere in OpticStudio:
 

  1. When computing the nominal criterion in the tolerance analysis, OpticStudio considers any compensators which are defined. This means that OpticStudio optimizes for the best criterion value using the defined compensators as variables. The Merit Function or any other analysis feature in OpticStudio on the other hand, is evaluated without any compensator adjustment.
     
  2. Sampling methods and sampling sizes may be different. In constructing physically significant Merit Functions for a selected criterion, OpticStudio uses Gaussian Quadrature pupil sampling. Some analysis features in OpticStudio use Rectangular Array sampling, which may result in a slightly different value than that determined using the GQ method. Theoretically, as the sampling size of both methods increases, the calculated results will approach equality. Similarly, even if the same sampling method is used, sampling size can have an effect on the outcome of a calculated value. Make sure that the sampling size is sufficient in either calculation before making a comparison of the results.
     
  3. By default, OpticStudio reports a single criterion value which is the root-mean-square (RMS) across multiple wavelengths, fields and/or configurations. The results may be separated by field and configuration, but make sure that when comparing a value from a specific analysis feature vs. that of the nominal criterion, the data corresponds to a single field or the RMS across all defined fields and/or configurations.

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings