You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the objective best pixel splitting should be NO pixel splitting at all (see Billinge's paper), many early adopter of pyFAI promoted some kind of pixel-splitting to avoid the Moiré pattern, especially in 2D integration.
I believe the full pixel splitting is production ready for at least 5 years, does it make sense to make it the default option (other pixel splitting are still available with a kwarg: method)
What should be the **default** pixel splitting in pyFAI ?
No pixel splitting: it is fast and correct, I can live with the Moiré pattern.
0%
BBox pixel splitting: it has been like this for 15 years, don't break working things.
11%
Full pixel splitting: it is the perfect balance between the two other and it is validated for several years now
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
While the objective best pixel splitting should be NO pixel splitting at all (see Billinge's paper), many early adopter of pyFAI promoted some kind of pixel-splitting to avoid the Moiré pattern, especially in 2D integration.
I believe the full pixel splitting is production ready for at least 5 years, does it make sense to make it the default option (other pixel splitting are still available with a kwarg:
method)9 votes ·
Beta Was this translation helpful? Give feedback.
All reactions