Skip to content

Flipper efficiencies assumed to be scalar #84

Open
@jokasimr

Description

@jokasimr

The FlipperEfficiency.value member is a float, and it's assumed that it is a float when we use it here.

Is it physically correct that the flipper efficiency cannot depend on wavelength?

In the case of polarization correction for reflectometry that I'm currently working on this becomes a problem. The problem happens because the calibration step doesn't produce a flipper efficiency $f$ directly. Instead it produces two polarization efficiencies, called $P_{+}$ and $P_{-}$ one for each of the two flipper states, for the combined effect of the polarizing component and the associated flipper.

That is, instead of representing the polarization efficiency of the component using the two variables $P, f$ we use the two variables $P_{\pm}$.
In principle we can translate between the two different ways of viewing it, like this:

$$ P_{+} = P $$ $$ P_{-} = P(2f-1) $$

$$ \implies f = (P_{+} + P_{-}) / 2 P_{+} $$

$P_\pm$ are dependent on wavelength and potentially on detector pixel, and if we use the above expression to compute $f$ it will also depend on wavelength and detector pixel.

How to solve?

  • If it is the case that the flipper efficiency is independent of wavelength and other event coordinates then it might make sense to try to determine the flipper efficiency from $P_{\pm}$ averaging (in some way) $(P_{+} + P_{-}) / 2 P_{+}$ over wavelength and detector pixel. I've checked this with the IDS, the flipper efficiency can be wavelength dependent.
  • If it is reasonable that the flipper efficiency is wavelength dependent then we should change the code to reflect that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions