| Age | Commit message (Collapse) | Author |
|---|
|
These flags weren't orthogonal at all, which was turning some routines
into spaghetti-code.
It's still possible to avoid read/write of peak lists, reflection data
or image data. But that's it.
|
|
It makes no sense for a different DataTemplate to be used for every
frame in a stream. And this way makes everything much easier for users
ot the API.
|
|
|
|
|
|
Also, this fixes some incorrect headers and adds --version flags to
programs which didn't yet have them.
|
|
The only place this is used is in geoptimiser, to get the
average_camera_length, itself a very bad solution.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These values were inconsistently set by different parts of the code,
e.g. different peak search methods. num_saturated_peaks was even set
during final integration. Now, the peak count is taken from the
ImageFeatureList, so it's authoritative.
|
|
spectrum.
|
|
|
|
This will need a separate way to create the official releases
(which shouldn't have Git revisions attached)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
groups
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
