-
Notifications
You must be signed in to change notification settings - Fork 12
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
how was octree generated? #4
Comments
Hello, thank you very much for your interest in our work! We have referenced the design of our baseline, Octformer (https://arxiv.org/abs/2305.03045), for the specific implementation of our octree. The specific implementation code can be found in the ocnn library mentioned in requirement.txt. Indeed, I think as you said, the octree is added to the batch as a static dictionary. My understanding is that the octree is statically defined in the batch you mentioned, and then instantiated with the input point cloud features in the following part in classification.py: def get_input_feature(self, octree):
flags = self.FLAGS.MODEL
octree_feature = ocnn.modules.InputFeature(flags.feature, flags.nempty)
data = octree_feature(octree)
return data For further understanding, perhaps you could refer to Octformer. |
Hello, I have a confused question as follows. |
Hi, thanks for the brilliant work first!
I'm a bit confused about how was octree generated. In
classification.py
it seems that octree already exists in thebatch
dictionary,which looks like something from dataset.
But logically octree is generated upon the input point cloud, rather than being provided along with dataset. Could you explain the origin outcoming of octree, i.e. when/in which script was it generated and written into
batch
dict? Thanks a lot!The text was updated successfully, but these errors were encountered: