[WIP] Multiple rod IO #181
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I noticed that while this implementation is convenient, it does not scale well. For <100 rods, it's seems to run fine, but for ~1000 rods, it slows down significantly. As such, I am putting this as WIP for the time being. |
fankiat
force-pushed
the
180_multiple_rod_io
branch
from
bc4cfc3
to
d225bf6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #180
An illustration of the resulting IO output as below. The rods are all in the same file for each timestamp, so users only need to load a file on paraview and all the rods added to the io would be rendered as separate rods.
test_multiple_rod.mp4