Il y a aussi la Fresnel 2 si la Fresnel 1 convient pas.
Watch out OpticsBuilder User Group the new OB course on OpticsAcademy is now available. With this course the OpticsBuilder users can learn the basic concepts of optics required to package, analyze, and validate optomechanical systems and describe how the Zemax ray trace engine calculates and measures optical performance, how to apply the conversion workflow from Zemax OpticStudio to the CAD environment with the OpticsBuilder add-in, understand how to use the vast variety of OpticsBuilder tools on use-case example and how to use the optical drawings feature of OpticsBuilder.You can find it here: Designing Optomechanical systems with Zemax OpticsBuilderIf you have any question, please do not hesitate to contact support@zemax.com or reply to this post.By Flurin Herren, Optomechanical Engineer, Zemax
That a great way to work around the fact that the ZPL macro language is not '’aware'’ of which configuration it is in.And it is not convenient to manually have to create one macro for each config. That's what the API code is doing, great stuff!Thank you for sharing, Sahil!
In summary:The ZBF stores E field data as Re and Im parts. The intensity is just Re^2 and Im^2, and the phase is tan^-1(Im/Re). Here is how the sum of two rays is working:Let's have val1 = er1 + i ei1 and val2 = er2 + i ei2 then, let's do the sum val1 + val2 if coherent: er3= er1 + er2 ei3 = ei1 + ei2 if incoherent: er3 = [val1val1* + val2val2*]^(-1/2) = [sum ( magnitude { val })] ei3 = 0 << this is where we put the imaginary part to 0, not in the individual contributing ei
Thank you for this repository, Yuan, it is excellent!
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.