-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graph visualisation would only work if CUDASimulation was explicitly init() #1243
Conversation
Thinking about this, technically it's possible for a user to activate a visualisation after the simulation has been init, e.g. if manually stepping the model. So that call should also be updated to hook if the sim has been init I guess. Edit: With further changes this should now be addressed, quickly tested it in davids example model by calling |
…licitly init() It should now work if the simulation is not explicitly init, or is init before the visualiser is created.
… provided. On Windows (under visual studio) if a std::filesystem::path contains ':', extension() returns empty string. There's not an obvious method within std::filesystem to check a path for bad characters.
e07ebce
to
055e348
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me (I've not tested it myself).
Nice spot of the incorrect exception message in LoggerFactory too.
applyConfig_derived()
is not implicitly called, I assumed otherwise. Hence,CUDAEnvironmentDirectedGraphBuffers
was not receiving it's ptr to the visualisation.Also noticed an edge-case with invalid characters in filepaths on Windows so improved the exception thrown.