I am also very interested in trying this out. In my document (Lumos data, ~13.8K precursors), only "retention time difference [squared]" and "identified count" are available for the model. The remaining scores are greyed out, including "precursor isotope dot product" and "precursor mass error" which should be useful for the model. These scores are not showing up in the Feature Scores histogram and are displayed only in the "unknown" bar, but they appear to be calculated and displayed as usual in the rest of the document. Am I doing something incorrectly, or is this the expected behavior?
Thanks!
Anatoly

Hey Anatoly,

Check out the following tutorial. Look for the Handling Missing Values section.

https://skyline.ms/_webdav/home/software/Skyline/@files/tutorials/PeakPicking_2-5.pdf

This idea worked really well for me for some Lumos phospho data. Especially with phospho data where it's super important to pick the right precursor I can see the benefit of this technique.

Good luck!

-Aaron

Hi Aaron,

Thanks for the response. I actually did read the tutorial before posting :)
I don't think my problem is about missing values. I am including a screenshot for idotp.
In your document, are you able to see any values for idotp and precursor ppm error in the histogram and actually use these as part of the model?

Thanks,
Anatoly

Hi Anatoly,
Can you post a screenshot of your Peptide Settings - Modifications tab? I have seen this kind of thing before in label-free experiments where the isotope labeling settings have not accurately reflected the experiment. I think in the past it has turned out to be that the standard type was set to "light". I believe this causes Skyline to think there is not any experimental measurements, just standards, which explains why even "Intensity" is grayed out.

Sorry for the confusing presentation.

--Brendan

For sure, had to ask.

Attached is what mine looks like.

Thank you, Brendan.
That was exactly the problem - I had internal standard type set to "light." I changed it to "None" and the rest of the scores are now available for the model. This is a fantastic addition to Skyline - thanks for your help!
Anatoly

Hi Brendan,

I do have an issue with using this feature. It seems to me like the main reason to use it would be to get q-values which can be used for statistics.

However, in the "group comparisons" feature, despite setting a q-value cutoff (which I was really excited about having the ability to do), I don't see any changes in my statistics. It's unfortunate as this feature seemed great but I was underwhelmed when I wasn't able to use it for statistics and had to use MSSTATS in R with a q-value filter.

I noticed the same thing with DIA data and mProphet modeling.

-Aaron

Aaron,

From looking at the code, I think the "Q-Value Cutoff" that you can specify in the Advanced section of the Edit Group Comparison dialog does not actually do what it's supposed to do. It does affect things like which results are included in "equalize median" normalization, but it does not affect the more important thing of excluding results from a group comparison.

If you go to:
Edit > Refine > Reintegrate
and set a q-value cutoff there, you'll get the same numbers as you would have gotten if the Q-value cutoff worked in the Group Comparison setting, but being able to control for each Group Comparison you define was supposed to be a much faster way to compare different possible values for that.

I'll try to fix this in an upcoming release of Skyline-Daily.
-- Nick