Skip to content
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

MetaDraw crashed while attempting to open the Chimeric Scan View. #2418

Closed
mzhastings opened this issue Sep 17, 2024 · 2 comments · Fixed by #2420
Closed

MetaDraw crashed while attempting to open the Chimeric Scan View. #2418

mzhastings opened this issue Sep 17, 2024 · 2 comments · Fixed by #2420

Comments

@mzhastings
Copy link

Describing the issue

MetaDraw crashed while attempting to open the Chimeric Scan View.

Reproducing the error

The scan being viewed was an ambiguous ID

  • Protein database

n/a

  • Mass spectrometry file types

.MZML

  • Settings

defaults

  • Example datafiles

Full sequence of peptide:
HGLDNY[Custom:NPA_Desthiobiotin on Y]RGYSLGNWVC[Common Fixed:Carbamidomethyl on C]AAKFESNFNTQATNR|HGLDNYRGY[Custom:NPA_Desthiobiotin on Y]SLGNWVC[Common Fixed:Carbamidomethyl on C]AAKFESNFNTQATNR

Path to folder with psm file and mzML file containing peptide:
"Z:\Users\Madeleine\CrashDataFiles"

Expected behavior for GUI

Expected to see the chimeric scan view

Screenshots

n/a

Desktop information

Additional context

@mzhastings
Copy link
Author

also fragment ion brackets aren't shown when looking at the ambiguous IDs child scan view (except for the first option)
image
image

@nbollis
Copy link
Member

nbollis commented Sep 18, 2024

Thanks for this report! The crash is an issue that I will look into.

The lack of fragment ions annotations is intended. When we write the psm/peptide file only the matched fragment ions from the first ambiguous option is outputted. This means MetaDraw does not have enough information to accurately annotate any other ambiguous search result.

image

@nbollis nbollis linked a pull request Sep 18, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants