Open
Conversation
These are now created in Brian2 already
For now, this can be enabled via `set_device(..., report_timers=True`, but should eventually be moved into brian2
This file contains hidden or 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 PR
cuda_standalonesimulations. They are now debug prints.ComputationTimeSummaryclass, which is very similar to theProfilingSummaryclass, but reporting the times for compilation, initialization, simulation loop and finalization. In the current implementation, this information is printed viaset_device('cuda_standalone', report_timers=True). This implementation belongs into brian2 though, but I want it in the brian2cuda release I'm preparing this week, hence it will be in brian2cuda for now.TODO after:
cuda_utils.hfor debuggingComputationTimeSummary