tbeltzun

**What is the requested feature?** `.hdf5` fields are currently written as a 1d stream of values. E.g. for an acoustic solver the nodal pressure field is three-dimensional, we thus loose...

reduce FEM (high order) initialization time

1

**What is the requested feature?** - identify initialization bottlenecks (CG FEM, wavePropagation); - propose alternatives. cc @sframba, opened to trace discussions.

**Describe the bug** ```bash $ geosx -m 0 -i .xml SIGFPE # triggered by log10(0) ```

add early check for invalid `toMetricPrefixString` input

3

Fix https://github.com/GEOS-DEV/GEOS/issues/2651. Use [`fpclassify`](https://en.cppreference.com/w/cpp/numeric/math/fpclassify) to avoid `-Werror=float-equal`.

The `MSG` argument fo the `LVARRAY_ERROR_IF` is useless when used on a GPU (device): https://github.com/GEOS-DEV/LvArray/blob/86af5bfb5204d94dd7b1f4bcf98a37b8de9a630c/src/Macros.hpp#L148 For example, the expression in https://github.com/GEOS-DEV/LvArray/blob/86af5bfb5204d94dd7b1f4bcf98a37b8de9a630c/src/ArraySlice.hpp#L56-L57 is printed as `Array Bounds Check Failed: index=

Don't know how this feasible, but it would be useful to recover a stacktrace from a function called from a GPU device in https://github.com/GEOS-DEV/LvArray/blob/bc43fa5f76174475e2f3f9af706e379350779244/src/Macros.hpp#L149