Exodus reader not applying displacements to meshes for 2d data.
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
To quote my user and Dave's reply,
It seems that with the new reader, the displacements are not applied to the mesh when that option is selected. This happens for 2D data (quad4 elements) but not for 3D hex8 elements, which are displaced appropriately. Was there any change in the logic detecting the displacement variable in the new reader? Yes, the way patterns in variable names are detected and turned from a set of scalars into a single vector has changed. I can see what's wrong and should have a fix later this afternoon; it would still be nice to have a sample file to test with, though. Alan should be bugging you about that and about the priority of the problem. The displacement variable is called DISPL{X,Y,Z} by ALEGRA, but the velocity has an underscore, VELOCITY_{X,Y,Z}. As far as the reader is concerned, only the first 3 characters and the last one character of the variable name are examined when searching for displacement vectors. In general, a set of consecutively stored variables with the same name that differ only by a trailing X, Y, and Z are turned into vectors. I'll fix that so that Z is not required when the coordinate dimension is 2.