Age | Commit message (Collapse) | Author |
|
|
|
|
|
There are no side-effects to setting it either way, and the caller can just set saturated=NULL
or ignore the result.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes a segfault
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This fixes a regression introduced by ad2c84d0, predating the initial CrystFEL release.
|
|
|
|
|
|
This fixes a speed regression introduced by dca1938a.
|
|
This REALLY fixes a significant data quality regression introduced by f668e3b3 (21st June 2012)
|
|
This fixes a significant data quality regression introduced by f668e3b3 (21st June 2012)
|
|
Also, s/ir_in/ir_inn/
|
|
This leads to a big improvement in speed when (ab)using max_adu for gaps in the detector.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit ae51e75490daf47e2deefe83e72a1f5c092fa023.
|
|
|
|
|
|
|
|
Saturated pixels seem to be OK during initial peak search
|
|
|
|
|
|
This should make it much more obvious (via check-near-bragg) when the peak positions are wrong.
|
|
|
|
|
|
|
|
|
|
|
|
I'm sure I've fixed this bug many times before...
|
|
|
|
|