Conversation
Collaborator
Author
|
Currently, peakBoundary() only considers the tallest (most intense) peak. It finds the global maximum intensity and walks outward from that single apex. So it is not appropriate for peakpicking. it is more to get "cleaner" boundaries after receiving info of chrompeak range from other softwares. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here i add a function do determine left and right boundary.
it is not added as a backend method as peakBoundary() is a read-only summary — it computes a result (a matrix) from the peaks data but doesn't transform or modify the data itself. Backend methods exist to store, retrieve, or transform data (like peaksData(), intensity(), imputePeaksData()). Since peakBoundary() just reads peaksData() and derives boundaries, it belongs at the Chromatograms level only.