Fix check_macro_cache logic around self.is_over_dataset #269
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #268. This reverts the logic within
Simulation.check_macro_cache
to ensure that when it checks the value ofself.is_over_dataset
, it follows the same logic present prior to the integration ofSimulationMacroCache
, i.e., the logic available atpolicyengine-core/policyengine_core/simulations/simulation.py
Line 1407 in 62e6be0
This does not add tests. While
SimulationMacroCache
did when it was merged, it was unclear how it actually fit intoSimulation
itself. Moving forward, we should clarify the aims and requirements of the macro cache, refactorSimulation
(open as #264), then add tests toSimulation
itself to prevent a similar issue