Age | Commit message (Collapse) | Author |
|
|
|
A little clearer than fftw_malloc(*sizeof)
|
|
This is only needed to reset FFTW to a "pristine" state, which is not
required here, and possibly even detrimental.
|
|
We don't need to fish out the arrays and use FFTW's "new array
execution" functions: http://fftw.org/fftw3_doc/New_002darray-Execute-Functions.html
|
|
|
|
Previously, it was possible for the search to run over the part of the
array initialised by FFTW.
|
|
Co-authored-by: Alexandra Tolstikova <alexandra.tolstikova@desy.de>
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/76
|
|
This adds an optional fast mode for asdf indexing, which is around 3
times faster with only a few percent lower success rate.
|
|
|
|
'changed' is initialised to zero, so there's no way this check can fail.
|
|
|
|
|
|
This removes the big potential for confusion, which has happened several
times (see e.g. 095cbebaf6). It also fixes in-tree builds with CMake
(but seriously, always use out-of-tree builds).
Fixes #2.
|
|
This allows the refined detector position to be used in a lot of places.
|
|
|
|
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.
|
|
|
|
|
|
|