roystgnr

Well, the error is correct, at least! There's no 22 in our switch statement there. http://victorsndvg.github.io/FEconv/formats/unv.xhtml seems to imply that we could interpret that as a libMesh EDGE3? If so...

Hmm... reading further at that link, the "Local order of nodes" section makes me think you'd want to try 0,2,1 first.

It'd be ideal to have an FE type for side-defined quantities. (Probably two types while we're at it; there are other use cases where you want the quantities to be...

Not sure how the discussion didn't make it into this ticket, but for future reference/archival: This would be fairly easy to do in cases where users are only going to...

Something from @friedmud that should go here: > sub-app meshes staying in sync with master app meshes > > Remember when we were trying to find an example of why...

We're not going to go with a "one mesh, but you call reposition(displacement_vector) to change its state" idea, because of the ease of leaving something in a bad state in...

What are our "mesh operations" that need to be kept perfectly synced: 1. Partitioning 2. AMR changes - which would ideally be able to go both ways, for use with...

Yeah, that was no joke. This is going to cost memory (unless we make it disableable at configure time, which might be a good long-term goal but adds too much...

> Without shadowing at the Elem level, how do you simplify the synchronization of ghosting for example? Every function doing ghosting has (or at least could be easily given) a...

> By extension, we also want to be adding the ability to synchronize DofMap operations Which ones, and how? Does every variable on every system on the primary mesh have...