aboutsummaryrefslogtreecommitdiff
path: root/libcrystfel/src/fom.c
AgeCommit message (Collapse)Author
2024-02-06Use libcrystfel memory allocation routines everywhereThomas White
2021-09-07fom_select_reflection_pairs: Keep zeroed intensities in datasetThomas White
Note the re-ordering of tasks, and the removal of 'continue'.
2021-09-07init_fom: Clean up on error pathThomas White
2021-07-21Make sure that memory gets freed on realloc failureThomas White
2021-07-21Add missing cleanup on error pathsThomas White
2021-04-27Rename libcrystfel's config.h to libcrystfel-config.hThomas White
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.
2021-02-09Add fom_is_comparison()Thomas White
2021-02-08Add fom_name()Thomas White
2021-02-08Expose fom_is_anomalous()Thomas White
2021-02-05Documentation for new FoM APIThomas White
2021-02-05Move fom_type_from_string out of APIThomas White
If it's needed, we'll replace it with a better piece of API (...which doesn't abort the program in the event of a typo!)
2021-02-05check_hkl: Remove standard deviation of intensityThomas White
It would've been difficult to calculate this in the new unified FoM API, and the figure is completely useless anyway. If you disagree with both of the above statements, please get in touch!
2021-02-05check_hkl: Move "single-list" FoMs into APIThomas White
Reasons for differences: 1. Resolution shells slightly different The binning calculation needs to take into account small rounding errors in the resolution calculation, when not using an explicit resolution range (--highres). The old version did this by taking a min/max resolution range slightly larger than the resolution of the data. The new version handles the rounding errors explicitly, so does not need this. 2. Number of reflections with infinite/invalid I/sigI values halved The number reported for this count was twice what it should have been, due to a bug in the old check_hkl. 3. Overall SNR is different When the above warning message applies, the old version still allowed the reflections with invalid I/sigI values to contribute to the denominator of the mean SNR calculation. The new version does not include them in the SNR calculation at all. Note that the reflections contribute to the other figures of merit unless otherwise stated. 4. Standard deviation of intensity is not calculated It would've been a lot of work to include this in the new version, and it's a totally useless number. If you disagree, please get in touch!
2021-01-22compare_hkl: Remove --intensity-shellsThomas White
No-one uses it, it doubles the complexity of the code, and the manual even warns not to use it.
2021-01-22Remove selection of reflections for FoM to libcrystfelThomas White
2021-01-22Improve names for FoM APIThomas White
2021-01-22Move figure of merit calculation into libcrystfelThomas White