Age | Commit message (Collapse) | Author |
|
On some systems, this conflicts with DST_NONE in sys/time.h.
|
|
In this case, return false because PinkIndexer is never in the list of
automatically-chosen indexers.
|
|
Not needed any more.
|
|
This requires changing all the paths to relative ones.
Previously, the jobs ran with their CWDs set to the corresponding
"result" folder. The trouble is, this breaks everything that uses a
relative location: image filenames, mask/satmap files referenced by the
geometry, etc.
Note that this change also means that the temporary folders
("indexamajig.XXX") are now produced in the top-level working directory.
Eventually, a GUI option should be added to allow these folders to be
put somewhere better (i.e. somewhere fast).
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/44
|
|
|
|
|
|
|
|
Just like the individual indexing methods, these aren't part of the API.
peakfinder8.h was there twice, for some reason.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Making them opaque seemed like a nice idea, because all the indexers
could take care of their own command-line arguments. However, it
doesn't work at all when indexing is run via the API.
|
|
|
|
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/41
|
|
|
|
Only when using PinkIndexer.
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/25
|
|
|
|
Rationale: Although the format has technically changed, CrystFEL 0.9.1
and older do not read the "hdf5/" lines anyway. The new "header" lines
are just noise, as far as they are concerned. However, increasing the
version number causes older CrystFEL versions to reject streams written
by newer CrystFEL versions. This is inconvenient, but will be a
particular problem since CrystFEL 0.10.0 will most likely be released
without a working "geoptimiser". We therefore need to be able to use
older CrystFEL versions for refining geometry. Older versions are
perfectly capable of reading newer streams.
In general, the semantics of stream version numbers are a bit messed up,
and we need to work out what they really mean.
This reverts commit fdce01adf9fc5950904b644ea755760cb32ec5b2.
|
|
The format for storing headers has changed from hdf5/location to
header/type/location.
|
|
The old way of recording metadata in the stream unfortunately doesn't
include any information about the data type. Most of the time, floating
point is what's intended. Older CrystFEL doesn't know about integer
headers at all, but there might be string values if --copy-hdf5-field
was used.
By interpreting "hdf5/something = val" as floating-point, most things
will work, e.g. camera length from HDF5 header enabling stream to be
loaded without access to the image data. Anything that can't be
interpreted as floating-point will be noisily ignored when loading the
stream.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Better understanding of the fPIC problem.
|
|
|
|
Meson's internal HDF5 search should work in all cases since 0.50.0,
subject to issues documented in INSTALL.md.
|
|
|
|
The problem is, '(null)' is not NULL.
|
|
|
|
This makes it consistent with all the other windows.
|
|
|
|
|
|
They need to be prefixed with "../" because they are in a different
folder.
|
|
I find that starting to show centres at a higher magnification level
makes it easier to distinguish the centre markers from bright pixels.
|
|
|
|
Smaller numbers of crystals are more common, so it's better for the
second crystal to be something very distinct from the peak search
colour.
|
|
|
|
|
|
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/36
|
|
|
|
|
|
|
|
|