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

Mismatching model on the MS2Deepscore V2.0 Zenodo repository? #218

Open
AharoniLab opened this issue Jun 17, 2024 · 2 comments
Open

Mismatching model on the MS2Deepscore V2.0 Zenodo repository? #218

AharoniLab opened this issue Jun 17, 2024 · 2 comments

Comments

@AharoniLab
Copy link

Hi,

Thanks for inspiring work.

Following the basic instructions for using a pretrained model to compute spectral similarities (https://github.com/matchms/ms2deepscore/tree/main) and loading the 'ms2deepscore_model.pt' model from here: https://zenodo.org/records/10814307

...I get the following warning:

The model version (0.5.0) does not match the version of MS2Deepscore (2.0.0), consider downloading a new model or changing the MS2Deepscore version

Could you kindly clarify?

Also, a slightly less generic file name might be helpful

Thanks,-)

@niekdejonge
Copy link
Collaborator

Hi @AharoniLab,
This was a mistake on our end, thanks for notifying us! We forgot updating the version of MS2Deepscore before training that model, which results in this warning.
However, this model should actually work with version 2.0.0 (and not 0.5.0)
So, you can safely use the model and we will fix the warning for future releases of the model.

@AharoniLab
Copy link
Author

Hi Niek,
Thanks a lot for updating. The model indeed seems to be able to handle mixed-mode data, to a certain extent (more on that in another thread). I do however, get an error message when trying to setup Monte Carlo predictions (i.e. inference) when using the same mentioned model:

MM_similarity_measure = MS2DeepScoreMonteCarlo(model, n_ensembles=10)
_Monte Carlo Dropout is not supposed to be used with a model where dropout-rate=0_

That model has indeed a dropout rate of zero, but was it even designed to be used with this certainty estimation approach?

Thanks, Nir.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants