| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
When there is only one panel, we can safely assume that fs/ss bad
regions refer to it without it being stated in the geometry file.
This allows some older Pilatus geometry files to be used without
complaints.
A further improvement would be to determine the panel when all the data
comes from one "slab" so the panel is still ambiguous. However, on
further thought it seems like a lot of work to do this reliably in all
cases. I'm not even sure that this case in particular is causing anyone
problems.
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/32
|
|
Apparently, I can't count.
|
|
|
|
Previously, they would not get scanned because no job was running. We
need one more scan after a job exits to make sure everything is up to
date.
|
|
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/13
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/12
|
|
|
|
A silly cut+paste error.
|
|
The logic behind forcing the results selector (to "Calculations within
GUI") was that anything calculated in the GUI should appear under that
selection only.
Unfortunately, when loading a stream without images, there is nothing at
all to be seen under this selection, not even an image. Forcing the
selector resulted in proj->cur_image = NULL and therefore a crash when
trying to index based on that.
Similarly, the call to update_peaks expected image data, but there is
none. In reality, we have a perfectly good image structure with peaks
from the stream already.
This allows a non-image stream to be "re-indexed" based on the peaks.
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/33
|
|
|
|
|
|
|
|
|
|
If this happens once, it'll probably happen every frame. This makes
things very noisy.
|
|
|
|
This will help to avoid mistakes when people put statements at the end
of the geometry file, rather than the top.
Closes https://gitlab.desy.de/thomas.white/crystfel/-/issues/20.
|
|
|
|
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 code hasn't been looked at for a very long time, and can be made a
bit faster by iterating in a more cache-friendly way.
|
|
|
|
The unique filename is needed by the GUI for looking up results in a
stream. Otherwise, the filename is "(null)" for everything and the
lookup just returns the first chunk in the stream.
The filename is generated based on the unique serial number for each
chunk, and is therefore unique across one run of indexamajig regardless
of the number of worker processes (-j). This might have to change in future
to accommodate jobs run across multiple nodes, if there is any demand
for looking at results in one big concatenated stream.
This also changes the condition for deciding when to look for a 'real'
file, to take into account that there is always a non-NULL filename.
|
|
|
|
|
|
This is a hack to filter out what seems like "keepalive" messages. It's
nasty, but better than contaminating the stream with spurious chunks.
|
|
The changes in b22f6f524 were incorrect. config.h should never be
included from libcrystfel headers, because that will include the main
CrystFEL program config.h instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This removes some unnecessary work (getting the address from the file)
and seems cleaner.
|
|
|
|
It's not used anywhere.
|
|
|
|
|
|
|
|
|
|
|
