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
I noticed while browsing results in pLabel 2.4 that the spectra are no longer in the order of the scan number. I found it quite useful when spectra were ordered by scan number because I validate hundreds of spectra across many raw files manually, and I didn’t have to search for each spectrum individually. It would be great if spectra could once again be ordered by scan number, or if you can suggest a way for me to effect this in pLabel.
I would find it useful if the Alpha Fragment Ion Coverage Rate and Beta Fragment Ion Coverage Rate that I can see in pLabel were reported in the file ending with: cross-linked_spectra.csv. (I'm still using pLink 2, so please forgive me if this is already included in pLink 3 output)
The text was updated successfully, but these errors were encountered:
1.We apologize for any inconvenience. To make it easier for users to view the spectra with better matches, we have sorted the display order based on the quality of identification. For now, specific spectra can only be accessed through search. Thank you for your suggestion
2.Thank you for your suggestion. We will consider adding this feature in future iterations
Hi,
I noticed while browsing results in pLabel 2.4 that the spectra are no longer in the order of the scan number. I found it quite useful when spectra were ordered by scan number because I validate hundreds of spectra across many raw files manually, and I didn’t have to search for each spectrum individually. It would be great if spectra could once again be ordered by scan number, or if you can suggest a way for me to effect this in pLabel.
I would find it useful if the Alpha Fragment Ion Coverage Rate and Beta Fragment Ion Coverage Rate that I can see in pLabel were reported in the file ending with: cross-linked_spectra.csv. (I'm still using pLink 2, so please forgive me if this is already included in pLink 3 output)
The text was updated successfully, but these errors were encountered: