waLBerla merge requestshttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests2018-04-05T15:26:32+02:00https://i10git.cs.fau.de/walberla/walberla/-/merge_requests/93UBB boundary with equation parser2018-04-05T15:26:32+02:00Michael Kuronmkuron@icp.uni-stuttgart.deUBB boundary with equation parserThis feature was initially suggested by @stewart. It builds upon `lbm::UBB` to allow
```
Boundaries
{
Border
{
direction T;
walldistance -1;
ParserUBB { x 0.005*y; y 0; z 0; }
}
}
```
or even
```
...This feature was initially suggested by @stewart. It builds upon `lbm::UBB` to allow
```
Boundaries
{
Border
{
direction T;
walldistance -1;
ParserUBB { x 0.005*y; y 0; z 0; }
}
}
```
or even
```
Boundaries
{
Border
{
direction T;
walldistance -1;
ParserUBB { x 0.1*sin(t); y 0; z 0; }
}
}
```
instead of only
```
Boundaries
{
Border
{
direction T;
walldistance -1;
UBB { x 0.05; y 0; z 0; }
}
}
```
It is quite similar to `lbm::DynamicUBB`, except that it uses a configuration file parameter instead of a functor. Because the parser does have a slight performance overhead, we only calculate the velocity once and store it if the expression provided is not time-dependent.
This pull request also fixes a few typos in related files and modifies `lbm::DynamicUBB` to not require an `lbm::TimeTracker` if the velocity functor does not depend on time.Christian Godenschwagerchristian.godenschwager@fau.deChristian Godenschwagerchristian.godenschwager@fau.dehttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/92Add createConfiguration functions to pe_coupling boundaries2018-04-04T07:45:48+02:00Michael Kuronmkuron@icp.uni-stuttgart.deAdd createConfiguration functions to pe_coupling boundariesWhile it makes no sense to create these boundary types from a config file, `geometry::initBoundaryHandling` needs this function to be present for all boundary types in the boundary handling. I have a boundary handling that uses PE bounda...While it makes no sense to create these boundary types from a config file, `geometry::initBoundaryHandling` needs this function to be present for all boundary types in the boundary handling. I have a boundary handling that uses PE boundaries created for particles and no-UBB boundaries that come from a config file.Christoph RettingerChristoph Rettingerhttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/90[API] Fix implict/explict typos in pe::cr2018-03-27T09:52:47+02:00Michael Kuronmkuron@icp.uni-stuttgart.de[API] Fix implict/explict typos in pe::crImplicit and explict were consistently misspelled in !32. As it is unlikely that anybody actually uses the switchable integrators in production code, I decided to make this API-incompatible change now. This code has never been in a relea...Implicit and explict were consistently misspelled in !32. As it is unlikely that anybody actually uses the switchable integrators in production code, I decided to make this API-incompatible change now. This code has never been in a release version either.Sebastian EiblSebastian Eiblhttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/91Disable cuda tests on macOS nightly builds2018-03-21T16:14:34+01:00Michael Kuronmkuron@icp.uni-stuttgart.deDisable cuda tests on macOS nightly buildsFixes https://i10git.cs.fau.de/walberla/walberla/issues/53Fixes https://i10git.cs.fau.de/walberla/walberla/issues/53Christian Godenschwagerchristian.godenschwager@fau.deChristian Godenschwagerchristian.godenschwager@fau.dehttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/32Switchable integrator and contact resolution for DEM2018-03-21T11:59:31+01:00Michael Kuronmkuron@icp.uni-stuttgart.deSwitchable integrator and contact resolution for DEMSebastian EiblSebastian Eiblhttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/88Fix calling of parmetis2018-03-13T09:01:42+01:00Sebastian EiblFix calling of parmetisSebastian EiblSebastian Eiblhttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/81Replace boost filesystem, any and optional if available in standard library2018-02-26T11:43:13+01:00Michael Kuronmkuron@icp.uni-stuttgart.deReplace boost filesystem, any and optional if available in standard libraryHere is the next set of changes for #48. They are minor API changes, no worse than what !44 introduced a few months ago (which, by the way, wasn't even tagged _[API]_...). This is easily fixable with something like
```
find . -type f -e...Here is the next set of changes for #48. They are minor API changes, no worse than what !44 introduced a few months ago (which, by the way, wasn't even tagged _[API]_...). This is easily fixable with something like
```
find . -type f -exec sed -i \
-e 's/boost::filesystem/walberla::filesystem/g' -e 's/boost::any/walberla::any/g' \
-e 's/boost::optional/walberla::optional/g' {} +
```
The nice thing about this pull request is: when building without the Python interface, we now no longer depend on any boost libraries; we only need the headers. GCC's libstdc++ ships with the necessary stuff in `std::experimental` since version 5.0, Clang's libc++ does too since 4.0 and MSVC since 2015. Apple's Clang doesn't ship `filesystem` and marks `any` and `optional` as unavailable, so we fall back to Boost on it (and on other older compiler versions).Christian Godenschwagerchristian.godenschwager@fau.deChristian Godenschwagerchristian.godenschwager@fau.dehttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/79Require C++14 and CMake 3.12018-02-21T16:25:39+01:00Michael Kuronmkuron@icp.uni-stuttgart.deRequire C++14 and CMake 3.1First batch of changes for #48.
Fixes !42First batch of changes for #48.
Fixes !42Christian Godenschwagerchristian.godenschwager@fau.deChristian Godenschwagerchristian.godenschwager@fau.dehttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/86Fix argument order of calcInteria in Sphere constructor.2018-02-21T08:18:20+01:00Felix WinterhalterFix argument order of calcInteria in Sphere constructor.calcInertia of Sphere is called with the wrong argument order. The sphere moment of inertia is completely wrong.calcInertia of Sphere is called with the wrong argument order. The sphere moment of inertia is completely wrong.https://i10git.cs.fau.de/walberla/walberla/-/merge_requests/85Ellipsoid VTK output2018-02-12T16:25:32+01:00Christoph RettingerEllipsoid VTK outputhttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/44wrap regex2018-01-31T17:20:00+01:00Dominik Thoennesdominik.thoennes@fau.dewrap regexThis wraps regex functions (walberla::regex) to only use boost with IBM compilers and the std regex otherwise.
Boost regex often causes problems when boost was build with a different compiler version.This wraps regex functions (walberla::regex) to only use boost with IBM compilers and the std regex otherwise.
Boost regex often causes problems when boost was build with a different compiler version.Dominik Thoennesdominik.thoennes@fau.deDominik Thoennesdominik.thoennes@fau.dehttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/80fix MPIEXEC_PREFLAG2018-01-29T09:30:31+01:00Dominik Thoennesdominik.thoennes@fau.defix MPIEXEC_PREFLAGcurrently the oversubscribe flag is not always set. Using FORCE should solve the problemcurrently the oversubscribe flag is not always set. Using FORCE should solve the problemhttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/77Resolve "body filter to exclude bodies from PeVTKMeshWriter"2018-01-19T15:26:59+01:00Sebastian EiblResolve "body filter to exclude bodies from PeVTKMeshWriter"Closes #47Closes #47Christian Godenschwagerchristian.godenschwager@fau.deChristian Godenschwagerchristian.godenschwager@fau.dehttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/75Resolve "Rename setMass function"2018-01-18T22:09:41+01:00Sebastian EiblResolve "Rename setMass function"Closes #46Closes #46Sebastian EiblSebastian Eiblhttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/52Dynamic refinement for pe module2018-01-18T16:16:56+01:00Sebastian EiblDynamic refinement for pe moduleSebastian EiblSebastian Eiblhttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/76Reworked Body Mapping2018-01-18T15:48:30+01:00Christoph RettingerReworked Body MappingDue to ambiguities between the pe flags (global, communicating, infiniteMass), and the demands of the pe coupling (regular , fixed, global bodies), see also issue https://i10git.cs.fau.de/walberla/walberla/issues/30, the body mapping ins...Due to ambiguities between the pe flags (global, communicating, infiniteMass), and the demands of the pe coupling (regular , fixed, global bodies), see also issue https://i10git.cs.fau.de/walberla/walberla/issues/30, the body mapping inside the pe_coupling module has been completely reworked.
Most of the body mapping functions have been removed as they duplicated the functionality.
Only two functions per type (standard LBM boundary condition mapping and momentum exchange boundary condition mapping) remained: to map all bodies and to map a single body.
The user can specify with the help of a mapping body selector function which bodies should be mapped and which should be skipped.
Standard routines are provided: selectAllBodies, selectRegularBodies(not infinite mass and not global), selectFixedBodies(infinite mass and not global), selectGlobalBodies
The PDF restoration has also been updated to now also restore global and fixed body PDFs in all cases.
These changes have been incorporated in all test cases and applications.
An additional test case for the body mapping has been added.
Documentation has been added.
All isFixed() checks in the pe_coupling sources and test have been removed and, if considered necessary, adequately replaced.
The selector functions have also been added to the PSM body mapping. Thus, it is possible to use PSM and MEM coupling in the same simulation, given that specific selector functions are provided.
The selector functions have also been added to the discrete particle method evaluators. Thus, it will be possible to use fully resolved and DPM coupling in the same simulation. Some functionalities are however still missing (e.g. solid volume fraction mapping of the fully resolved particles to have a correct guess of the SVF for the empirical correlations and the GNS sweep).Christian Godenschwagerchristian.godenschwager@fau.deChristian Godenschwagerchristian.godenschwager@fau.dehttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/74WIP: Add openmesh and mesh module to conda python modules2018-01-16T02:44:38+01:00Christian Godenschwagerchristian.godenschwager@fau.deWIP: Add openmesh and mesh module to conda python modulesChristian Godenschwagerchristian.godenschwager@fau.deChristian Godenschwagerchristian.godenschwager@fau.dehttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/37Resolve "Add builds for GCC 7"2018-01-12T14:46:10+01:00Christian Godenschwagerchristian.godenschwager@fau.deResolve "Add builds for GCC 7"Closes #24Closes #24https://i10git.cs.fau.de/walberla/walberla/-/merge_requests/73Enable dynamic refinement for coupled LBM-PE simulations2018-01-10T09:18:55+01:00Christoph RettingerEnable dynamic refinement for coupled LBM-PE simulationsAdded some functionalities, useful for coupled simulations with dynamic refinement.
Added a settling sphere test case in three variants: Uniform grid, statically refined grid, dynamically refined grid.Added some functionalities, useful for coupled simulations with dynamic refinement.
Added a settling sphere test case in three variants: Uniform grid, statically refined grid, dynamically refined grid.Christoph RettingerChristoph Rettingerhttps://i10git.cs.fau.de/walberla/walberla/-/merge_requests/72Added discrete particle method coupling2018-01-09T16:41:47+01:00Christoph RettingerAdded discrete particle method couplingThis adds the discrete particle (i.e. subgrid) coupling method to waLBerla.
The algorithm is explained in detail in https://arxiv.org/abs/1711.00336 (to be published soon).
Two test cases are added that validate the algorithm (settling v...This adds the discrete particle (i.e. subgrid) coupling method to waLBerla.
The algorithm is explained in detail in https://arxiv.org/abs/1711.00336 (to be published soon).
Two test cases are added that validate the algorithm (settling velocities and bouncing behavior).
One showcase is added (bidisperse fluidized bed) to demonstrate the capabilities of the approach.Christoph RettingerChristoph Rettinger