You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: