Open3D
Open3D copied to clipboard
Stubs for FlyingObjects implementation
Type
- [ ] Bug fix (non-breaking change which fixes an issue): Fixes #
- [ ] New feature (non-breaking change which adds functionality). Resolves #
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) Resolves #
Motivation and Context
Checklist:
- [ ] I have run
python util/check_style.py --apply
to apply Open3D code style to my code. - [ ] This PR changes Open3D behavior or adds new functionality.
- [ ] Both C++ (Doxygen) and Python (Sphinx / Google style) documentation is updated accordingly.
- [ ] I have added or updated C++ and / or Python unit tests OR included test results (e.g. screenshots or numbers) here.
- [ ] I will follow up and update the code if CI fails.
- [ ] For fork PRs, I have selected Allow edits from maintainers.
Description
Thanks for submitting this pull request! The maintainers of this repository would appreciate if you could update the CHANGELOG.md based on your changes.
@intelshashi: could you provide some narrative explanation, or perhaps a link, to define your usage of the term “FlyingObjects”? It obviously does not mean that that phrase suggests to me. (I do a lot of work with objects that fly around in 3d space.) Apparently something to do with a class called vtkFlyingEdges3D
?
@intelshashi: could you provide some narrative explanation, or perhaps a link, to define your usage of the term “FlyingObjects”? It obviously does not mean that that phrase suggests to me. (I do a lot of work with objects that fly around in 3d space.) Apparently something to do with a class called
vtkFlyingEdges3D
?
I am exploring an alternative isocontour algorithm, see link below for details. https://www.kitware.com/really-fast-isocontouring/
Please note this pull request is work in progress, I was running out of disk space and wanted to make sure my changes were not lost. It will take sometime to be ready.
Closing as feature is merged through PR #6648