Generic multilayer (optical element)

[rafaelcelestre]

When trying to implement a toroidal ML mirror, I have the following error:

('OWMultilayer' object has no attribute 'toroidal_multilayer_pole_location')

The idea is to approximate the plane mirror by a torus with radii taken from metrology data.

Note: I cannot plug the MLayer reflectivity directly into an existing optic, like we did in S3.

[srio]

Thanks for reporting this bug. It is fixed.

(It was due that the variable f_torus in S4 is referred in the gui as toroidal_mirror_pole_location. Unfortunately it contains "mirror" even if is shared by crystals, multilayers, etc. I cannot change that because it will affect the existing workspaces. I fixed the call in multilayer giui).

Note: I cannot plug the MLayer reflectivity directly into an existing optic, like we did in S3.

Not in multilayers. However, you can do it in mirrors, and you can enter a multilayer reflectivity. There is no way to identify the kind of external reflectivity you are input so you can saftely use the mirror instead the multilayer.

May be I can copy this functionality of mirrors into multilayers?

[rafaelcelestre]

So, I find it quite useful to have the preprocessor connected to the optical element widget in order to visually remind me what is being done.

Copying the behavior we have for mirrors (blue arrows) in S4 to ML (red arrows) would be nice:

---

Good tip @ reflectivity from multilayers in OE/basic settings/reflectivity. This raises a question, then: why in S4 the ML mirror is a separate entity?

[srio]

Yes. It makes sense. I reopen the issue and I will do is asap.