Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
This is only really needed for offline processing. It's an added
complication for now. Maybe we'll revisit it later and re-expose this,
though.
|
|
|
|
|
|
|
|
|
|
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/68
|
|
|
|
|
|
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.
|
|
Rationale: it makes the JSON structure a bit more logical, and enables
things like the following:
set_of_params_1.integration.radii == set_of_params_2.integration.radii
params.peaksearch.radii == params.integration.radii
Previously, these would have required multiple comparisons.
|
|
This (re-)adds the ability to get data via a request/reply socket.
See afcb7b568947c for when it was removed.
|
|
This fixes --threshold when --zmq-subscribe is used.
|
|
|
|
|
|
|
|
This removes some unnecessary work (getting the address from the file)
and seems cleaner.
|
|
|
|
It's not used anywhere.
|
|
|
|
|
|
|
|
This will avoid multiple indexamajig processes from overwriting the
others' files when running a batch job.
|
|
|
|
Unfortunately, PinkIndexer needs the real camera length for its centre
refinement. Giving a fake value and scaling the resulting shift does
not work - the indexing rate drops with even a small error.
Ideally, this would work in the same way as --wavelength-estimate, by
using a static value from the geometry file if it's given. However,
this is rather complicated to implement because of the way all the units
stuff is implemented. Therefore, this is left as an improvement for the
future.
|
|
This give FromFile its own private command-lien option processing, like
the other indexers. It removes the ability to auto-generate the
solution filename, but I don't think there's a way to do that without
breaking abstractions.
|
|
|
|
|
|
If the geometry file contains a literal wavelength, then let's use it.
That's better than nagging the user for a --wavelength-estimate.
|
|
This is a more general replacement for --pinkIndexer-thread-count.
|
|
Spectrum file is currently not supported at all. Maybe later.
|
|
These conflict badly with CrystFEL's own checks, creating a horrible
user and developer experience.
Later, if we want to handle wide bandwidth beams, we will improve the
central CrystFEL checks to support it.
|
|
There is absolutely nothing useful that an indexing algorithm can do
with the opaque DataTemplate object.
|
|
This is a more sensible non-indexer-specific and non-Xray-specific
replacement for --pinkIndexer-override-photon-energy
|
|
|
|
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.
|
|
This option is no longer used, and generates a warning. The peak
location comes in the geometry file instead.
|
|
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.
|