Streamline DataManager -> TreePiece Coordination #183
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
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.
This makes a couple of changes to how the DataManager interacts with TreePieces.
The 'registeredTreePieces' array maintained by the DataManager is cleared out immediately before the tree build. This removes the need to call 'clearRegisteredPieces' in various points throughout the code.
When the CUDA flag is enabled, TreePieces are now assigned CUDA streams when the tree build happens. Previously, this happened during 'commenceCalcualteGravityLocal', which meant that the GPU functionality was only useable when gravity was enabled.
The 'teststep' and 'testonestar' cases were both verified to be passing.