-
Notifications
You must be signed in to change notification settings - Fork 0
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
Unable to read mgf files #108
Comments
Hi, Please check the CSV files to see if it has two columns named 'matchscore'. If so, try deleting one of them and uploading again. Please let me know if this works or if there are still problems. Best wishes, |
Hi Colin, Thanks |
Hmmm. |
it could be taking spaces out of column names also, so "matchscore" and "Match Score" would count as duplicate column names |
Hi Colin i tried to send you an email yesterday with the csv file but the email could not send for some reason. i have attached it here. |
i have seen your email about the file containing two different matchscores. which one would be best to delete? |
yes... it has "MatchScore" and "match score" and the xiview parser thinks these are the same, which it maybe shouldn't do. |
thank you so much for the help I'll try those now |
The right one to delete would be |
I think those columns are part of the xiSEARCH csv output, not of the xiFDR CSM file that is the one that should be uploaded to xiView. Indeed the file you have uploaded here is not the CSM file, but it's the unfiltered csv file coming out of xiSEARCH as far as I can tell. See reply Rappsilber-Laboratory/XiSearch#107 |
i think @bsakc has things working now. You should upload the mzIdentML file produced by xiFDR. |
log id:mmacgkfv5e00qtjsp7o96rt4pq_1719841584.log
error type:Error
message:duplicate column(s): matchscore
id: undefined
I have created the mgf files on both proteome discoverer and MSconvert however, i always get this error message and cannot see the spectra matching to the crosslinks. the csv files were produced using xisearch. Please let me know if there is an issue with my workflow
The text was updated successfully, but these errors were encountered: