David Wells [Sun, 14 Feb 2016 14:40:15 +0000 (09:40 -0500)]
Update the results for step-18.
This commit updates the discussion (we no longer have to rewrite
makefiles), the timing values (happily, the program runs about 20x
faster now than when these results were recorded at some point in the
past, which most likely in 2002-2005 based on the mention of the
Athlon XP processor), and the output files from the simulation.
Timo Heister [Sun, 14 Feb 2016 16:02:06 +0000 (11:02 -0500)]
fix eager Assertion in DoFAccessor
TriaRawIterator constructs a DoFAccessor with NULL as the Triangulation, see
include/deal.II/grid/tria_iterator.templates.h:71
so the new Assert introduced in #2179 triggers.
Timo Heister [Sun, 14 Feb 2016 15:15:33 +0000 (10:15 -0500)]
fix cmake 3.3 warning about code-gallery.h
cmake 3.3 will warn about CMP0058 and is unable to compile the documentation
when using Ninja:
This project specifies custom command DEPENDS on files in the build tree
that are not specified as the OUTPUT or BYPRODUCTS of any
add_custom_command or add_custom_target:
doc/doxygen/code-gallery/code-gallery.h
We have to jump through a few hoops to make this work: Generating a
dependency to a source file generated in a subdirectory CMakeLists.txt
requires a custom command attached to a custom_target. Because ADD_DEPENDENCIES
only allows custom_targets not custom_commands, we have to add another dummy.
Timo Heister [Sun, 14 Feb 2016 13:47:14 +0000 (08:47 -0500)]
suppress more warnings in external libs
this suppresses:
/ssd/libs-candi/trilinos-12.4.2-Source/include/Amesos2_Superludist_FunctionMap.hpp:285:17: warning: comparison of constant 67 with expression of type 'SLUD::DiagScale_t' is always false [-Wtautological-constant-out-of-range-compare]
char eq = AMESOS2_SLUD_GET_EQUED(*equed);
and
/ssd/libs-candi/trilinos-12.4.2-Source/include/Tpetra_Experimental_BlockCrsMatrix_def.hpp:2826:3: warning: all paths through this function will call itself [-Winfinite-recursion]
Spencer Patty [Thu, 11 Feb 2016 21:51:08 +0000 (15:51 -0600)]
add a test associated with the perturbed vertices changes that calls GridTools::distort_random on the triangulation and then runs the same test as in tests/grid/build_triangulation_from_patch_01.cc
danshapero [Thu, 11 Feb 2016 22:10:22 +0000 (14:10 -0800)]
Factored out repeated code in interpolated grid data
InterpolatedTensorProductGridData has some repeated code for finding
the right table index for an input point when computed the value or
gradient; this has been factored out into a protected member function
and the member data have been made protected instead of private for
ease of extension.
Timo Heister [Thu, 11 Feb 2016 19:26:51 +0000 (14:26 -0500)]
update graphical output in examples
- switch from gmv to vtu in several places
- format numbers in filenames with leading zeros
- vector output in step-20
- step-29: enable some debug output
Timo Heister [Wed, 10 Feb 2016 18:09:04 +0000 (13:09 -0500)]
disable gcc warning
In file included from /usr/include/c++/4.8/cassert:43:0,
from /ssd/libs-
candi/boost_1_60_0/include/boost/property_tree/detail/json_parser/narrow_encoding.hpp:6,
from /ssd/libs-
candi/boost_1_60_0/include/boost/property_tree/detail/json_parser/read.hpp:14,
from /ssd/libs-
candi/boost_1_60_0/include/boost/property_tree/json_parser.hpp:16,
from /ssd/deal-git/source/base/parameter_handler.cc:26:
/ssd/libs-
candi/boost_1_60_0/include/boost/property_tree/detail/json_parser/narrow_encoding.hpp:
In member function ‘char
boost::property_tree::json_parser::detail::utf8_utf8_encoding::to_internal_trivial(char)
const’:
/ssd/libs-
candi/boost_1_60_0/include/boost/property_tree/detail/json_parser/narrow_encoding.hpp:71:25:
warning: comparison is always true due to limited range of data type
[-Wtype-limits]
assert(c <= 0x7f);
Timo Heister [Mon, 8 Feb 2016 14:20:18 +0000 (09:20 -0500)]
fix several scary MPI bugs
I am surprised the code in question used to work at all because we are just
overwriting random memory. I detected those using clang's argument type
warnings and extensible clang type annotation within MPICH.
Timo Heister [Fri, 5 Feb 2016 14:53:41 +0000 (09:53 -0500)]
fix metis tests
On my machine with 64bit ints and 32bit metis I am getting the 32bit results
and so the tests fail. Fix this by always comparing against all possible
outputs. Also include additional output for metis_04.