-
Notifications
You must be signed in to change notification settings - Fork 31
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
Speed #49
Comments
Calling .readlines() a file is fast, as done for the event finding. I'm not sure where all of the .readline() methods are being called.
Reading in the files is fast. And profiling doesn't show any readline() calls. It could be this readline() call in oct2py/session.py:evaluate (line 551):
|
Here's profiling output of essentially just the DFlowData.clean_data() call:
Pretty sure all the slow ups are all from the Octave code. |
See issue #30 for details on the rtfilter. |
Here is a profile of essentially running DFlowData.clean_data() + all the methods in WalkingData (including inverse dynamics compuations).
I think using readline to pull the events from the record files is a major slow down. Also all the calls to session.py are oct2py calls, which are slow. I believe the slow parts are the inverse dynamics real time filter and the soder.m file.
The text was updated successfully, but these errors were encountered: