Simulator programs and utilities for automatic differentiation.

Andreas Lauser b93a61fd38 make the property system work with multiple compile units ... so far, the linker bailed out due to duplicate definitions of variables if multiple compile units used the same type tag. This is problematic if the sources are split into separate compile units and that use the same type tag; in particular, this applies for traditional libraries. Due to various C++ peculiarities, this patch complicates the internal implementation of the property system quite a bit, but given that the usage of it (as well as the compile time) stay unchanged, I do not consider this to be a big problem. Note that the introspection code is particularly problematic because it needs static initializers that do not cause the linker to choke in the case of multiple compile units. Finally, to prevent future regressions, this patch adds a unit test for the lens problem which uses multiple compile units. (This test is called lens_immiscible_ecfv_ad_mcu and basically identical to the existing lens_immiscible_ecfv_ad test and I thus think that it is pretty unimaginative -- improvement proposals are welcome.)		2017-09-03 15:27:35 +02:00
bin	relax the python script to check the reference solutions	2013-07-07 19:02:28 +02:00
doc	slightly improve the handbook build script	2017-01-16 15:32:16 +01:00
examples	make the property system work with multiple compile units	2017-09-03 15:27:35 +02:00
tests	remove the Stokes model	2017-07-21 21:38:13 +02:00