-
Notifications
You must be signed in to change notification settings - Fork 59
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Description Solid objects are currently only using simplex. This can be problematic since double contacts can occur at the junction of two triangles. This PR aims at introducing solid objects built from volume elements, which could solve this problem. The contact between particle and volume 3D object is not implemented yet. Only in the creation and the displacement. Testing A new test has been implemented. (volume_solid_object_displacement.cc) Documentation Old simulation parameters have been renamed. The center of rotation was being defined by 3 parameters. Subsection center of rotation and its three parameters (x, y and z) have been replaced by one parameter named center of rotation using a list of doubles. A new subsection solid surfaces need to be used when defining solid object in the parameter file. Co-authored-by: Audrey Collard-Daigneault <71884806+acdaigneault@users.noreply.github.com> Co-authored-by: Olivier Guévremont <guevremont.o@gmail.com> Co-authored-by: Bruno Blais <blais.bruno@gmail.com>
- Loading branch information
1 parent
6c4a9d0
commit 4207163
Showing
38 changed files
with
789 additions
and
485 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,25 @@ | ||
*********************************************** | ||
Discrete Element Method (DEM) | ||
*********************************************** | ||
The discrete element method (DEM) solver in Lethe is called ``lethe-particles`` and supports two-dimensional and three-dimensional simulations. In ``simulation_control``, the general simulation parameters (for example, time-step, end time, etc.) are defined. ``timer`` and ``test`` sections are used for timing the classes and functions, and testing the reproducibility of the results. In ``model_parameters``, we define the simulation models, including particle-particle and particle-wall contact models. ``lagrangian_physical_properties`` defines the physical properties of the particles and walls. Insertion information including the dimensions of the insertion box and insertion frequency is defined in the ``insertion_info`` section. In the ``floating_walls`` section, we can add flat walls to the simulation domain. ``mesh`` section defines the simulation triangulation and refinements. In the ``boundary_conditions`` section, we can define boundaries as outlets, or rotate or slide them. | ||
The discrete element method (DEM) solver in Lethe is called ``lethe-particles`` and supports two-dimensional and three-dimensional simulations. In ``simulation_control``, the general simulation parameters (for example, time-step, end time, etc.) are defined. ``timer`` and ``test`` sections are used for timing the classes and functions, and testing the reproducibility of the results. | ||
In ``model parameters``, we define the simulation models, including particle-particle and particle-wall contact models. ``lagrangian physical properties`` defines the physical properties of the particles and walls. | ||
Insertion information including the dimensions of the insertion box, insertion frequency, etc. are defined in the ``insertion info`` section. | ||
The``mesh`` section defines the simulation triangulation and refinements. | ||
In the ``DEM boundary conditions`` section, boundaries can be defined as outlets or they can get periodicity, rotation or translation. | ||
In the ``floating walls`` section, hyperplanes can be added to the simulation domain. | ||
In the ``solid objects`` section, surface meshes can defined and their motion can be controlled. | ||
|
||
.. toctree:: | ||
:maxdepth: 1 | ||
|
||
boundary_conditions | ||
floating_mesh | ||
floating_wall | ||
insertion_info | ||
lagrangian_physical_properties | ||
mesh | ||
model_parameters | ||
post-processing | ||
simulation_control | ||
solid_objects | ||
test | ||
timer |
Oops, something went wrong.