feat: sparse horizon handler for vdf #276
Merged
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.
The current horizon-based handler for VDF aggregates flow over
N
iterations for every link in every interval (for example, 5 minutes). All of this is saved as one huge block in memory and also generates large files in the output when running large-scale scenarios, for instance when using the whole network of Bavaria.This PR introduces (experimentally) the "Sparse Horizon" handler, which works exactly as the standard version, but only saves observations that have actually taken place. So if a link in a specific time step in a specific iteration had zero flow, it will not appear in memory. This will very likely drastically decrease memory use for large-network simulations which are run with low population sampling rates.
TODO;