Dylan Copeland

ping @tzanio

Thanks @JacobLotz for testing. As explained in the comment above https://github.com/mfem/mfem/pull/3648#discussion_r1383856167 the user has to know what refinement factors are valid for a particular spacing formula. It would be ideal...

It didn't take long to break the single precision build. We should put a build in the CI. This PR introduced `double` in `hypre.cpp`.

Is there an example mesh to illustrate what this PR fixes? A unit test would be ideal. If a unit test cannot be made easily, can you share some example...

I am not aware of anyone working on this issue since I posted in 2020, and I haven't worked on a related topic in recent years. This seems like a...

> Since this PR seems to be introducing a huge ABI-breaking change, would you guys consider adopting inline namespaces (for single vs. double precision) to avoid creating ABI-incompatibility headaches for...

Is there a way to disable the branch history check? It fails because too many files were committed.

All the CI tests are passing except windows. I'm not sure what to do about that.

> Can you merge in `master` and resolve conflicts please? Done, but there will be conflicts for this branch on every commit to `master`. This is a reason to expedite...

Thank you @nbeams for your suggestion. This PR was intended as a minimal introduction of single-precision in MFEM, but even the minimal case is very pervasive. In order to run...