I am modeling some CPC’s in NSC. I know that they are not 100% reflective and I want to assign a coating to the inside surfaces. But in OS, NSC, there is no way to apply a coating to a surface. Why is this? I can think of many reasons I would want a surface with a coating. A simple cubed beam splitter is one example. Define a cube of glass and then put a 45 degree surface inside with a 50/50 coating. Or, make CPC’s objects rather than surfaces. Anyone have any thoughts to a workaround?Thanks,Paul
Hey everyone. I have a NSC model that contains two sets of CPC’s and a Mersenne relay. My source is an array of conical wavefronts to mimic Cerenkov radiation. I need to trace a lot of rays through the system to the detector to look at the temporal dispersion of rays vs. time (or more correctly, Power vs. Time). So I’m writing my ray trace to a ZDR file. But when I convert it to text, I can’t get all the rays because the file is too large.So I want to try using the ZRD2MAT function that writes the ZRD data to a Matlab.m file.I have no idea how to do this. Currently, I’ve been creating a lot of text files with the ZRD info in them and reading and summing all the Optical Path data to get the total OP from source to detector. then, catching the last Intensity value for that ray and storing the info in a 2D array in Mathematica. It’s a PITA! I’d rather do it in Matlab.What path do I use if Matlab is in one folder and the lens is in another folder?anyone who can help me will get 100 Atta-Bo
Hey everyone, I’m new to this group, although I’ve been using Zemax since 1993. I am very interested in Optics Builder, but whenever I read about it in the manual, it’s difficult to see exactly how I can create objects that I can use in NSC. Can anyone recommend a source that explains in detail what OB can do and how to do it?Thanks,Paul Manhart
I have a suggestion to put a G column in the MFE. This would indicate what surface the operand referred to. Like REAY S4 W2 G6 Hx Hy Px Pythis would mean that you want the Y ray height on surface two, relative to surface 6. It would do away with the global operands like RAGY, RAGX and so forth. It would allow one to get global values for every operand in the MFE. Anyone have any thoughts on this? Am I missing something? Seems so obvious to me. But maybe there’s a reason Zemax can’t make this change.Paul Manhart
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.