Closed rmflight closed 2 years ago
This approach may have a problem with estimates of variance in SMIRFE.
On Thu, Mar 10, 2022 at 10:17 PM Robert M Flight @.***> wrote:
I had this idea long ago, but completely forgot until now.
To assign peak data that does not intrinsically have scan level data (i.e. the XCaliber data) we can create a fake scan level that just has 20 scans of identical peak information.
This should let it be assigned by SMIRFE.
— Reply to this email directly, view it on GitHub https://github.com/MoseleyBioinformaticsLab/manuscript.peakCharacterization/issues/8, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADEP7B7LM4MQYNLSTAINWHDU7K3L5ANCNFSM5QOOBVPA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: <MoseleyBioinformaticsLab/manuscript.peakCharacterization/issues/8@ github.com>
Email: @. (work) @. (personal) Phone: 859-218-2964 (office) 859-218-2965 (lab) 859-257-7715 (fax) Web: http://bioinformatics.cesb.uky.edu/ Address: CC434 Roach Building, 800 Rose Street, Lexington, KY 40536-0093
That is true and something I forgot about.
However, for potentially assigning any of the methods that don't have intrinsic scan level data, or where it is really hard to get scan level data to match aggregate peaks, this is the only option I can see trying without making major modifications to SMIRFE code.
Of course, if this doesn't work, then I'll use peak matching to the PeakChar assignments for evaluation.
After discussion w/ @hunter-moseley during our lab meeting, we've decided that making SMIRFE assign data this way is like putting a square peg into a round hole, and it doesn't make sense to compare assignments generated like this when SMIRFE expects scan level data.
I still went ahead and tried doing this, generating scan level m/z values from a normal distribution with 0.5 ppm SD and centered at the centroided m/z.
That still gives the same negative sample error in SMIRFE as we observed in #7 . So no MSnbase assignments. :shrug:
I had this idea long ago, but completely forgot until now.
To assign peak data that does not intrinsically have scan level data (i.e. the XCaliber data) we can create a fake scan level that just has 20 scans of identical peak information.
This should let it be assigned by SMIRFE.