Add "locally_refine" mesh building option
The alligator wants to eat the bigger number

Fix for greater-than vs less-than typo in locally_refine option
More locally_refine fixes

Infinite loop fixed, and we now interpret -1 as 0 rather than
uint(-1).
Add locally_refine_regression.sh test
Rename locally_refine -> locally_h_refine

Some forwards compatibility for future p refinement
Merge pull request #107 from grinsfem/locally_refine

Locally refine
Use tar-pax format

GNU docs say the format is "new" but was standardized in 2001.

With the older tar-ustar format, we were failing "make distcheck"
thanks to a 100+-character regression test filename that would end up
omitted (silently!?!) from the dist tarballs.  We could rename our
long-named tests, but doxygen seems to like generating huge filenames
from huge class names and I don't want to risk future equally-subtle
bugs.
Merge pull request #108 from grinsfem/tar-pax

Use tar-pax format
[GRINS]: fixing typo: 'steppping'-->'stepping'
Merge pull request #111 from nicholasmalaya/typo

[GRINS]: fixing typo: 'steppping'-->'stepping'
Don't overlap makefile target with directory name

This fixes the "can't do make dist without doxygen running" bug
Update regression value

The previous value was generated with a buggy libMesh version; the new
value (off by ~2%) was generated with a fixed version.
Merge pull request #112 from grinsfem/LMCB_regression

Update regression value
Fix libMesh header inclusions

There seems to have been a libMesh header change (include replaced
with forward declaration?) which broke GRINS; this fixes that, and
removes error_estimator.h inclusion from files that don't use it.
Merge pull request #113 from grinsfem/header_tweaks

Fix libMesh header inclusions
Add base_velocity option to velocity_penalty
Merge pull request #114 from grinsfem/base_velocity

Add base_velocity option to velocity_penalty
Add mesh-options/redistribute option
Turn off viz output from test
Disable redistributing higher order nodes

This kills this feature if we're trying to do "fancy" higher order
geometric elements like the non-full-order types or the 3rd+ order
types, or if we're trying to fit curved boundaries... but it also is
necessary to make the feature usable in the first place with 2nd order
geometric elements.