Age | Commit message (Collapse) | Author |
|
|
|
This doesn't do anything. The very next lines override all the
settings.
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/64
|
|
If there are lots of error messages (e.g. a missing mask file), looking
at the last 4k of the log file is not always enough. Now it will go
back to 16k, in steps of 4k. It will stop early if it finds the start
of the file, and it will complain if it still doesn't find what it's
looking for.
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/61
|
|
|
|
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/59
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/58
|
|
|
|
This is no longer needed after 48c02e71e5bf. Simply set the correct
PATH before starting the GUI, and it will be propagated to the SLURM
jobs.
Astute readers will notice that the feature has been silently broken
since last March (65a1afdce2da5cd), anyway. Whoops.
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/56
|
|
Unfortunately, several environments rely on "magic" environment
variables to make things work. These need to be propagated.
The path to the GUI will no longer be added to the PATH. This was
intended to help when the indexing executables (mosflm, dirax etc) were
found alongside the CrystFEL executables. However, it's highly likely
that the path to the CrystFEL executables will be in PATH anyway.
This way, running the SLURM jobs in the same environment as the GUI
itself, also seems more compliant with the "principle of least
surprise".
|
|
|
|
When running online, there's no input file handle to close.
|
|
This avoids the process getting killed while waiting e.g. between runs
in an online context.
|
|
|
|
|
|
Usually, one will want this option enabled. However, sometimes it
speeds things up a lot to disable it.
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/54
|
|
Otherwise, setting the defaults won't work properly.
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/51
|
|
|
|
There's already some confusion between "loading a stream into the GUI"
and "adding a stream as a result". This should help resolve it, as well
as simplifying multi-stream results (coming up).
|
|
Requires that the array of crystals isn't allocated on the stack.
|
|
The csplit format is ambiguous when the filenames contain spaces. To
make things a bit clearer, the file now requires the fields to be
separated by exactly one space rather than any number of tabs/spaces.
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/55
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/17
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/18
|
|
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/52
|
|
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/28
|
|
When using the GUI, it will be set to the corresponding indexing result
name.
|
|
|
|
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/19
|
|
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/49
|
|
|
|
The variable-sized array can't have zero size, so we need to check.
|
|
|
|
|
|
|
|
|
|
It's not used anywhere, and in fact is freed before being passed in.
|
|
|
|
|
|
|
|
The previous cutoff of 0.2*reflection_separation seems to have been too
conservative. It cuts out over 1000 crystals from the 8000 crystals in
one of the regression tests. Examining the values shows that 0.5 is
better value. It's also a realistic physical limit - more than this,
and the reflections should be overlapping.
|
|
This changes how CrystFELImageView handles its adjustments for the
GtkScrollable interface, to match the GTK examples. In particular, it
adds a call to g_object_ref_sink() which prevents premature destruction
of the adjustments when the GUI is closed down.
|
|
|
|
|
|
|
|
|
|
|