You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before commit e0ae82021acd5b5d60763a24b73aa0053927b952 in https://github.com/lehtiolab/static-resources , scans above nr 502 in the labelfree-phos test crashed luciphor with "No such scan number in the index". Particularly scan nr 506 had an ID'ed peptide in Sage search, which is how this was found.
Maybe this had to do with that the scans are renumbered, but I'm not sure. I made luciphor crash in commit 3a055f7 to be sure of any problems in the future, but this is a bit weird. The scan number is found in the index, I don't know how the mzML reading library works here.
The text was updated successfully, but these errors were encountered:
Before commit e0ae82021acd5b5d60763a24b73aa0053927b952 in https://github.com/lehtiolab/static-resources , scans above nr 502 in the labelfree-phos test crashed luciphor with "No such scan number in the index". Particularly scan nr 506 had an ID'ed peptide in Sage search, which is how this was found.
Maybe this had to do with that the scans are renumbered, but I'm not sure. I made luciphor crash in commit 3a055f7 to be sure of any problems in the future, but this is a bit weird. The scan number is found in the index, I don't know how the mzML reading library works here.
The text was updated successfully, but these errors were encountered: