-
Notifications
You must be signed in to change notification settings - Fork 7
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
Unparseable number during XiFDR #76
Comments
Can you provide the csv file that failed? It looks like some formatting error occurred. |
could you also send the file as it was before you saved it in excel? |
I think I found the problem. The input files contain commas - and source column is not quoted correctly. So need to add quotes there. But if you could change the input file names before search to something without a comma that should work. |
It really just seems like, it were the commas that disrupted the parsing - Thank you for your time and help! |
Next version will quote the fields that where the problem. |
Heya,
I ran .d-data (Q-TOF) through xiSearch (v2.1.5.5), which exported an CSV-file to the results-folder without any issues.
Hereafter, I tried to run it through xiFDR (v1.7.6.7) for validation, and the first error that occurred was:
I changed the text to columns in the CSV-file (columns separated by commas) through Excel, and tried to run it in xiFDR once again. Now I've got the following message, which I can't decipher:
May I have set the CSV-file or xiFDR up wrong, or could it be something else?
I really hit a wall here, so any help or any tips are highly appreciated.
The text was updated successfully, but these errors were encountered: