Skip to content
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

MatNWB timing #56

Closed
CodyCBakerPhD opened this issue Apr 30, 2024 · 1 comment
Closed

MatNWB timing #56

CodyCBakerPhD opened this issue Apr 30, 2024 · 1 comment

Comments

@CodyCBakerPhD
Copy link
Collaborator

It would also be great if we could find a way to run targetted timing operations via MatNWB (including the native ros3 method), similar to how we figured out how to do web based timings #30

@oruebel
Copy link
Contributor

oruebel commented Apr 30, 2024

We probably can't do the timing from Python directly, because it would likely include the time for starting up Matlab and importing MatNWB etc. (rather than just the operations we want to time). However, if we do the timing in Matlab itself, could we "just" run Matlab scripts that return the timing result back to Python (e.g., by writing to a file) and then in the test we can return the metric that Matlab tracked. For the network tracking tests, I think those could be run in a similar way. The network tracker records all traffic and then we filter by process ID, i.e., instead of using the process id for our Python process we would need to track the process that Matlab is running. I.e., as long as we can figure out the id of the process we need to track we should be able to do the network tracking as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants