Closed akhoubani closed 1 year ago
@akhoubani This changes the ordering of elements as I understand. Did you double check with other Nek5000 setups that it works?
An alternate solution could be to keep the ordering that we had earlier (since there maybe an obscure user which relies on that order) and create an new element map capped with h.nb_elems_file
so the IndexError does not occur.
@akhoubani This changes the ordering of elements as I understand. Did you double check with other Nek5000 setups that it works?
I am unsure why pymech
should use elmap
to read data. I checked with some of my solvers, and it works fine.
If I remember correctly, the reason for ordering the elements with elmap
was that element orderings for the same mesh file were inconsistent between runs, especially when running on a different number of cores. In the past, I had tried to calculate the difference between two fields from different runs but with the same geometry, and got garbage because the element order was inconsistent.
This is something I could add a test for.
LGTM!
Fixes #48