Fix collection of timer information #42
Merged
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
jasperalbers
approved these changes
Dec 17, 2021
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.
The PR 3 of [beNNch-models]((https://github.com/INM-6/beNNch-models/) changed the content of the logging files: They now also contain all of the
nest.GetKernelStatus()dictionary. This leads to problems when collecting the timer information: 1) The content of a line can possibly have more than two entries. 2) Not all entries are of interest for further timer analysis.This PR fixes both problems. Any entry that does not fit into the
key, valuescheme is written into a throwaway list. Any entry that is not part of the metrics of interest is disregarded.I have tried it with the microcircuit but I don't see a reason why it should behave differently with the other models.