Closed mrbuche closed 1 week ago
Fixed in #134.
$ cargo run -qr -F profile -- mesh -i spheres_resolution_4.npy -o target/foo.inp --smooth automesh 0.1.10 Reading spheres_resolution_4.npy Done 7.246989ms Meshing target/foo.inp ⤷ Removed voxels 327.585084ms Element-to-node connectivity 284.005907ms Nodal coordinates 691.668606ms Renumbered nodes 85.932201ms Done 1.410858943s Smoothing target/foo.inp ⤷ Node-to-element connectivity 489.889089ms Node-to-node connectivity 5.430347083s Nodal hierarchy 846.394093ms Done 6.766705079s Writing target/foo.inp ⤷ Nodal coordinates 4.626956897s Element-to-node connectivity 3.780540771s Done 9.124938823s
@mrbuche
Just finished new timing results with automesh
version 0.0.10
Describe the bug
The calculation of the node-to-element connectivity appears to be much slower than other operations.
To Reproduce
Expected behavior
Appears to be $O(N^2)$ rather than $O(N)$, which is likely due to looping over the element-to-node connectivity within the loop over the node-to-element connectivity in order to populate it.
Additional context
Reproduce using this commit. The node-to-element connectivity is currently needed to calculate the node-to-node connectivity and the nodal hierarchy.