Apply peak to subsequent error

support
Apply peak to subsequent error Jason Held  2019-11-15
 

I'm assuming that the 'subsequent' in 'apply peak to subsequent' refers the result files lower in the file list. Is that true?

If either case, when I use it I get an error:

Top bit of the error window says "Failed to apply peak. Specific argument was out of the range of valid values. Parameter name: count:". More info gives this info:

System.Reflection.TargetInvocationException: Specified argument was out of the range of valid values.
Parameter name: count ---> System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: count
at System.Linq.Enumerable.Range(Int32 start, Int32 count)
at pwiz.Common.PeakFinding.FoundPeak.SetBoundaries(Int32 startIndex, Int32 endIndex) in C:\proj\pwiz_x64\pwiz_tools\Shared\Common\PeakFinding\FoundPeak.cs:line 97
at pwiz.Common.PeakFinding.PeakFinder.GetPeak(Int32 startIndex, Int32 endIndex) in C:\proj\pwiz_x64\pwiz_tools\Shared\Common\PeakFinding\PeakFinder.cs:line 52
at pwiz.Skyline.Model.Results.ChromatogramInfo.CalcPeak(Int32 startIndex, Int32 endIndex, FlagValues flags) in C:\proj\pwiz_x64\pwiz_tools\Skyline\Model\Results\ChromHeaderInfo.cs:line 2579
at pwiz.Skyline.Model.TransitionGroupDocNode.ChangePeak(SrmSettings settings, ChromatogramGroupInfo chromGroupInfo, Double mzMatchTolerance, Int32 indexSet, ChromFileInfoId fileId, OptimizableRegression regression, Transition transition, Nullable1 startTime, Nullable1 endTime, PeakIdentification identified, UserSet userSet, Boolean preserveMissingPeaks) in C:\proj\pwiz_x64\pwiz_tools\Skyline\Model\TransitionGroupDocNode.cs:line 2710
at pwiz.Skyline.Model.SrmDocument.<>c__DisplayClass162_0.<ChangePeak>b__0(TransitionGroupDocNode node, ChromatogramGroupInfo info, Double tol, Int32 iSet, ChromFileInfoId fileId, OptimizableRegression reg) in C:\proj\pwiz_x64\pwiz_tools\Skyline\Model\SrmDocument.cs:line 1721
at pwiz.Skyline.Model.SrmDocument.ChangePeak(IdentityPath groupPath, String nameSet, MsDataFileUri filePath, Boolean loadPoints, ChangeNodePeak change) in C:\proj\pwiz_x64\pwiz_tools\Skyline\Model\SrmDocument.cs:line 1774
at pwiz.Skyline.Model.SrmDocument.ChangePeak(IdentityPath groupPath, String nameSet, MsDataFileUri filePath, Transition transition, Nullable1 startTime, Nullable1 endTime, UserSet userSet, Nullable1 identified, Boolean preserveMissingPeaks) in C:\proj\pwiz_x64\pwiz_tools\Skyline\Model\SrmDocument.cs:line 1719 at pwiz.Skyline.Model.PeakMatcher.PeakMatch.ChangePeak(SrmDocument doc, SrmTreeNode nodePepTree, TransitionGroupDocNode nodeTranGroup, String nameSet, MsDataFileUri filePath) in C:\proj\pwiz_x64\pwiz_tools\Skyline\Model\PeakMatcher.cs:line 418 at pwiz.Skyline.Model.PeakMatcher.ApplyPeak(SrmDocument doc, PeptideTreeNode nodePepTree, TransitionGroupDocNode& nodeTranGroup, Int32 resultsIndex, ChromFileInfoId resultsFile, Boolean subsequent, ILongWaitBroker longWaitBroker) in C:\proj\pwiz_x64\pwiz_tools\Skyline\Model\PeakMatcher.cs:line 150 at pwiz.Skyline.SkylineWindow.<>c__DisplayClass1198_2.<ApplyPeak>b__0(ILongWaitBroker monitor) in C:\proj\pwiz_x64\pwiz_tools\Skyline\SkylineGraphs.cs:line 2111 at pwiz.Skyline.Controls.LongWaitDlg.RunWork(Action1 performWork) in C:\proj\pwiz_x64\pwiz_tools\Skyline\Controls\LongWaitDlg.cs:line 232
--- End of inner exception stack trace ---
at pwiz.Skyline.Util.Helpers.WrapAndThrowException(Exception x) in C:\proj\pwiz_x64\pwiz_tools\Skyline\Util\Util.cs:line 1909
at pwiz.Skyline.Controls.LongWaitDlg.PerformWork(Control parent, Int32 delayMillis, Action`1 performWork) in C:\proj\pwiz_x64\pwiz_tools\Skyline\Controls\LongWaitDlg.cs:line 180
at pwiz.Skyline.SkylineWindow.ApplyPeak(Boolean subsequent) in C:\proj\pwiz_x64\pwiz_tools\Skyline\SkylineGraphs.cs:line 2111

 
 
Kaipo responded:  2019-11-15

Subsequent refers to the run time of the results files. As for the error would you mind sharing the file (File > Share...)? You can upload it to https://skyline.ms/files.url or email it to me (kaipot at uw.edu) directly.

Thanks,
Kaipo

 
Jason Held responded:  2019-11-15

In the meantime I've closed and re-opened skyline (didn't update or anything) but I am not longer getting the error.

Jason