Currently, we construct quad and hex meshes for DGMulti using a general VertexMappedMesh constructor. However, we assume constant geometric terms, which is only true of Cartesian (or parallelogram) quad/hex meshes.
This should be fixed by introducing a CartesianMesh type or an AffineMesh type parameter and restricting existing DGMulti Quad() and Hex() solvers to these meshes.
Currently, we construct quad and hex meshes for
DGMultiusing a generalVertexMappedMeshconstructor. However, we assume constant geometric terms, which is only true of Cartesian (or parallelogram) quad/hex meshes.This should be fixed by introducing a
CartesianMeshtype or anAffineMeshtype parameter and restricting existingDGMultiQuad()andHex()solvers to these meshes.