-
Notifications
You must be signed in to change notification settings - Fork 49
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
Doubts about datasets #93
Comments
Re: 1 So the When a CAD model is created the designer can create and nest multiple layers of components. This becomes the tree structure. One way to understand this is to rebuild the CAD and inspect it manually in Fusion 360 using this script: https://github.com/AutodeskAILab/Fusion360GalleryDataset/tree/master/tools/assembly2cad Re: 2
Re: 3
The location is contained in the Re: 4 Re: 5 |
Thank you for your reply. |
Also about the source of this data, you said it was obtained by parsing this .f3d using Fusion 360 python API, I wonder if you have the intention to open source this parser? |
So you mean the FYI 8b4e1828-b296-11eb-9d3c-f21898acd3b7.smt and 8b4e5752-b296-11eb-9d3c-f21898acd3b7.smt are two bodies. One of them is the screw and one of them is the plate. There are two components - one is the root component containing the plate, and one is the screw component. |
Yes we parsed the .f3d files using the python API. Unfortunately we don't have plans to release this code. |
Your response was so timely and I appreciate you being so patient in answering my questions, however, the answer here raises three other minor questions for me. 2.What kind of components and bodies are put into the root hierarchy, and are there any characteristics of the components and bodies that are put into the root hierarchy? 3.Does there exist assembly data for a component that contains multiple bodies, and if so, is it possible to give information about this assembly data so that I can quickly retrieve it in the dataset. Thank you as always and have a nice day ! |
This is because there is one body in the root component (which by definition there can be only one root, so therefore no occurrences). Occurrences will exist for all regular components, just not the root.
This really depends on the designers preferences.
Yes that is possible. What I would suggest you do to understand how the assemblies are structured is to rebuild them and inspect them manually in Fusion 360 using this script: https://github.com/AutodeskAILab/Fusion360GalleryDataset/tree/master/tools/assembly2cad |
Ok, thanks for your reply, I will try to rebuild it to understand it better. |
Thank you for open sourcing such a great project!
But I have a few questions about Assembly Dataset that I hope you can answer.
Hierarchical information about the assembly dataset, such as Tree, root, etc. There are some variables that I somewhat don't quite understand after reading the paper and in the presentation of Fusion 360 Gallery, as follows:
In the paper you say: "The tree contains this hierarchy information by linking to occurrence UUIDs." Is the tree the whole diagram in Figure 9 right in the paper? Does it include the parts below? (I understand that the parts should be the bodies in the paper.) I may be a bit vague about the definition of the tree.
For example, take an assembly(20215_e2eb3082)that I randomly selected from the Assembly Dataset. Looking at the JSON file, the Tree only contains a dictionary with a key of root and a value of occurrences, but at the root level of the data it contains only components and bodies, which shouldn't mean the same thing as root, right?
Is the 'name' of Occurrence in the dataset the proper name for the component in a particular industry, and does it contain other information such as location or order that is useful for assembly?
About 'body' inside the 'name' naming method for 'Body' + 'number', and different 'bodies' may contain the same name, what does this number indicate?
5.The last point, about the naming of bodies, occurrences, components, similar to 20215_e2eb3082 in occurrences: 03fd7a74-05b5-11ec-ba40-0a17b33ae929, component: 03fcde40-05b5- 11ec-8cdf-0a17b33ae929, bodies: 03f2f326-05b5-11ec-9d62-0a17b33ae929, do these numbers and letters have any special meaning?
Hope to get your reply!
Thank you as always and have a nice day !
The text was updated successfully, but these errors were encountered: