Update README.md
#1
by
ccm
- opened
README.md
CHANGED
@@ -20,63 +20,66 @@ Complementing these representation modalities, we also provide a configuration-b
|
|
20 |
|
21 |
|
22 |
|
23 |
-
- **Curated by:**
|
24 |
-
- **Funded by [optional]:** [More Information Needed]
|
25 |
-
- **Shared by [optional]:** [More Information Needed]
|
26 |
-
- **Language(s) (NLP):**
|
27 |
-
- **License:**
|
28 |
|
29 |
### Dataset Sources [optional]
|
30 |
|
31 |
<!-- Provide the basic links for the dataset. -->
|
32 |
|
33 |
-
- **Repository:** [
|
34 |
- **Paper [optional]:** HUVER: The HyForm Uncrewed Vehicle Engineering Repository, ASME JMD (under review)
|
35 |
-
- **Demo [optional]:** [More Information Needed]
|
36 |
|
37 |
## Uses
|
38 |
|
|
|
|
|
|
|
39 |
- The multimodal UAV dataset presented in this paper features a variety of UAV representations, including 3D models in GLB format, grammar representations, text descriptions, and parametric data. This diversity facilitates the development of surrogate models that utilize different UAV representations to predict performance more accurately.
|
40 |
- This multifaceted UAV dataset supports the creation of diverse UAV designs through various generative models.
|
41 |
Models like GANs, LSTMs, transformers, and GNNs can generate new UAV images and designs in different formats, including GLB.
|
42 |
The inclusion of negative examples in the dataset helps identify and correct potential design flaws early, enhancing model refinement and
|
43 |
ensuring the feasibility and safety of the UAV designs.
|
44 |
|
45 |
-
|
46 |
-
|
47 |
-
<!-- This section describes suitable use cases for the dataset. -->
|
48 |
-
|
49 |
-
[More Information Needed]
|
50 |
|
51 |
### Out-of-Scope Use
|
52 |
|
53 |
<!-- This section addresses misuse, malicious use, and uses that the dataset will not work well for. -->
|
54 |
|
55 |
-
[More Information Needed]
|
|
|
|
|
56 |
|
57 |
## Dataset Structure
|
58 |
|
59 |
### Data Instances
|
|
|
60 |
{
|
61 |
-
'Image': <0001.png>,
|
62 |
-
'glb_file': <https://huggingface.co/datasets/raiselab/HUVER/resolve/main/train/glb/0001.glb?download=true>,
|
63 |
-
'Grammar_string": <*aMM0-*bNM2++*cMN1++*dLM2*eML1^ab^ac^ad^ae>,
|
64 |
-
'Cost ($)': <1877.19>,
|
65 |
-
'Number of Batteries': <1>,
|
66 |
-
'Number of Motor-Rotor Pairs': <4>, 'Number of Airfoils': <0>,
|
67 |
-
'Number of Connectors': <4>,
|
68 |
-
'Weight of Batteries (lb)': <19.40347644>,
|
69 |
-
'Weight of Motor-Rotor Pair (lb)': <3.858051314>,
|
70 |
-
'Weight of Airfoils (lb)': <0.0>,
|
71 |
-
'Total Weight (lb)': <23.26152854>,
|
72 |
-
'Total Thrust (lb)': <82.50002518>,
|
73 |
-
'Normalized Average Structure Size': <0.324324324>,
|
74 |
-
'Normalized Average Motor Size': <0.259259259>,
|
75 |
-
'Normalized Average Foil Size': <0.0>,
|
76 |
-
'Design Descriptor': <This drone is made up of 1 part and has 4 engines that help it move. It also has 0 wings for better flying. It has 4 links that connect everything together securely. The drone weighs 23.2615285432816 pounds in total and can lift itself and more, thanks to its strong thrust of 82.500025177002 pounds.>,
|
77 |
-
'Operations Descriptor': <This drone configuration has a feasible flying range of 0.0-0.0 miles, evaluated over the payload range of 0-0 pounds. This configuration has a velocity range of 0.06352621-0.06352621 mph. It is observed when payload increases, the flying range and velocity decrease. The drones achieve highest values of velocity and range for the lowest payloads. It can be interpreted from the data that the drone can fly as far as 0.0 miles, and can reach maximum speeds up to 0.06352621 mph. This means that while the drone does well in many situations, how far and fast it can fly can vary with how much payload it carries. This drone costs around $1877.19, adding up costs of all the components used to achieve this configuration.>,
|
78 |
-
'Performance': <Feasibilty": "CouldNotStabilize", "Flying Range": 0.0, "Payload Capacity (lb)": 0, "Velocity (mph)": 0.06352621, "Performance Descriptor": "This drone could not hover. The drone for a payload of 0 pounds, could not accomplish a successful run, the reason being either the motors could not provide enough lift or the drone did not balance properly after flight".>
|
79 |
}
|
|
|
80 |
|
81 |
### Data Fields
|
82 |
- Grammar String : Each UAV configurationn in this dataset can be fully described by a grammar string, which is structured according to specific pre-defined grammar rules.
|
@@ -91,7 +94,7 @@ ensuring the feasibility and safety of the UAV designs.
|
|
91 |
|
92 |
## Visualization
|
93 |
|
94 |
-
|
95 |
|
96 |
## Dataset Creation
|
97 |
|
@@ -117,7 +120,7 @@ You can [visualize](https://github.com/raiselab23/HUVER/blob/main/visualization.
|
|
117 |
|
118 |
[More Information Needed]
|
119 |
|
120 |
-
### Annotations [optional]
|
121 |
|
122 |
<!-- If the dataset contains annotations which are not part of the initial data collection, use this section to describe them. -->
|
123 |
|
@@ -151,32 +154,35 @@ You can [visualize](https://github.com/raiselab23/HUVER/blob/main/visualization.
|
|
151 |
|
152 |
Users should be made aware of the risks, biases and limitations of the dataset. More information needed for further recommendations.
|
153 |
|
154 |
-
## Citation [optional]
|
155 |
|
156 |
<!-- If there is a paper or blog post introducing the dataset, the APA and Bibtex information for that should go in this section. -->
|
157 |
|
158 |
-
**BibTeX:**
|
159 |
|
160 |
[More Information Needed]
|
161 |
|
162 |
**APA:**
|
163 |
|
164 |
-
[More Information Needed]
|
165 |
|
166 |
-
## Glossary [optional]
|
167 |
|
168 |
|
169 |
|
170 |
-
[More Information Needed]
|
171 |
|
172 |
-
## More Information [optional]
|
173 |
|
174 |
-
[More Information Needed]
|
175 |
|
176 |
-
## Dataset Card Authors [optional]
|
177 |
|
178 |
-
[More Information Needed]
|
179 |
|
180 |
## Dataset Card Contact
|
181 |
|
182 |
-
[More Information Needed]
|
|
|
|
|
|
|
|
20 |
|
21 |
|
22 |
|
23 |
+
- **Curated by:** Abhiram Karri, Gary Stump, Christopher McComb, Binyang Song
|
24 |
+
<!-- - **Funded by [optional]:** [More Information Needed] -->
|
25 |
+
<!-- - **Shared by [optional]:** [More Information Needed] -->
|
26 |
+
- **Language(s) (NLP):** English, en
|
27 |
+
- **License:** MIT
|
28 |
|
29 |
### Dataset Sources [optional]
|
30 |
|
31 |
<!-- Provide the basic links for the dataset. -->
|
32 |
|
33 |
+
- **Repository:** [HUVER](https://huggingface.co/datasets/raiselab/HUVER)
|
34 |
- **Paper [optional]:** HUVER: The HyForm Uncrewed Vehicle Engineering Repository, ASME JMD (under review)
|
35 |
+
<!-- - **Demo [optional]:** [More Information Needed] -->
|
36 |
|
37 |
## Uses
|
38 |
|
39 |
+
### Direct Use
|
40 |
+
|
41 |
+
<!-- This section describes suitable use cases for the dataset. -->
|
42 |
- The multimodal UAV dataset presented in this paper features a variety of UAV representations, including 3D models in GLB format, grammar representations, text descriptions, and parametric data. This diversity facilitates the development of surrogate models that utilize different UAV representations to predict performance more accurately.
|
43 |
- This multifaceted UAV dataset supports the creation of diverse UAV designs through various generative models.
|
44 |
Models like GANs, LSTMs, transformers, and GNNs can generate new UAV images and designs in different formats, including GLB.
|
45 |
The inclusion of negative examples in the dataset helps identify and correct potential design flaws early, enhancing model refinement and
|
46 |
ensuring the feasibility and safety of the UAV designs.
|
47 |
|
48 |
+
<!-- [More Information Needed] -->
|
|
|
|
|
|
|
|
|
49 |
|
50 |
### Out-of-Scope Use
|
51 |
|
52 |
<!-- This section addresses misuse, malicious use, and uses that the dataset will not work well for. -->
|
53 |
|
54 |
+
<!-- [More Information Needed] -->
|
55 |
+
This dataset is not appropriate for detailed design of flight ready systems.
|
56 |
+
|
57 |
|
58 |
## Dataset Structure
|
59 |
|
60 |
### Data Instances
|
61 |
+
```json
|
62 |
{
|
63 |
+
'Image': <0001.png>,
|
64 |
+
'glb_file': <https://huggingface.co/datasets/raiselab/HUVER/resolve/main/train/glb/0001.glb?download=true>,
|
65 |
+
'Grammar_string": <*aMM0-*bNM2++*cMN1++*dLM2*eML1^ab^ac^ad^ae>,
|
66 |
+
'Cost ($)': <1877.19>,
|
67 |
+
'Number of Batteries': <1>,
|
68 |
+
'Number of Motor-Rotor Pairs': <4>, 'Number of Airfoils': <0>,
|
69 |
+
'Number of Connectors': <4>,
|
70 |
+
'Weight of Batteries (lb)': <19.40347644>,
|
71 |
+
'Weight of Motor-Rotor Pair (lb)': <3.858051314>,
|
72 |
+
'Weight of Airfoils (lb)': <0.0>,
|
73 |
+
'Total Weight (lb)': <23.26152854>,
|
74 |
+
'Total Thrust (lb)': <82.50002518>,
|
75 |
+
'Normalized Average Structure Size': <0.324324324>,
|
76 |
+
'Normalized Average Motor Size': <0.259259259>,
|
77 |
+
'Normalized Average Foil Size': <0.0>,
|
78 |
+
'Design Descriptor': <This drone is made up of 1 part and has 4 engines that help it move. It also has 0 wings for better flying. It has 4 links that connect everything together securely. The drone weighs 23.2615285432816 pounds in total and can lift itself and more, thanks to its strong thrust of 82.500025177002 pounds.>,
|
79 |
+
'Operations Descriptor': <This drone configuration has a feasible flying range of 0.0-0.0 miles, evaluated over the payload range of 0-0 pounds. This configuration has a velocity range of 0.06352621-0.06352621 mph. It is observed when payload increases, the flying range and velocity decrease. The drones achieve highest values of velocity and range for the lowest payloads. It can be interpreted from the data that the drone can fly as far as 0.0 miles, and can reach maximum speeds up to 0.06352621 mph. This means that while the drone does well in many situations, how far and fast it can fly can vary with how much payload it carries. This drone costs around $1877.19, adding up costs of all the components used to achieve this configuration.>,
|
80 |
+
'Performance': <Feasibilty": "CouldNotStabilize", "Flying Range": 0.0, "Payload Capacity (lb)": 0, "Velocity (mph)": 0.06352621, "Performance Descriptor": "This drone could not hover. The drone for a payload of 0 pounds, could not accomplish a successful run, the reason being either the motors could not provide enough lift or the drone did not balance properly after flight".>
|
81 |
}
|
82 |
+
```
|
83 |
|
84 |
### Data Fields
|
85 |
- Grammar String : Each UAV configurationn in this dataset can be fully described by a grammar string, which is structured according to specific pre-defined grammar rules.
|
|
|
94 |
|
95 |
## Visualization
|
96 |
|
97 |
+
Once you've downloaded the dataset you can visualize it [using this script](https://github.com/raiselab23/HUVER/blob/main/visualization.py).
|
98 |
|
99 |
## Dataset Creation
|
100 |
|
|
|
120 |
|
121 |
[More Information Needed]
|
122 |
|
123 |
+
<!-- ### Annotations [optional] -->
|
124 |
|
125 |
<!-- If the dataset contains annotations which are not part of the initial data collection, use this section to describe them. -->
|
126 |
|
|
|
154 |
|
155 |
Users should be made aware of the risks, biases and limitations of the dataset. More information needed for further recommendations.
|
156 |
|
157 |
+
<!-- ## Citation [optional] -->
|
158 |
|
159 |
<!-- If there is a paper or blog post introducing the dataset, the APA and Bibtex information for that should go in this section. -->
|
160 |
|
161 |
+
<!-- **BibTeX:**
|
162 |
|
163 |
[More Information Needed]
|
164 |
|
165 |
**APA:**
|
166 |
|
167 |
+
[More Information Needed] -->
|
168 |
|
169 |
+
<!-- ## Glossary [optional] -->
|
170 |
|
171 |
|
172 |
|
173 |
+
<!-- [More Information Needed] -->
|
174 |
|
175 |
+
<!-- ## More Information [optional] -->
|
176 |
|
177 |
+
<!-- [More Information Needed] -->
|
178 |
|
179 |
+
<!-- ## Dataset Card Authors [optional] -->
|
180 |
|
181 |
+
<!-- [More Information Needed] -->
|
182 |
|
183 |
## Dataset Card Contact
|
184 |
|
185 |
+
<!-- [More Information Needed] -->
|
186 |
+
- [@abhi1505](https://huggingface.co/abhi1505)
|
187 |
+
- [@ccm](https://huggingface.co/ccm)
|
188 |
+
|