Optimize double loops in CT node #571
Draft
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.
I had some time to read the rules for CT node. And I found a low-hanging fruit.
There are 3 places where we are computing:
But inner loop over
dycan be moved on the upper level, and you will have linear complexity not quaratic overdy.I made a small script until we are developing here to check the speed boost quickly
benchmark/continuous_transition_bench.jl.I think the code style could be slightly improved but I what do you think about it guys?
My branch:
Main branch: