-
Notifications
You must be signed in to change notification settings - Fork 4
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
Caching of existing files #49
Comments
This is unintended. The intention is for files to be considered regardless where they come from, unless they are outdated. I'm guessing this is caused by storing dependencies as absolute paths. Note that the cache will report why it needs regeneration if its log level is set low enough. Running |
Hi Max, thanks for the quick reply! I've found that the cache does not check the presence of the actually needed (lumi/pileup) files, but the cache (.pkl) file. Also, because of |
The I agree that having some things in |
If somebody has the time (hint**hint) there's an alternative: have a global and local cache mode.
The functionality for this is already there, but it needs cleanup and consolidation. Required changes:
I guess that should do the trick, but there's only so much coffee in one day... |
For now, I stuck to a simple fix :) 6b88c754 |
Since both Dominik and me are no longer at EKP, please let me know if there is help required on this. I don't have a working test environment anymore. |
When lumi/pileup files are already present in the repository, the files are still queried as they are not in the local cache. Is this behaviour on purpose? IMHO if someone else has checked in the files it would be convenient to simply use them
The text was updated successfully, but these errors were encountered: