-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skyline/work/20230710 add refine with shape correlation #2663
base: master
Are you sure you want to change the base?
Skyline/work/20230710 add refine with shape correlation #2663
Conversation
…antizationCutoff parameters
…lue below test cutoff
…ttps://github.com/ProteoWizard/pwiz into Skyline/work/20230710_addRefineWithShapeCorrelation
Let's make it "refine-shape-r-include-cutoff" and
"refine-shape-r-quant-cutoff". We don't need to spell everything out
completely in the argument name. That is what the description is for. There
is some value to keeping these argument names shorter. For one, they fit
the documentation table layout better.
…On Mon, Jul 17, 2023 at 10:19 AM nickshulman ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In pwiz_tools/Skyline/CommandArgs.cs
<#2663 (comment)>:
> @@ -902,6 +902,10 @@ private bool ParseReintegrateExcludeFeature(NameValuePair pair)
(c, p) => c.Refinement.QValueCutoff = p.ValueDouble);
public static readonly Argument ARG_REFINE_MINIMUM_DETECTIONS = new RefineArgument(@"refine-minimum-detections", INT_VALUE,
(c, p) => c.Refinement.MinimumDetections = p.ValueInt);
+ public static readonly Argument ARG_REFINE_SC_INCLUDED_CUTOFF = new RefineArgument(@"refine-shape-correlation-included-cutoff", NUM_VALUE,
+ (c, p) => c.Refinement.SCIncludedCutoff = p.ValueDouble);
+ public static readonly Argument ARG_REFINE_SC_QUANTIZATION_CUTOFF = new RefineArgument(@"refine-shape-correlation-quantization-cutoff", NUM_VALUE,
I think the word here should be "quantitative".
Transitions with a shape correlation below this value will be marked as
non-quantitative.
—
Reply to this email directly, view it on GitHub
<#2663 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACYBWUDCJJEKU4XVLCRXZALXQVX2JANCNFSM6AAAAAA2K2M7VM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
…ttps://github.com/ProteoWizard/pwiz into Skyline/work/20230710_addRefineWithShapeCorrelation
…o ComparisonType.min
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like you've added a bunch of files (.sky, .blib, etc) in "TestData\Refine".
Usually we would put all these sorts of files inside of one .zip file.
{ | ||
if (type == ComparisonType.min) | ||
{ | ||
comparisonValue = chromInfos.Min(c => c.PeakShapeValues?.ShapeCorrelation); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this will end up doing the wrong thing if any of the shape correlation values are null.
For the purposes of "Min", "null" is considered lower than any other number.
However, in terms of "<" or ">", comparison of null to a number is always false.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing this out. I changed the method to now check if shape correlation values are above the cutoff. If the method returns false the transition will be removed. Now when the comparison value is null the method will return false and the transition will be removed.
…or null SC values
…ttps://github.com/ProteoWizard/pwiz into Skyline/work/20230710_addRefineWithShapeCorrelation
…k/20230710_addRefineWithShapeCorrelation
…k/20230710_addRefineWithShapeCorrelation
…k/20230710_addRefineWithShapeCorrelation
…sources.resx Change "ARG_REFINE_SC_INCLUDED_COMPARISON_TYPE" to use "ComparisonType" enum.
…k/20230710_addRefineWithShapeCorrelation
Added 2 parameters to the consistency tab of the RefineDlg. IncludedCutoff removes all transitions with a shape correlation below the cutoff value. QuantizationCutoff marks all transitions with a shape correlation below the value as non-quantitative.