Jerome Kieffer

Hi Ray, thanks for the feed-back. It puzzles me that the bug is not reproducible ... First of all, the bug appears in a section of code which was changed...

Just a couple of comment, "no" pixel splitting is apparently better if one wants to perform Rietveld refinement according to Billinge: https://arxiv.org/pdf/1309.3614.pdf That said, most people prefer smoother curves. About...

I got the file, thanks, and it confirms that the bug in `dtth` i.e. the distance in 2theta from the pixel center to the corner. This explains not only why...

I tried this: ``` import pyFAI, numpy ai = pyFAI.AzimuthalIntegrator(0.640, detector="Pilatus2m", wavelength=0.142e-10) polarization = ai.polarization(factor=0.99) msk = ai.detector.mask res1 = ai.integrate1d(polarization, 2048, unit='2th_deg', mask=msk, correctSolidAngle=True, method=('bbox', 'csr', 'cython')) numpy.max(ai._cached_array.get('2th_corner', 0))...

I have one doubt : can you print the azimuthal integrator ? Is the detector actually a Pilatus or is it a Nexus-detecor ? If a file exist with the...

To correct this bug, the factor Σ ω² needs to be calculated which means changing the structure of every single rebinning engine and risks to jeopardize some performance optimization done...

1) Serialize the pyFAI.gui.model.CalibrationModel + composed objects. 2) restore are boot-up time Issue: what if the user provides a config online vs the last stored state

Well, pyFAI-calib (the CLI version, not the GUI) is not actively maintained and I consider removing it for pyFAI 1.0. In order to be able to debug, could you please...

needs further investigation ... I suspect the OS is a linux.

I can confirm the bug in a py3.9 venv on debian11