MetaMorpheus: Index search crashes when reading index if two proteins have the same accession

Hi,

please see the following crash report: MetaMorpheus: version 0.0.304 Data files were processed on a VMware, Inc. VMware7,1 computer using Windows version 6.2.9200.0 with a 64-Bit processor and 32 cores operating at 2.1GHz and 128GB installed RAM. .NET Framework Version: 4.7 or laterC:\Program Files\Thermo\MSFileReader\Fileio_x64.dll MISSING\nC:\Program Files\Thermo\MSFileReader\fregistry_x64.dll MISSING\nC:\Program Files\Thermo\MSFileReader\XRawfile2_x64.dll MISSING\n e: MzLibUtil.MzLibException: A crash occured in FlashLFQ during the intensity normalization process: Sequence contains no elements at FlashLFQ.FlashLfqEngine.Run() at TaskLayer.PostSearchAnalysisTask.QuantificationAnalysis() in C:\projects\metamorpheus\TaskLayer\SearchTask\PostSearchAnalysisTask.cs:line 455 at TaskLayer.PostSearchAnalysisTask.Run() in C:\projects\metamorpheus\TaskLayer\SearchTask\PostSearchAnalysisTask.cs:line 66 at TaskLayer.SearchTask.RunSpecific(String OutputFolder, List1 dbFilenameList, List1 currentRawFileList, String taskId, FileSpecificParameters[] fileSettingsList) in C:\projects\metamorpheus\TaskLayer\SearchTask\SearchTask.cs:line 381 at TaskLayer.MetaMorpheusTask.RunTask(String output_folder, List1 currentProteinDbFilenameList, List1 currentRawDataFilepathList, String displayName) in C:\projects\metamorpheus\TaskLayer\MetaMorpheusTask.cs:line 430e.Message: A crash occured in FlashLFQ during the intensity normalization process: Sequence contains no elementse.InnerException: e.Source: FlashLFQe.StackTrace: at FlashLFQ.FlashLfqEngine.Run() at TaskLayer.PostSearchAnalysisTask.QuantificationAnalysis() in C:\projects\metamorpheus\TaskLayer\SearchTask\PostSearchAnalysisTask.cs:line 455 at TaskLayer.PostSearchAnalysisTask.Run() in C:\projects\metamorpheus\TaskLayer\SearchTask\PostSearchAnalysisTask.cs:line 66 at TaskLayer.SearchTask.RunSpecific(String OutputFolder, List1 dbFilenameList, List1 currentRawFileList, String taskId, FileSpecificParameters[] fileSettingsList) in C:\projects\metamorpheus\TaskLayer\SearchTask\SearchTask.cs:line 381 at TaskLayer.MetaMorpheusTask.RunTask(String output_folder, List1 currentProteinDbFilenameList, List1 currentRawDataFilepathList, String displayName) in C:\projects\metamorpheus\TaskLayer\MetaMorpheusTask.cs:line 430e.TargetSite: FlashLFQ.FlashLfqResults Run()

thanks! D.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 19 (13 by maintainers)

Most upvoted comments

I’ve figured out what was the quantification problem – there was one of the samples accidentally set as tech replicate 2, without any replicate 1…

From: Robert Millikin notifications@github.com Sent: Monday, March 23, 2020 3:25 PM To: smith-chem-wisc/MetaMorpheus MetaMorpheus@noreply.github.com Cc: David Morgenstern david.morgenstern@weizmann.ac.il; Author author@noreply.github.com Subject: Re: [smith-chem-wisc/MetaMorpheus] MM crashed while quantifying (#1852)

I think to solve the second one, as @zrolfshttps://github.com/zrolfs implied, you will just need to delete your old index and have MetaMorpheus rebuild it. The index is probably built from an older version of MetaMorpheus that contained a bug, and newer versions have the bug fixed. So you will just need to delete the old index and have the new version of MM rebuild the index. If you’re not sure what I mean I can elaborate.

For the quantification crash, I think I will need your entire dataset unfortunately. Normalization crashes are hard to identify in isolation. Can you send your data to me?

Thanks!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/smith-chem-wisc/MetaMorpheus/issues/1852#issuecomment-602586650, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIQ5VIJFT7O6BDYEBYXTUUDRI5PLLANCNFSM4LRH2NTQ.

I also would lean toward “remove contaminants” as the default

@zrolfs ah ok I misunderstood. This is related to the discussion with @blfrey and @trishorts about what to do with proteins that appear in both the contaminant and target lists. I think we need some kind of user-facing setting about what to do with these conflicts (keep target, keep contaminant, keep both and rename them)

@Dmorgen ok thanks. MM is supposed to prevent that from happening, at least in the GUI. I think that can definetly occur if the experimental design is created outside of the GUI though (e.g., in Excel). If you made it with the GUI I need to fix something still