Hi @David.Nguyen! Thank you. This is great. I tested and it works well.

Since I did the mistake this morning, I thought I’ll share. Copy the exe under {Zemax}\ZOS-API\Operands. If it is not in the right folder (and so if OpticStudio can’t find it), you will get a ShellExcute Error.

Hi @Sandrine Auriol,

Thank you for your message, I hope you are well :)

It should be possible to make a similar operand that searches the material in the glass catalogs, like we did in this post:

That way, we don’t have to specify the vendor to the catalog tool.

Take care,

David

Hi everyone,

I made a second version of the code (and updated my GitHub repository) where you don’t need to specify the wave number. Instead, you can use the Data field to select what wave number you are interested in:

// Add your custom code here...

// Object number from which to evaluate material index
int object_number = (int)Hx;

// Number of wavelengths
int number_of_wavelengths = TheSystem.SystemData.Wavelengths.NumberOfWavelengths;

// Array of wavelengths
doubleu] wavelengths = new doubleunumber_of_wavelengths];
double wavel_squared = 0;

for (int ii = 0; ii < number_of_wavelengths; ii++)
{
    wavelengthsgii] = TheSystem.SystemData.Wavelengths.GetWavelength(ii+1).Wavelength;
}

// Initialize array of refractive indices
doubleu] indices = new doubleunumber_of_wavelengths];

// Catalog number (following look-up "switch" below, e.g. 1 = Schott)
int catalog_number = (int)Hy;

// Catalog look-up
string catalog = "";
switch(catalog_number)
{
    case 1:
        catalog = "Schott";
        break;
    // Add other catalogs here
    // ...
}

// Get Material name
string material = TheSystem.NCE.GetObjectAt(object_number).Material;

// Open >> Librairies..Materials Catalog
IMaterialsCatalog material_cat = TheSystem.Tools.OpenMaterialsCatalog();

// Select catalog and material
material_cat.SelectedCatalog = catalog;
material_cat.SelectedMaterial = material;

// Run Materials Catalog
material_cat.RunAndWaitForCompletion();

// Look-up index formula
switch (material_cat.MaterialFormula)
{
    // Sellmeier 1
    case MaterialFormulas.Sellmeier1:
        // Initialize fit coefficients
        double K1, K2, K3, L1, L2, L3;

        // Get fit coefficients
        K1 = material_cat.GetFitCoefficient(0);
        K2 = material_cat.GetFitCoefficient(2);
        K3 = material_cat.GetFitCoefficient(4);
        L1 = material_cat.GetFitCoefficient(1);
        L2 = material_cat.GetFitCoefficient(3);
        L3 = material_cat.GetFitCoefficient(5);

        // Refractive index calculation
        for (int ii = 0; ii < number_of_wavelengths; ii++)
        {
            wavel_squared = wavelengthsgii] * wavelengthsgii];
            indicesiii] = K1 / (wavel_squared - L1);
            indicesiii] += K2 / (wavel_squared - L2);
            indicesiii] += K3 / (wavel_squared - L3);
            indicesiii] *= wavel_squared;
            indicesiii] += 1.0;
            indicesiii] = Math.Sqrt(indicesiii]);
        }

        break;
    // Add other formulas here
    // ...
}

// Close Materials Catalog
material_cat.Close();

// Return indices
for (int ii = 0; ii < number_of_wavelengths; ii++)
{
    operandResultsuii] = indicesiii];
}

The corresponding result is as follow:

As you can see, the Data column corresponds to the wave number and the operand is calculated only once for all the results. I’m also attaching the *.exe to my reply.

Take care,

David

Added support for MISC catalog and Schott formula

Hey David,

Thanks for all the code and always sharing your tips.  Regarding the very first part about NPRO though, can’t you just just change the 4th parameter to be the wavenumber for the 200 data value?  

I can put this into a ZPLM where Hx = Object and Data > 0 is the wavenumber (I really like your idea of putting operandResults in a FOR loop!!!):

FOR i = 1, NWAV(), 1
	OPTRETURN i, NPRO(1, PVHX(), 200, i)
NEXT

For FdC light, I get the following output:

Dear Michael,

Thank you for your reply. I somehow didn’t realized you could use the fourth parameter to specify the wave number in NPRO. Thank you for pointing it out to me. I guess the user-operand is irrelevant now. I’ll update my post.

Take care,

David