Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
If it's needed, we'll replace it with a better piece of API (...which
doesn't abort the program in the event of a typo!)
|
|
It would've been difficult to calculate this in the new unified FoM API,
and the figure is completely useless anyway.
If you disagree with both of the above statements, please get in touch!
|
|
Reasons for differences:
1. Resolution shells slightly different
The binning calculation needs to take into account small rounding errors
in the resolution calculation, when not using an explicit resolution
range (--highres). The old version did this by taking a min/max
resolution range slightly larger than the resolution of the data. The
new version handles the rounding errors explicitly, so does not need
this.
2. Number of reflections with infinite/invalid I/sigI values halved
The number reported for this count was twice what it should have been,
due to a bug in the old check_hkl.
3. Overall SNR is different
When the above warning message applies, the old version still allowed
the reflections with invalid I/sigI values to contribute to the
denominator of the mean SNR calculation. The new version does not
include them in the SNR calculation at all. Note that the reflections
contribute to the other figures of merit unless otherwise stated.
4. Standard deviation of intensity is not calculated
It would've been a lot of work to include this in the new version, and
it's a totally useless number. If you disagree, please get in touch!
|
|
This solves a tricky conceptual issue: Stream owns the DataTemplate when
it's reading (because it came from the stream headers), but not when
writing (when it's provided to us).
|
|
This prevents an out-of-memory situation (due to ulimit) from
manifesting as a segfault.
|
|
|
|
|
|
|
|
No-one uses it, it doubles the complexity of the code, and the manual
even warns not to use it.
|
|
|
|
|
|
|
|
|
|
|
|
Bad regions are specified (in the geometry file) in terms of the "file"
coordinates, which might be different to the panel-relative ones.
|
|
|
|
Bad regions specified in terms of x/y still require an iteration over
all pixels of the detector, but I don't see an easy way around that.
Avoiding x/y bad regions will give best performance.
|
|
It's not used any more - nowhere is it set to 1.
|
|
|
|
|
|
|
|
Also flips the order of iteration for (negligibly) better performance
|
|
This avoids a load of trigonometric functions. In combination with the
new UnitCell representation caching, this gives a significant speedup
for cases where resolution() is called in a loop.
|
|
Previously, the "getter" functions would re-calculate the requested
representation every time they were called. This could mean doing a
matrix inversion in the middle of a tight loop, wasting loads of time.
Now, it stores the calculated values and returns them directly next
time. Setting the parameters invalidates the values for all
representations other than the one given.
The cost of doing this is that the cell can no longer be "const" in the
getter functions. This tracked through some other code, but nothing too
severe.
|
|
|
|
|
|
This test is meant to avoid integrating overlapping spots. It does a
very bad job of this, because it doesn't take into account whether
the neighbouring reflection is actually excited, or even allowed by the
lattice. It's even worse when we think about wide bandwidth.
|
|
|
|
|
|
The criterion for "too large" is 20% of the 1/d value for the lowest
reflection which is not systematically absent according to the
centering.
A profile radius larger than the 1/d value for a reflection will crash
the xsphere partiality model, and some visualisation shows that this is
a clearly non-physical situation. The profile radius shouldn't be
anywhere near the inter-Bragg spacing for reasonable data.
However, feedback shows that this is happening quite often in real data,
probably due to bad indexing.
|
|
|
|
|
|
This makes handling Pilatus/Eiger files, as well as many others, much
easier.
|
|
These needed to be kept up to date with a call to map_all_peaks every
time anything changed - wavelength, detector position etc. Not doing so
has already led to bugs in another branch, and probably already causes
problems on this branch.
This patch eliminates the rx,ry,rz completely. Anyone who needs
reciprocal space coordinates for a peak is now responsible for calling
detgeom_transform_coords themselves.
|
|
This is a hack, and should be replaced by something which gets the
metadata from the stream rather than hitting the read image file every
time.
|
|
|
|
|
|
I'm sick of fixing this same issue over and over again.
New rule: any code handling unit cell tolerances MUST be labelled with
details of units.
|
|
|
|
See 0f18ff76a3d1f5979db for some discussion.
|
|
|
|
|
|
This gives a huge speed improvement, without sacrificing very much in
indexing rate.
|
|
This reverts commit 62183aacf906f4aff771295aa378cff039dd50ff.
The apparent slowness was due to a bug introduced in August 2019.
See 2a8f415df845064186baa833f9fe1ad91c0f5753.
|
|
|