Add DofMap::(un)stash_dof_constraints()

Adjoint-based sensitivity calculations can require us to calculate
residuals without applying constraints, and this seems to be the least
modularity-defiling way to let us turn them off and back on quickly.
adjoint_qoi_sensitivity bugfix for adjoint BCs

With heterogeneous adjoint BCs we can't constrain the residual vector
and still expect to accurately calculate adjoint-weighted residuals
with a dot product.
Fix lift_func errors in adjoint qoi sensitivity

Choosing the right BCs and not making a sign error might be helpful...
Use API properly

enforce_constraints_exactly took a pointer to allow for a default
NULL; but enforce_adjoint_constraints exactly takes a reference...
has_heterogenous_adjoint_constraint changes

New method has_heterogenous_adjoint_constraints tests for any such
constraints.

Old method has_heterogenous_adjoint_constraint new returns the
constraint rhs Number rather than bool; this should be semantically
backward-compatible with the old system unless someone was manually
setting a zero constraint and expecting that to count as heterogenous.
Integrate regularized flux QoIs in FEMSystem
FEMSystem integration of heterogeneous qoi_deriv

This is consistent with the new assemble_qoi behavior
Selectively apply liftfunc and constraints

We need the liftfunc terms to be left out of the RHS for adjoint
solves; we need QoI derivative vectors to be left unconstrained when
using them for dot products in sensitivity calculations.
Parallel constraint calculation on SerialMesh too

This will hopefully be a speedup for everybody, but more importantly
it should fix a bug where FEMFunctionBase boundary conditions could
not be used on a SerialMesh on more than one processor.
Comment clarifying a libmesh_error()

I'm choosing to make the SerialMesh behavior less robust here in order
to catch inefficient SerialMesh usage even when that usage isn't
technically incorrect.  We might want to make the error test more
complicated and change this error to a debug-mode warning in the
future.
Only send_receive nodes when we need to

With a serialized mesh sending nodes redundantly is inefficient; with
a synchronized SerialMesh doing so is currently an error.
Allow the user to limit point locator searches to subsets of the mesh.

We have an application where a requested point lives on the interface between subdomains, and it is desirable to restrict which subdomain the returned element belongs to. This commit implements this feature, with backwards compatibility through the API using default function arguments.
vector_as_adjoint changes

Change name to vector_is_adjoint; anybody using this API probably
should be paying attention to this commit anyways.

Fix default vector behavior: handle projections with primal rather
than adjoint BCs.  I'm not sure why this took so long to trigger a
regression anywhere; are we doing a redundant constraint application
with the correct rhs after projections?
Ran bootstrap.

I guess Automake didn't agree with the way I fixed a conflict while
merging the cutcell quadrature branch.  Hopefully it's happy now.
Replace use of mkstemps with mkstemp to accomodate glibc < 2.11
Merge pull request #356 from libMesh/always_parallel_constraints

Parallel constraint calculation on SerialMesh too
Merge pull request #362 from dschwen/mkstemps

Replace use of mkstemps with mkstemp to accomodate glibc < 2.11
Merge pull request #358 from libMesh/set_adjoint_fix

vector_as_adjoint changes
Fix a bug Vikram caught in FEMSystem qoi derivs
Update references

* Cetin, 2014
* Simunovic, 2014
* Tonks, 2014
* Xiang, 2013
* Metaxa, 2013
* Laird, 2013
* Wieme, 2013
* Biermann, 2013
* Barker, 2013
* Use 1-inch margins