Matthias Maier [Thu, 21 Aug 2014 17:10:48 +0000 (19:10 +0200)]
CMake: Remove all "help" targets
It turns out that CMAKE_PROPERTY is too buggy to be useful. We cannot
set property CMP0037 to the old behavior in order to define a custom "help"
target in a macro without a warning. o_O
Luca Heltai [Thu, 21 Aug 2014 13:28:37 +0000 (15:28 +0200)]
Merge pull request #103 from bangerth/move-functions
These functions were previously in GridTools, but conceptually they create
meshes and so should be in GridGenerator. Move them there but leave the
old functions in GridTools with a note that they are now deprecated.
Also structure the documentation of the functions in GridGenerator better.
Move create_union_triangulation() and extract_boundary_mesh().
These functions were previously in GridTools, but conceptually they create
meshes and so should be in GridGenerator. Move them there but leave the
old functions in GridTools with a note that they are now deprecated.
Also structure the documentation of the functions in GridGenerator better.
Matthias Maier [Thu, 21 Aug 2014 09:04:09 +0000 (11:04 +0200)]
Fix memory_consumption_01 for icc
The comparison file for compiler=Intel=yes was just invalid. Current icc
does not miscompile the test in release mode anymore. So remove all special
comparison files.
Matthias Maier [Thu, 21 Aug 2014 08:24:52 +0000 (10:24 +0200)]
Merge pull request #88 from guidokanschat/fe_from_name_codim_ready
FETools::get_fe_from_name() implemented for nonzero codimension
- Existing testbits/get_fe_from_name passes
- Modified all get_name functions to include the spacedim parameter. …
- Added one test for codimension one finite element generation from names.
- Reintroduce get_fe_from_name<dim>() with one template parameter as deprecated
- New function get_fe_by_name<dim,spacedim>()
Luca Heltai [Sat, 16 Aug 2014 16:47:09 +0000 (18:47 +0200)]
Modified all get_name functions to include the spacedim parameter.
Added one test for codimension one finite element generation from names.
Reintroduce get_fe_from_name<dim>() with one template parameter as deprecated
New function get_fe_by_name<dim,spacedim>()
Timo Heister [Wed, 20 Aug 2014 19:02:09 +0000 (15:02 -0400)]
Merge pull request #100 from bangerth/silence-warning-2
Silence a warning from gcc 4.9.1. The warning pertained to the fact that we define a function in an anonymous
namespace that is only called from a function inside an #ifdef ... #endif
block. The solution is to move the function into #ifdef ... #endif as well.
This addresses this test result: http://cdash.kyomu.43-1.org/viewBuildError.php?type=1&buildid=11683
I get an error of the form
/u/bangerth/p/deal.II/1/dealii/include/deal.II/meshworker/dof_info.h:69:9: runtime error: load of value 216, which is not a valid value for type 'bool'
when running the testsuite with the ASAN framework. This is caused by the DoFInfo
class having a member variable that is left uninitialized in the constructor.
Fix this.
The warning pertained to the fact that we define a function in an anonymous
namespace that is only called from a function inside an #ifdef ... #endif
block. The solution is to move the function into #ifdef ... #endif as well.
This addresses this test result: http://cdash.kyomu.43-1.org/viewBuildError.php?type=1&buildid=11683
Timo Heister [Wed, 20 Aug 2014 18:24:03 +0000 (14:24 -0400)]
Merge pull request #99 from bangerth/fix-test-signature
Rename output of tests that need PETSc, not Trilinos. The tests actually use PETSc, but their output names suggested that they need Trilinos. This was wrong.
Luca Heltai [Tue, 19 Aug 2014 13:35:24 +0000 (15:35 +0200)]
Merge pull request #94 from bangerth/silence-warning
Some newer compilers kept warning about an out-of-bounds array access
in Point::operator() but didn't indicate where exactly it came
from. This turned out to be in DataOutBase::write_eps(), a function
that is implemented only for dim==2 but was compiled also for dim==1
and dim==3 and contained this statement: 'pointsvertex'. The patch
reorganizes the code so that the function is only compiled for dim==2
and a more general specialization that does nothing but abort is used
for all other dimensions.
Some newer compilers kept warning about an out-of-bounds array access
in Point<1>::operator() but didn't indicate where exactly it came
from. This turned out to be in DataOutBase::write_eps(), a function
that is implemented only for dim==2 but was compiled also for dim==1
and dim==3 and contained this statement: 'points[vertex](1)'. The patch
reorganizes the code so that the function is only compiled for dim==2
and a more general specialization that does nothing but abort is used
for all other dimensions.
Add workaround to be able to use SLEPc >= 3.5.0 with deal.II. This requires disabling support for STFOLD spectrum transformation type since it was removed in SLEPc 3.5.0 and newer.
agrayver [Wed, 13 Aug 2014 12:40:48 +0000 (14:40 +0200)]
Fix bug in project_boundary_values_curl_conforming related to the wrong indexing of high-order DoFs in internals::compute_face_projection_curl_conforming.
This commit removes the obsolete support for a 'Nightly' track and adds a
new 'Continuous' track. The idea is that in future 'tester' uses
exclusively the 'Regression Test' track and simserv04 uses 'Continuous'.
Both testing sites have different strategies: tester goes through all
commits with one configuration (for 32 and 64 bit indices), simserv04 just
checks the latest merge available but for a number of compilers and
configuration. The current mix of test results is just confusing and very
horrible to read :-/
Matthias Maier [Fri, 8 Aug 2014 23:22:38 +0000 (01:22 +0200)]
Silence a warning
A logical construct of the form "EXPR && EXPR || EXPR" in manifold_lib.cc
triggered a bunch of warning. Silence them by explicitly enclosing the
intended precedence: (EXPR && EXPR) || EXPR.
Timo Heister [Fri, 8 Aug 2014 21:31:21 +0000 (17:31 -0400)]
Merge pull request #74 from guidokanschat/doxygen_steps_missing
Fix a bug in doxygen causing missing tutorials
The tutorial steps were missing in the online documentation.
This bug fix makes them reappear by creating the string of input directories and files only after the list has been competed.
Timo Heister [Thu, 7 Aug 2014 13:31:54 +0000 (09:31 -0400)]
Merge pull request #65 from bangerth/fix-muparser-if
Change the parsing of functions in muparser.
muparser requires that there be no space between the name of a function and its argument
list. This is incompatible to the behavior we had with fparser that allowed for spaces
in this position. To allow for backward compatible behavior, this patch changes the
parsing in such a way that it eats spaces after the function name for all built-in
and deal.II-defined functions before passing the expression to muparser.
This addresses bug #218 at https://code.google.com/p/dealii/issues/detail?id=218 .
Luca Heltai [Thu, 7 Aug 2014 13:04:09 +0000 (15:04 +0200)]
Merge pull request #63 from tamiko/fix_manifold_instantiations
This commit reverts the quick fix in commit 982b0683.
The issue why we encountered unresolved references to
dealii::FlatManifold::FlatManifold(dealii::Point, double)
etc. was due to boilerplate instantiations of Triangulation::get_manifold
for cases with spacedim < dim (in order to make TriaAccessor happy).
This commit fixes the issue by using a nullptr-dereference in order to
return an invalid object - the specific code throws an error message before
that and should actually not be reachable at all.
Matthias Maier [Thu, 7 Aug 2014 11:07:45 +0000 (13:07 +0200)]
Fix instantiation issue with FlatManifold properly
This commit reverts the quick fix in commit 982b0683.
This commit closes #56
The issue why we encountered unresolved references to
dealii::FlatManifold<3, 2>::FlatManifold(dealii::Point<2, double>, double)
etc. was due to boilerplate instantiations of Triangulation::get_manifold
for cases with spacedim < dim (in order to make TriaAccessor happy).
This commit fixes the issue by using a nullptr-dereference in order to
return an invalid object - the specific code throws an error message before
that and should actually not be reachable at all.