-
Notifications
You must be signed in to change notification settings - Fork 60
Add new 3D blob tracking example #500
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
base: RC_v1.6.x
Are you sure you want to change the base?
Add new 3D blob tracking example #500
Conversation
Linting results by Pylint:Your code has been rated at 8.31/10 (previous run: 8.31/10, +0.00) |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## RC_v1.6.x #500 +/- ##
=============================================
+ Coverage 63.55% 63.98% +0.43%
=============================================
Files 27 27
Lines 3844 3890 +46
=============================================
+ Hits 2443 2489 +46
Misses 1401 1401
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
I recommend handling issue #37 (Calculation of velocity components-vectors) in a separate PR, as it seems to affect multiple example scripts beyond the one modified here. |
This PR introduces a new example showcasing 3D blob tracking (#478). In addition, the following updates have been made:
New example added: A new example for generating and tracking 3D blobs has been added to the example folder
Environment update: The environment-examples.yml file has been updated to include any necessary dependencies related to the new example
Test function: A new test function has been added to tobac/testing.py to create a 3D blob
Doc: The new 3d example has been added to the gallery with an appropriate thumbnail
Have you followed our guidelines in CONTRIBUTING.md?
Have you self-reviewed your code and corrected any misspellings?
Have you written documentation that is easy to understand?
Have you written descriptive commit messages?
Have you added NumPy docstrings for newly added functions?
Have you formatted your code using black?
If you have introduced a new functionality, have you added adequate unit tests?
Have all tests passed in your local clone?
If you have introduced a new functionality, have you added an example notebook?
Have you kept your pull request small and limited so that it is easy to review?
Have the newest changes from this branch been merged?