Age | Commit message (Collapse) | Author |
|
If the geometry file contains a literal wavelength, then let's use it.
That's better than nagging the user for a --wavelength-estimate.
|
|
|
|
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.
|
|
|
|
...and factorise common code
|
|
Same reason as removing them from tests. Also, libcrystfel might be
used in projects which have HAVE_CONFIG_H defined.
|
|
|
|
Regarding check_path_existence: This was a very complicated procedure,
for not very much gain. The attempt to open a dataset for real, which
invariably follows, can still fail after this check.
|
|
|
|
NB The coffset is no longer written to the HDF5 file. This was a
terrible hack anyway. The resolution field is just as bad, but as least
easy to get from the detgeom.
|
|
|
|
The only place this is used is in geoptimiser, to get the
average_camera_length, itself a very bad solution.
|
|
|
|
|