Panzer: Adding some comments to Constant evaluator
Merge branch 'master' of software:/space/git/Trilinos
MueLu: removed Navier2DBlocked_test.cpp nightly test

should be replaced by a new better one. Most of the code was a duplicate of
Navier2DBlocked_test2.cpp which covers the more interesting cases.
[Didasko] trailing whitespace
[Didasko] fix resource leaks
[Didasko] trailing whitespace
[Didasko] unitialized variables
[Didasko] trailing whitespace
[TriUtils] char *data_file ==> const char *data_file

Using a `const char*` as function argument allows char literals
as arguments.
Besides this change, this commit contains a bunch of indentation corrections
and replacement of conditional `exit(...)` calls by their TEUCHOS_EXCEPT*
equivalents.
[Didasko] unused variable

Build/Test Cases Summary
Enabled Packages: Didasko, Triutils
Disabled Packages: Pamgen,Intrepid
Enabled all Forward Packages
0) MPI_DEBUG => passed: passed=712,notpassed=0 (27.18 min)
1) SERIAL_RELEASE => passed: passed=659,notpassed=0 (5.46 min)
Other local commits for this build/test group: c50b58b, 2dd1a82, 7ecb66a, 8d28ec0, a69ab83, 7986d7a
[TriUtils] missing `const` decoration
Panzer: Exposing some private methods in Tpetra LOF
Merge branch 'master' of software:/space/git/Trilinos
MueLu: new nightly test (structural equations). not active yet
Merge branch 'master' of software:/space/git/Trilinos
Teuchos: TableFormat: Removed unused private variable.

I also took the chance to reorder the private fields in order to pack
the integers together and leave the array at the end.
Tpetra: CrsGraph: Removed unnecessary bool haveRowInfo_.

This commit affects both the "classic" and Kokkos refactor versions of
Tpetra.

The nonpublic bool haveRowInfo_ was always superfluous, for two reasons:

  1. Its value was always set to true.
  2. The hasRowInfo() method doesn't need haveRowInfo_
     in order to compute its return value.

This commit removes the superfluous variable.
Tpetra: CrsGraph: Fixed default domain & range Maps in fillComplete.

This commit affects both the "classic" and Kokkos refactor versions of
Tpetra.

Unlike CrsMatrix, CrsGraph did not check whether it already has domain
and range Maps, before setting the domain and range Maps to the row Map
in the zero- or one-argument versions of fillComplete.  This could cause
problems if fillComplete has already been called on the graph, but the
user wants to call resumeFill and fillComplete again.  Currently, the
latter requires that the user supply the graph's existing domain and
range Maps to fillComplete.  This is counterintuitive, because the graph
already _has_ domain and range Maps.

It is uncommon for users to call fillComplete twice on a graph, mainly
because CrsGraph does not currently allow changing a graph's column Map
once it has one.  However, if the user applies a local reordering using
the reindexColumns method, they must call resumeFill before and
fillComplete after.

This commit fixes CrsGraph::fillComplete so that the default domain Map
is only the row Map if the graph doesn't already have a domain Map, and
similarly for the range Map.
Galeri: Fixed build error (missing "std::")

Build/Test Cases Summary
Enabled Packages: Tpetra
Disabled Packages: Sacado,GlobiPack,OptiPack,FEI,RBGen,NOX,Moertel,Rythmos,MOOCHO
Enabled all Forward Packages
0) MPI_DEBUG => passed: passed=381,notpassed=0 (6.01 min)
1) SERIAL_RELEASE => passed: passed=333,notpassed=0 (0.55 min)
Other local commits for this build/test group: 0c64866, 7e91977, efcc23c
Kokkos: Fixed LayoutStride constructor was not working as intended.

LayoutStride construction with an order and dim array was not assigning
dimension correctly.

Here is an example of how it works and is intended too:
    const int rank = 4;
    const int order[] = { 1 , 3 , 2 , 0 };
    const unsigned dim[] = { dim0 , dim1 , dim2 , 3 };
    Kokkos::LayoutStride layout_stride = Kokkos::LayoutStride::order_dimensions( rank , order , dim );
    Kokkos::View<int****, Kokkos::LayoutStride> A("A",layout_stride);

"order" gives the order of dimensions from smallest stride to largest stride.
"dim" gives the logical dimensions of the view.

The following statements for example are all true:

 A.dimension_1()==dim1
 A.dimension_3()==3
 &A(k,l+1,m,n)-&A(k,l,m,n)==1
 &A(k,l+1,m+1,n)-&A(k,l,m,n)==1 + dim1*3
 &A(k+1,l+1,m+1,n)-&A(k,l,m,n)==1 + dim1*3 + 3*dim1*dim2
 &A(k,l,m,n+1)-&A(k,l,m,n)==dim1