Internal:Ss missile comparison AFLR: Difference between revisions
Jump to navigation
Jump to search
| Line 141: | Line 141: | ||
| 100.058 | | 100.058 | ||
|} | |} | ||
== Comments == | |||
# Although CDT3D does not use alignment, it is not this that makes it faster (actually when alignment will be implemented, it is expected to make refinement even faster) | |||
# In CDT3D, we store the previous location in BG mesh, speeding up subsequent queries in the same neighborhood. | |||
# By design, the point insertion order in CDT3D takes advantage of the geometric locality and thus we take advantage of the spatial locality of the points For some reasongIn CDT3D, point location | |||
Revision as of 16:12, 14 September 2018
Quantitative
| Metric Complexity | # Vertices | # Elements | Time (s) | |
|---|---|---|---|---|
| Target | 80,000 | ~160,000 | ~960,000 | N/A |
| AFLR | 80,422.6 | 160,845 | 965,071 | 233.3 |
| CDT3D (1 thread) | 78,215.9 | 189,788 | 1,107,104 | 100.0 |
| CDT3D (6 threads) | 79,221.6 | 191,353 | 1,116,112 | 21.5 |
Qualitative
Time Breakdown
| Operations | details | AFLR (malign =ON) | AFLR(maling =OFF) |
|---|---|---|---|
| BG Mesh Initialization | 0.534 | 0.533 | |
| Point Creation | |||
| Euclidean length | 0.028 | 0.037 | |
| Riemannian length | 0.166 | 0.24 | |
| Metric interpolation at face | 0.302 | 0.408 | |
| Evaluate Log(Metric) | 1.902 | 0.272 | |
| Search in BG mesh | 137.825 | 334.594 | |
| Search point in mesh | 0.092 | 0.271 | |
| Metric-Alignment | 80.387 | 0 | |
| Point Creation Total | 219.759 | 336.881 | |
| Point Filtering | 2.373 | 2.412 | |
| Point Insertion | 0.154 | 0.184 | |
| Element Deactivation | 0.626 | 2.914 | |
| Local Reconnection 32-23 | 8.553 | 9.037 | |
| Local Reconnection 4-4 | 0 | 3.118 | |
| Total | 232.389 | 355.571 |
| Operations | CDT3D ( 1 thread ) |
|---|---|
| BG Mesh Initialization | 1.08535 |
| Deactivate Elements | 2.69843 |
| Point Creation | 8.54597 |
| Point Insertion | 0.25458 |
| Local Reconnection 3-2/2-3 | 64.4204 |
| Local Reconnection 4-4 | 22.4864 |
| Total | 100.058 |
Comments
- Although CDT3D does not use alignment, it is not this that makes it faster (actually when alignment will be implemented, it is expected to make refinement even faster)
- In CDT3D, we store the previous location in BG mesh, speeding up subsequent queries in the same neighborhood.
- By design, the point insertion order in CDT3D takes advantage of the geometric locality and thus we take advantage of the spatial locality of the points For some reasongIn CDT3D, point location