-
Notifications
You must be signed in to change notification settings - Fork 6
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
Implement MLx related integration tests #110
Conversation
@mmesim, I added some more As discussed, could you please compute the results from the integration-tests
independently? (You'll find the test data in the Thanks. |
OT: This is detection related (and not
I noted an interesting behavior when increasing the |
Note that detection is performed on the horizontal components (once on the first horizontal component, once on the second horizontal component). Note also that with this commit the tests are not configured, yet (i.e. in the `dataset.conf`).
Detect on vertical component, while MLx is computed based on the horizontal components.
Fix memory leak when executing multiple `MLx` amplitude/magnitude integration tests. The static index was not cleared properly during resetting the `magnitude::Factory`. At the time being, an index is most probably not required, anyway.
Use multiple streams from different sensor locations. Use multiple template families.
Attached the notebook used to validate the tests. Credits to @mmesim. Note that the actual implementation uses a slightly different order when it comes to preprocessing the data. E.g. the data is filtered before it is deconvoluted. |
MLx
integration tests #75.Closes #75.