Chromatogram peak detection - bunching vs others?











up vote
3
down vote

favorite
1












Reading presentations from existing tool providers I noticed that in order to detect peaks they first use bunching (average N points) and then use slope and curvature to detect peaks. I'm guessing they use bunching to get rid of high-frequency noise.



Aren't there better alternatives like removing high frequencies with FT? I'm concerned that bunching requires peak width to be known to define Bunching Factor. Which means we first need to detect peak width in some other way before using curvature. But I've seen more than 1 presentation talking about bunching, so there have to be reasons to use this approach instead of others.










share|improve this question






















  • Several chromatogram signals are made of three components: peaks (potentially merged), drift or baseline, and random stuff. Do you wish to qualify or quantify peaks? Any hints about peak width and noise?
    – Laurent Duval
    Dec 2 at 18:02










  • I'd like to determine peak beginning/end and its area. I'm building a generic tool to process LCMS, thus there could be baseline drifts and different levels of noise. Need to automatically tag peaks within EIC and (maybe) TIC.
    – Stanislav Bashkyrtsev
    Dec 2 at 18:27












  • Only 1D in a separable way? Any bound on peak width?
    – Laurent Duval
    Dec 2 at 19:23










  • Only 1D, yes. No particular bounds on peak widths. Though I haven't seen peaks as wide as 30 seconds yet. But I assume they may exist if LC method is not selected properly.
    – Stanislav Bashkyrtsev
    Dec 3 at 6:54

















up vote
3
down vote

favorite
1












Reading presentations from existing tool providers I noticed that in order to detect peaks they first use bunching (average N points) and then use slope and curvature to detect peaks. I'm guessing they use bunching to get rid of high-frequency noise.



Aren't there better alternatives like removing high frequencies with FT? I'm concerned that bunching requires peak width to be known to define Bunching Factor. Which means we first need to detect peak width in some other way before using curvature. But I've seen more than 1 presentation talking about bunching, so there have to be reasons to use this approach instead of others.










share|improve this question






















  • Several chromatogram signals are made of three components: peaks (potentially merged), drift or baseline, and random stuff. Do you wish to qualify or quantify peaks? Any hints about peak width and noise?
    – Laurent Duval
    Dec 2 at 18:02










  • I'd like to determine peak beginning/end and its area. I'm building a generic tool to process LCMS, thus there could be baseline drifts and different levels of noise. Need to automatically tag peaks within EIC and (maybe) TIC.
    – Stanislav Bashkyrtsev
    Dec 2 at 18:27












  • Only 1D in a separable way? Any bound on peak width?
    – Laurent Duval
    Dec 2 at 19:23










  • Only 1D, yes. No particular bounds on peak widths. Though I haven't seen peaks as wide as 30 seconds yet. But I assume they may exist if LC method is not selected properly.
    – Stanislav Bashkyrtsev
    Dec 3 at 6:54















up vote
3
down vote

favorite
1









up vote
3
down vote

favorite
1






1





Reading presentations from existing tool providers I noticed that in order to detect peaks they first use bunching (average N points) and then use slope and curvature to detect peaks. I'm guessing they use bunching to get rid of high-frequency noise.



Aren't there better alternatives like removing high frequencies with FT? I'm concerned that bunching requires peak width to be known to define Bunching Factor. Which means we first need to detect peak width in some other way before using curvature. But I've seen more than 1 presentation talking about bunching, so there have to be reasons to use this approach instead of others.










share|improve this question













Reading presentations from existing tool providers I noticed that in order to detect peaks they first use bunching (average N points) and then use slope and curvature to detect peaks. I'm guessing they use bunching to get rid of high-frequency noise.



Aren't there better alternatives like removing high frequencies with FT? I'm concerned that bunching requires peak width to be known to define Bunching Factor. Which means we first need to detect peak width in some other way before using curvature. But I've seen more than 1 presentation talking about bunching, so there have to be reasons to use this approach instead of others.







smoothing peak-detection






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 2 at 14:09









Stanislav Bashkyrtsev

1184




1184












  • Several chromatogram signals are made of three components: peaks (potentially merged), drift or baseline, and random stuff. Do you wish to qualify or quantify peaks? Any hints about peak width and noise?
    – Laurent Duval
    Dec 2 at 18:02










  • I'd like to determine peak beginning/end and its area. I'm building a generic tool to process LCMS, thus there could be baseline drifts and different levels of noise. Need to automatically tag peaks within EIC and (maybe) TIC.
    – Stanislav Bashkyrtsev
    Dec 2 at 18:27












  • Only 1D in a separable way? Any bound on peak width?
    – Laurent Duval
    Dec 2 at 19:23










  • Only 1D, yes. No particular bounds on peak widths. Though I haven't seen peaks as wide as 30 seconds yet. But I assume they may exist if LC method is not selected properly.
    – Stanislav Bashkyrtsev
    Dec 3 at 6:54




















  • Several chromatogram signals are made of three components: peaks (potentially merged), drift or baseline, and random stuff. Do you wish to qualify or quantify peaks? Any hints about peak width and noise?
    – Laurent Duval
    Dec 2 at 18:02










  • I'd like to determine peak beginning/end and its area. I'm building a generic tool to process LCMS, thus there could be baseline drifts and different levels of noise. Need to automatically tag peaks within EIC and (maybe) TIC.
    – Stanislav Bashkyrtsev
    Dec 2 at 18:27












  • Only 1D in a separable way? Any bound on peak width?
    – Laurent Duval
    Dec 2 at 19:23










  • Only 1D, yes. No particular bounds on peak widths. Though I haven't seen peaks as wide as 30 seconds yet. But I assume they may exist if LC method is not selected properly.
    – Stanislav Bashkyrtsev
    Dec 3 at 6:54


















Several chromatogram signals are made of three components: peaks (potentially merged), drift or baseline, and random stuff. Do you wish to qualify or quantify peaks? Any hints about peak width and noise?
– Laurent Duval
Dec 2 at 18:02




Several chromatogram signals are made of three components: peaks (potentially merged), drift or baseline, and random stuff. Do you wish to qualify or quantify peaks? Any hints about peak width and noise?
– Laurent Duval
Dec 2 at 18:02












I'd like to determine peak beginning/end and its area. I'm building a generic tool to process LCMS, thus there could be baseline drifts and different levels of noise. Need to automatically tag peaks within EIC and (maybe) TIC.
– Stanislav Bashkyrtsev
Dec 2 at 18:27






I'd like to determine peak beginning/end and its area. I'm building a generic tool to process LCMS, thus there could be baseline drifts and different levels of noise. Need to automatically tag peaks within EIC and (maybe) TIC.
– Stanislav Bashkyrtsev
Dec 2 at 18:27














Only 1D in a separable way? Any bound on peak width?
– Laurent Duval
Dec 2 at 19:23




Only 1D in a separable way? Any bound on peak width?
– Laurent Duval
Dec 2 at 19:23












Only 1D, yes. No particular bounds on peak widths. Though I haven't seen peaks as wide as 30 seconds yet. But I assume they may exist if LC method is not selected properly.
– Stanislav Bashkyrtsev
Dec 3 at 6:54






Only 1D, yes. No particular bounds on peak widths. Though I haven't seen peaks as wide as 30 seconds yet. But I assume they may exist if LC method is not selected properly.
– Stanislav Bashkyrtsev
Dec 3 at 6:54












1 Answer
1






active

oldest

votes

















up vote
2
down vote













peak(s) determination tends to be application specific. There are many heuristics and one usually needs to try and test a lot.



It helps a lot if there is a reliable statistical model for your data.



One trick is to note that peak is larger than its adjacent neighbors. Peaks on boundaries can be determined by reflection.



Another issue is the set that you are finding peaks on. Some data consists of multiple scans that can be averaged to reduce noise. One can also do what you refer to as bunching and bunching has numerous variations such as summing, weighted summing, taking a median and combinations.



Another concern may be strong peaks bleeding into weak peaks or masking them entirely. Many applications have this bin bias problem and there are ways to approach that which are beyond what can be answered in a simple answer given here.



One can also use thresholds to isolate peaks and again that has many variations.



Usually, a community has conventions on how to approach problems like finding peaks and there is probably some documents that constitute a standard. You might want to look for those.






share|improve this answer























    Your Answer





    StackExchange.ifUsing("editor", function () {
    return StackExchange.using("mathjaxEditing", function () {
    StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
    StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
    });
    });
    }, "mathjax-editing");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "295"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    noCode: true, onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdsp.stackexchange.com%2fquestions%2f53853%2fchromatogram-peak-detection-bunching-vs-others%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    peak(s) determination tends to be application specific. There are many heuristics and one usually needs to try and test a lot.



    It helps a lot if there is a reliable statistical model for your data.



    One trick is to note that peak is larger than its adjacent neighbors. Peaks on boundaries can be determined by reflection.



    Another issue is the set that you are finding peaks on. Some data consists of multiple scans that can be averaged to reduce noise. One can also do what you refer to as bunching and bunching has numerous variations such as summing, weighted summing, taking a median and combinations.



    Another concern may be strong peaks bleeding into weak peaks or masking them entirely. Many applications have this bin bias problem and there are ways to approach that which are beyond what can be answered in a simple answer given here.



    One can also use thresholds to isolate peaks and again that has many variations.



    Usually, a community has conventions on how to approach problems like finding peaks and there is probably some documents that constitute a standard. You might want to look for those.






    share|improve this answer



























      up vote
      2
      down vote













      peak(s) determination tends to be application specific. There are many heuristics and one usually needs to try and test a lot.



      It helps a lot if there is a reliable statistical model for your data.



      One trick is to note that peak is larger than its adjacent neighbors. Peaks on boundaries can be determined by reflection.



      Another issue is the set that you are finding peaks on. Some data consists of multiple scans that can be averaged to reduce noise. One can also do what you refer to as bunching and bunching has numerous variations such as summing, weighted summing, taking a median and combinations.



      Another concern may be strong peaks bleeding into weak peaks or masking them entirely. Many applications have this bin bias problem and there are ways to approach that which are beyond what can be answered in a simple answer given here.



      One can also use thresholds to isolate peaks and again that has many variations.



      Usually, a community has conventions on how to approach problems like finding peaks and there is probably some documents that constitute a standard. You might want to look for those.






      share|improve this answer

























        up vote
        2
        down vote










        up vote
        2
        down vote









        peak(s) determination tends to be application specific. There are many heuristics and one usually needs to try and test a lot.



        It helps a lot if there is a reliable statistical model for your data.



        One trick is to note that peak is larger than its adjacent neighbors. Peaks on boundaries can be determined by reflection.



        Another issue is the set that you are finding peaks on. Some data consists of multiple scans that can be averaged to reduce noise. One can also do what you refer to as bunching and bunching has numerous variations such as summing, weighted summing, taking a median and combinations.



        Another concern may be strong peaks bleeding into weak peaks or masking them entirely. Many applications have this bin bias problem and there are ways to approach that which are beyond what can be answered in a simple answer given here.



        One can also use thresholds to isolate peaks and again that has many variations.



        Usually, a community has conventions on how to approach problems like finding peaks and there is probably some documents that constitute a standard. You might want to look for those.






        share|improve this answer














        peak(s) determination tends to be application specific. There are many heuristics and one usually needs to try and test a lot.



        It helps a lot if there is a reliable statistical model for your data.



        One trick is to note that peak is larger than its adjacent neighbors. Peaks on boundaries can be determined by reflection.



        Another issue is the set that you are finding peaks on. Some data consists of multiple scans that can be averaged to reduce noise. One can also do what you refer to as bunching and bunching has numerous variations such as summing, weighted summing, taking a median and combinations.



        Another concern may be strong peaks bleeding into weak peaks or masking them entirely. Many applications have this bin bias problem and there are ways to approach that which are beyond what can be answered in a simple answer given here.



        One can also use thresholds to isolate peaks and again that has many variations.



        Usually, a community has conventions on how to approach problems like finding peaks and there is probably some documents that constitute a standard. You might want to look for those.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 2 at 18:48

























        answered Dec 2 at 14:42









        Stanley Pawlukiewicz

        5,9332421




        5,9332421






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Signal Processing Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            Use MathJax to format equations. MathJax reference.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdsp.stackexchange.com%2fquestions%2f53853%2fchromatogram-peak-detection-bunching-vs-others%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Probability when a professor distributes a quiz and homework assignment to a class of n students.

            Aardman Animations

            Are they similar matrix