AND to load the cache on instantiation.
This requires some minor logic changes but None of them should affect users in anyway.
Motivation
Currently, the cache from DataConfig is loaded by the AnalysisManager, i.e. after instantiation. And it is the AnalysisManager that provides the path to the cache.
We want to be able to load it easily on instantiation, in order to be able to load and use it directly anywhere, and not just from within the AnalysisManager
What was changed
The core here is to replace in the DataConfig
use_cache
withAND to load the cache on instantiation. This requires some minor logic changes but None of them should affect users in anyway.
Motivation
Currently, the cache from DataConfig is loaded by the
AnalysisManager
, i.e. after instantiation. And it is theAnalysisManager
that provides the path to the cache. We want to be able to load it easily on instantiation, in order to be able to load and use it directly anywhere, and not just from within the AnalysisManager