DUNE-project

Which makes it much easier to install for those running the current Debian stable distribution. Enjoy! Download from Debian wheezy-backports.

Which makes it much easier to install for those running the current Debian stable distribution. Enjoy! Download from Debian wheezy-backports.

Last weekend we switched our default build system. Instead of Autotools, CMake is now the default. We hope to lower the barrier to make changes to the build system, reduce configure and compile times, get less cluttered output, and use a more modern ... [More] system that is still actively developed. Support for Autotools is deprecated and will be removed after Dune 2.4. Pass --no-cmake to dunecontrol to force the use of Autotools. If no build directory is given make files, libraries and executables are in <module-dir>/build-cmake/ . Our CMake-related documentation can be found in the Dune user wiki: http://users.dune-project.org/projects/main-wiki/wiki/Using_cmake_to_build_your_DUNE_project A quick guide for the switch: http://users.dune-project.org/projects/main-wiki/wiki/Switching_to_CMake Please help improving Dune by testing the new build system. Report bugs, share success stories, and improve the documentation in the wiki! Our plan is to keep Autotools for the Dune 2.4 release and drop it for Dune 3.0. Once we dropped Autotools support, we are able to make major changes as we don't have to consider Autotools compatibility anymore. [Less]

Last weekend we switched our default build system. Instead of Autotools, CMake is now the default. We hope to lower the barrier to make changes to the build system, reduce configure and compile times, get less cluttered output, and use a more ... [More] modern system that is still actively developed. Support for Autotools is deprecated and will be removed after Dune 2.4. Pass --no-cmake to dunecontrol to force the use of Autotools. If no build directory is given make files, libraries and executables are in /build-cmake/ . Our CMake-related documentation can be found in the Dune user wiki: http://users.dune-project.org/projects/main-wiki/wiki/Using_cmake_to_build_your_DUNE_project A quick guide for the switch: http://users.dune-project.org/projects/main-wiki/wiki/Switching_to_CMake Please help improving Dune by testing the new build system. Report bugs, share success stories, and improve the documentation in the wiki! Our plan is to keep Autotools for the Dune 2.4 release and drop it for Dune 3.0. Once we dropped Autotools support, we are able to make major changes as we don't have to consider Autotools compatibility anymore. [Less]

The dune-grid-glue module for the coupling of Dune grids is now available in form of binary packages for Debian Testing/Jessie.

The dune-grid-glue module for the coupling of Dune grids is now available in form of binary packages for Debian Testing/Jessie.

On 22.-23.9.2014 twelve Dune developers gathered in Berlin for two days of discussion and planning of the future development of Dune. The agenda of the meeting is available, and there are detailed meeting minutes, thanks to Dominic. Possibly the ... [More] most relevant decision for users of Dune is in the release schedule. There will be a 2.4 release with various improvements and fixes before the end of the year. However, after that we will start to work on a 3.0 release which will include some more disruptive changes. The list includes Dropping the AutoTools build system, Removing the EntityPointer class, but making Entity objects copyable instead, Introducing per-module namespaces. See the meeting minutes for more details. [Less]

On 22.-23.9.2014 twelve Dune developers gathered in Berlin for two days of discussion and planning of the future development of Dune. The agenda of the meeting is available, and there are detailed meeting minutes, thanks to Dominic. Possibly the ... [More] most relevant decision for users of Dune is in the release schedule. There will be a 2.4 release with various improvements and fixes before the end of the year. However, after that we will start to work on a 3.0 release which will include some more disruptive changes. The list includes Dropping the AutoTools build system, Removing the EntityPointer class, but making Entity objects copyable instead, Introducing per-module namespaces. See the meeting minutes for more details. [Less]

A new version of the ALUGrid manager has been released. We have added many new features and improved the performance of the code. One important change is that it is no longer required to download and build a separate library to use ALUGrid. Instead ... [More] we have combined both the implementation and the bindings into a new dune module. To use DUNE-ALUGrid simply download the new module from the user wiki. Then add dune-alugrid either under "Suggests" or "Depends" in your dune.module file. Now simply run dunecontrol and everything should work as before. There are only a few things to keep in mind: We have removed the special grid types e.g. ALUGridConform. Instead the type of the grid is always of the form Dune::ALUGrid< dimgrid, dimworld, eltype, refinetype, communicator >. (where communicator has a default value). The values for eltype are cube,simplex and for refinetype> the values are conforming, nonconforming defined in the DUNE namespace. The GRIDTYPE defines can still be used as before. The define HAVE_ALUGRID will not work correctly anymore. Since DUNE-ALUGrid is now a dune module the correct name for the define is HAVE_DUNE_ALUGRID. This can produce some problems... Note that we will not be supporting older versions of ALUGrid anymore and the binding in dune-grid will be deprecated. New features and improvements include Conforming refinement for the 3D simplex grid Internal load balancing method based on a space filling curve, making DUNE-ALUGrid self contained also in parallel Bindings for fully parallel partitioners using zoltan. (metis is still supported as well) Complete user control of the load balancing Improved memory footprint A detailed description of all the new features and some more details concerning the inner workings of DUNE-ALUGrid can be found in the paper The DUNE-ALUGrid Module. This is the paper we would now ask everyone to cite when using the DUNE-ALUGrid module. [Less]

A new version of the ALUGrid manager has been released. We have added many new features and improved the performance of the code. One important change is that it is no longer required to download and build a separate library to use ALUGrid. Instead ... [More] we have combined both the implementation and the bindings into a new dune module. To use DUNE-ALUGrid simply download the new module from the user wiki. Then add dune-alugrid either under "Suggests" or "Depends" in your dune.module file. Now simply run dunecontrol and everything should work as before. There are only a few things to keep in mind: We have removed the special grid types e.g. ALUGridConform. Instead the type of the grid is always of the form Dune::ALUGrid< dimgrid, dimworld, eltype, refinetype, communicator >. (where communicator has a default value). The values for eltype are cube,simplex and for refinetype> the values are conforming, nonconforming defined in the DUNE namespace. The GRIDTYPE defines can still be used as before. The define HAVE_ALUGRID will not work correctly anymore. Since DUNE-ALUGrid is now a dune module the correct name for the define is HAVE_DUNE_ALUGRID. This can produce some problems... Note that we will not be supporting older versions of ALUGrid anymore and the binding in dune-grid will be deprecated. New features and improvements include Conforming refinement for the 3D simplex grid Internal load balancing method based on a space filling curve, making DUNE-ALUGrid self contained also in parallel Bindings for fully parallel partitioners using zoltan. (metis is still supported as well) Complete user control of the load balancing Improved memory footprint A detailed description of all the new features and some more details concerning the inner workings of DUNE-ALUGrid can be found in the paper The DUNE-ALUGrid Module. This is the paper we would now ask everyone to cite when using the DUNE-ALUGrid module. [Less]