Age | Commit message (Collapse) | Author |
|
There are still some rough edges, e.g. it only works with a simple
I/SIGI column (not I+/I-), and can't yet interpret the symmetry
information in the file. However, it's still better than the old
mtz2hkl script.
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/7
|
|
|
|
The containers have all the development package dependencies and tools preinstalled to save
time and network bandwidth in the Fedora 32 & 37 and Centos7 jobs.
|
|
|
|
This also reduces the default timeout to 500 ms.
|
|
|
|
Example: group_all = q0,q1,q2,q2
|
|
|
|
|
|
Previously, this file ended up in man1, where it couldn't be found.
|
|
Unfortunately, V04-14-00 cannot be compiled with older Meson versions
(which we otherwise support) - they apparent confuse the old version of
the Fortran dependency scanner with use of #ifdef.
There's not currently much for us to gain from a more recent Millepede
version, so this is the easiest solution.
|
|
This allows the user to re-run any job, if they want, or at least easily
use the GUI's work as a template.
|
|
Closes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/87
|
|
|
|
Lots of things can go wrong here, in which case it falls back to the
shell search path.
|
|
We noticed that constant freeing and re-allocating the (potentially
quite large) arrays resulted in much lower performance. Since we know
that all images have the same data layout, we can safely re-use the
arrays. This gives a large speedup.
|
|
The saturation array is created by create_satmap when needed, which
takes care that all panels get an array (so we only have to check
image->sat != NULL). The array created by image_create_dp_bad_sat was
actually leaked!
In any case, saturation maps are rarely used. We can do without the
extra allocations.
The routine name has been changed accordingly, to prevent future
confusion.
|
|
|
|
The "children" array was the wrong size, and not freed. Also, some
formatting fussiness.
|
|
|
|
With the prefix, it can get quite long.
|
|
|
|
Still some work to be done here, but it's already an improvement.
|
|
We'd like the manual pages to be built for the central deployment.
|
|
|
|
|
|
|
|
These are now ignored, but shouldn't be in the examples.
|
|
These should be get_exerr. Following 1ae9a4582, the r_dev values are no
longer useful physical quantities, only a refinement target function.
This was causing the last few Git versions to not predict any
reflections at all!
|
|
|
|
The variable isn't needed, and just serves to break the build when
Fortran isn't available.
|
|
The restraint was way too strong, after the last round of tweaking.
With a weaker restraint, the algorithm converges very quickly - it's
practically linear - so ten iterations is way too much.
|
|
|
|
|
|
This should help avoid confusion when people find they need a Fortran
compiler.
|
|
This avoids weird weighting factors everywhere and much confusion.
Since Millepede doesn't have an easy way of weighting measurements (only
via altering the ESD values), treating it as a units conversion seems to
be easier.
|
|
We want the residual in pixels, as described in the comment for
EXC_WEIGHT.
This routine is only used for displaying the total residuals, not for
the real minimisation maths. However, we need to be clear.
|
|
We explicitly want the gradient of the residual, nothing else.
|
|
|
|
Needed for Millepede
|
|
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/3
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/29
|
|
|
|
Fixes: https://gitlab.desy.de/thomas.white/crystfel/-/issues/85
|
|
|
|
|
|
|
|
|
|
Should always be a right-hand grip rotation around positive axis
direction.
|
|
|