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

'charmap' codec can't encode characters in position XX #183

Closed
JesusCastano01 opened this issue Aug 22, 2024 · 3 comments
Closed

'charmap' codec can't encode characters in position XX #183

JesusCastano01 opened this issue Aug 22, 2024 · 3 comments
Labels
Milestone

Comments

@JesusCastano01
Copy link

Hi,

I've been trying to use MS2Rescore with some results from MaxQuant, and I can't seem to get it to run successfully. I've tried different release versions, and I always run into an issue. I used it before successfully, but now, I haven't found a way to run it.

The current error message says:

UnicodeEncodeError: 'charmap' codec can't encode characters in position 18-20: character maps to

It looks like an encoding problem, but the msms file encoding is UTF-8 already, so I'm not sure.

I'm attaching the log file and json file, just in case.
I used ms2rescore 3.0.2 and also the latest version, and with both of them, I had the same issue.

I appreciate any advice on this.

Thanks,

CLI_test_percolator-config.json
ms2rescore_out_percolator.log.txt

@RalfG
Copy link
Member

RalfG commented Aug 22, 2024

Hi @JesusCastano01,

Thanks for reaching out! This is a very peculiar one... Would you also be able to share the input file? On first glance, the configuration file looks fine.

Best,
Ralf

@RalfG RalfG added the bug label Aug 22, 2024
@JesusCastano01
Copy link
Author

Hi Ralf,
Unfortunately, the input file is bigger than the allowed 25 MB. Any other way I can share the msms input file with you?

@RalfG RalfG added this to the v3.1.2 milestone Sep 17, 2024
@RalfG
Copy link
Member

RalfG commented Sep 18, 2024

Hi @JesusCastano01,

This was most-likely the same issue as in #185, which is now fixed in v3.1.2.

Best,
Ralf

@RalfG RalfG closed this as completed Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants