Description
Based off of discussion here #315 and the request to create a separate feature request post.
Without the use of grouping + fillChromPeaks()
, a simple + integrated way to perform a targeted second pass of peak detection for missed peaks with the ability to merge this with the initial object (containing peaks from first pass of detection) might be useful new functionality into the xcms ecosystem.
Perhaps for the CentWave algorithm, this would involve building off of the functionality for pre-defining ROI? An example use case for our research group would be if CentWave identified 95%+ of high quality peaks, then to use this functionality as a means to go back and reincorporate features that were clearly missed at the discretion of the graduate student. (Fine tuning CentWave params got us so far but not 100% of the way!)
Hope that is clear/makes sense. My developer skills are weak/non-existent but please let me know how I can contribute if needed!