Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-07-30 | Eliminate duplicate symbols | Thomas White | |
This makes searching easier, and also permits Meson's unity build mode. | |||
2020-07-29 | Expose a couple more functions for easier testing | Thomas White | |
2020-07-29 | Convert a few more bits and pieces to detgeom | Thomas White | |
2020-07-29 | Convert make_BgMask to detgeom | Thomas White | |
2020-07-29 | Convert estimate_peak_resolution to detgeom | Thomas White | |
2020-07-29 | Split off parse_peaksearch() | Thomas White | |
2020-07-29 | Add str_peaksearch() | Thomas White | |
Will be needed for passing peak search parameters to indexamajig from GUI | |||
2020-07-29 | Convert peak detection to use detgeom | Thomas White | |
2020-07-29 | Remove badrow culling | Thomas White | |
Very old, not used at all, and better solved by masking bad regions. | |||
2020-07-29 | ImageFeatureList: Store panel number, not pointer | Thomas White | |
This makes the conversion to DataTemplate/detgeom MUCH easier. | |||
2020-01-10 | Mass update of copyright dates | Thomas White | |
2019-11-13 | Fix peak check logic for multiple crystals | Thomas White | |
It seems that the code wasn't properly updated when multi-crystal indexing was introducted. This "continue" statement didn't do anything. | |||
2019-09-06 | Use new peak check only when doing multi-lattice indexing | Thomas White | |
2019-09-06 | New check for indexing solutions (copied across from pinkIndexer) | Thomas White | |
2019-08-26 | Fix resolution estimation | Thomas White | |
Didn't work when the number of peaks was very low. | |||
2019-07-19 | peakFinder9: remove references to image.num_peaks etc | Thomas White | |
2019-05-14 | Remove image.num_peaks and num_saturated_peaks | Thomas White | |
These values were inconsistently set by different parts of the code, e.g. different peak search methods. num_saturated_peaks was even set during final integration. Now, the peak count is taken from the ImageFeatureList, so it's authoritative. | |||
2019-05-14 | Add documentation for search_peaks_peakfinder8 | Thomas White | |
2019-05-07 | Update all source code comments to Doxygen format | Thomas White | |
2019-03-06 | indexamajig: Rename --min-gradient to --min-squared-gradient | Thomas White | |
The eventual aim of this is to deprecate the "--min-gradient" option, resolving the long-standing confusion about whether this option is the gradient or the squared gradient. | |||
2018-06-10 | indexamajig: Estimate resolution based on peaks only | Thomas White | |
2018-05-30 | Changed sig_fac to min_snr | Yaroslav Gevorkov | |
2018-05-24 | Generalise peakfinder9 error messages, and fail if not compiled in | Thomas White | |
2018-05-24 | Move FDIP includes to top, and remove unnecessary ones | Thomas White | |
2018-05-24 | Update authorship and copyright dates | Thomas White | |
2018-05-24 | Formatting | Thomas White | |
2018-05-24 | Add "peakfinder9" | Yaroslav Gevorkov | |
2017-03-13 | Added saturated peak management to peakfinder8 | Valerio Mariani | |
2017-03-10 | Peakfinder8 in CrystFEL. Same results as Anton's Cheetah implementation | Valerio Mariani | |
2016-10-14 | validate_peaks(): Remove drifting and proximity checks, and use original ↵ | Thomas White | |
coordinates We trust the HDF5 peaks, even if we can't see a peak there. That means we can't reliably take a centroid and "improve" the coordinates. In some cases, the centroiding procedure seems to be making the peak coordinates worse than they were originally. Now, the only remaining checks are: 1. Is the peak in a bad region of the detector? 2. Is it saturated? (but --use-saturated is the default) 3. If --check-hdf5-snr, is it above the minimum SNR? | |||
2016-07-01 | No more slab-relative coordinates in libcrystfel | Thomas White | |
2016-05-19 | integrate_peak(): Trap if pk_total=0 | Thomas White | |
2016-04-01 | Add adu_per_photon (distinct from adu_per_eV) | Thomas White | |
2016-01-30 | Revert "Allow peak check to pass just by accounting for more than 5 peaks" | Thomas White | |
This reverts commit 693aae4d2219632d15174fe4c4f9d0526d6166c4. Reverting because this allows a very large number (~100% "indexing rate") of false solutions to get through simply by slackening the peak detection parameters. Since we know that "-multi" indexing doesn't work well at the moment, let's fix this properly later. | |||
2016-01-06 | search_peaks_in_panel(): Fix iteration bounds (again) | Thomas White | |
2015-12-18 | Allow peak check to pass just by accounting for more than 5 peaks | Thomas White | |
The "old" criterion is still allowed for a pass, but would filter out multi-lattice hits. | |||
2015-12-17 | Clean up unused code | Thomas White | |
2015-11-06 | Fix iteration bounds for peak search | Thomas White | |
It was out by one because of some leftover characters from the previous version. | |||
2015-10-06 | Fussiness | Thomas White | |
2015-10-05 | search_peaks() / integrate_peak(): Remove image->data | Thomas White | |
2014-09-22 | Beam file removal, part I | Thomas White | |
2014-09-02 | integrate_peak(): Revert use of image->dp | Thomas White | |
2014-08-13 | Remove old bad region tests and use dp instead of data for integration of peaks | Thomas White | |
2014-08-13 | Respect all bad pixels during peak detection | Thomas White | |
Not just no_index panels and bad regions | |||
2014-08-13 | Remove integrate_peak() from the API | Thomas White | |
Good riddance. One of my least favourite routines. | |||
2014-08-11 | Take overlaps into account during integration | Thomas White | |
2014-07-24 | Fixes closest feature detection bug | Valerio Mariani | |
2014-03-28 | validate_peaks(): Count saturated peaks only if they are being rejected | Thomas White | |
2014-03-28 | integrate_peak(): Useful return codes | Thomas White | |
2014-03-26 | indexamajig: Don't check SNR with --peaks=hdf5 unless given --check-hdf5-snr | Thomas White | |