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

Is caching is different for pre/post the update 2 month ago? #19

Open
hiranumn opened this issue May 11, 2021 · 1 comment
Open

Is caching is different for pre/post the update 2 month ago? #19

hiranumn opened this issue May 11, 2021 · 1 comment

Comments

@hiranumn
Copy link

First of all, thank you for this great work!

I had a model trained before the update you made 2 months ago.
Since then I updated everything to match the new version except that the cache folder stayed constant (accidentally).

I was experiencing any problem until today when I tried to run the trained model with the newly generated cache folder.

So my questions are,

  1. Is the cache generation process any different between pre/post update?
  2. Is there any concern if you train a new model with the post-update package with the old cache? Particularly, could it invalidate some of the nice assumptions that this model has?

Thank you so much in advance!
Nao

@FabianFuchsML
Copy link
Owner

FabianFuchsML commented May 20, 2021

  1. I don't think we changed anything about the caching for a long time (if ever since the first release); but if you suspect a change somewhere, git diff allows you to compare different commits, so maybe that might help

  2. as my answer to 1. is no, I don't suspect that using 'old caches' would lead to problems

I hope this helps :)
Fabian

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