Hi Giulia,

You are missing a NSTR operand. Probably after you clear your detectors in operand 4.

Excerpt from the Help File (The Optimize Tab (sequential ui mode) > Automatic Optimization Group > Merit Function Editor (automatic optimization group) > Optimization Operands by Category > Non-sequential Ray Tracing and Detector Operands):

Did you actually generate this Merit Function with the Wizard?

Let me know if this helps.

Take care,

David

Hi Giulia,

No problem. Just to make sure I understand correctly. The Detector Viewer is zoomed in on a particular hot pixel, is that right? To me, it looks more like a spot where some rays were concentrated somehow. Is it possible to see the whole Detector?

One thing I can say from your Detector Viewer window is that your detector is 1000 x 1000 or 1 million pixels, and the number of hits is 977398, close to 1 million as well.

This means that you are probably undersampling your pixels in some regions of the Detector. Usually, I think Zemax recommends at least 100 hits per pixel, even better would be 1000 hits per pixels. One way to check if you have undersampling issues is to run consecutive raytraces and look at the Detector Viewer after each raytrace. If the image you see changes between raytraces, you probably want to increase the number of rays you trace, or try to minimize the losses during the raytrace. These are the rays that are launched from the source, but get lost in your system.

Does that make sense?

Take care,

David

Hi Giulia,

You are right, I could have noticed it from your screenshot as well. From the 1 million ray you trace, only a few get lost on the way. But this doesn’t change the fact that on average you have 1 ray per pixel. We can see from your image that most pixels don’t recieve any energy. The two things that would be interesting to know is where the rays land, and what density of rays per pixel you achieve in those regions. As I said before, I would try to have at least 100 rays per pixels. The other thing to try is what happens to your “hot spots” when you run consecutive raytraces? Are they always in the same location?

Take care,

David

Dear Giulia,

The 100 rays per pixel is a rule of thumb. It does not apply universally, but is a good starting point.

I think I didn’t explain what I meant carefully. Let me show you what I had in mind with an example (also attached to my post).

I’ve used a Source Gaussian that I shine onto a 100 x 100 Detector Rectangle, and I’m manually increasing the number of rays from 100 to 1000000.

Since the rays are drawn randomly from a Gaussian distribution I need to make sure I draw enough of these rays to get an accurate representation of my source. As you can see in my screenshot above, with 100 rays it is clearly not enough. To me, only after 100000 rays do I get a representation I’m satisfied with. This would be 10 rays per pixel. In this particular case, I needed less than the 100 rays per pixels but it is also because everything is relatively “smooth”. My source doesn’t fall onto an object with a high density of features, such as a Fresnel lens. The point is, I’m not sure if it is what is causing your hot spots, but you definitely want to check your sampling (how many rays per pixels).

For that purpose, I would suggest to manually run a couple of raytraces, and just check how the detector viewer looks like. Does it changes a lot between raytraces? You don’t really need the API to do that. You could open two detector viewers, run a raytrace, lock one of the detector viewers (using the “Lock” icon), then run a second raytrace. How do the images look like? Are the hot pixels in the same location?

Let me know if this makes sense.

Take care,

David

Hi Giulia,

Sorry, I think I was confused. The hot spot you are talking about is only the bright spot in the center of your detector, is that right?

I think it is just the Fresnel lens focusing the rays according to your Merit Function. Nothing to worry aobut, I think this is correct indeed.

Take care,

David