``` are listed below:
- [coupled_solvers.feti_dynamic_coupled_solver](../Coupling_Strategy/Feti_Dynamic_Coupled_Solver.html)
### Coupling Sequence
-This part of the settings dictate the communication between the solvers used in the CoSimulation. The order of the solver executed will follow the order of the items inside the ```"coupling_sequence"``` field. Each item correspond to one solver. It has the ```name``` of the solver, the ```input_data_list``` and the ```output_data_list```.
+This part of the settings dictate the communication between the solvers used in the CoSimulation. The order of the solver executed will follow the order of the items inside the ```"coupling_sequence"``` field. Each item correspond to one solver. It has the ```name``` of the solver, the ```input_data_list``` and the ```output_data_list```.
The ```name``` field correspond on a solver naming that the user created in the ```"solvers"``` part of the solver settings. More details about how the solver is defined is explained [here](#solvers).
-The data to be transfered are managed in the ```input_data_list``` and ```output_data_list```. The ```input_data_list``` contains the data to be used for the current solver. On the other hand, the ```output_data_list``` contains the data from this solver to be sent to another solver.
+The data to be transfered are managed in the ```input_data_list``` and ```output_data_list```. The ```input_data_list``` contains the data to be used for the current solver. On the other hand, the ```output_data_list``` contains the data from this solver to be sent to another solver.
Each item inside ```"input_data_list"``` contain:
- ```"data"``` : variable of the input data.
@@ -188,8 +188,8 @@ In this part, the user define the solvers to be used for the CoSimulation. For c
- [solver_wrappers.kratos.convection_diffusion_wrapper](../Coupling_Operations/Convection-Diffusion.html)
- [solver_wrappers.kratos.dem_wrapper](../Coupling_Operations/DEM.html)
- [solver_wrappers.kratos.fluid_dynamics_wrapper](../Coupling_Operations/Fluid_Dynamics.html)
- - [solver_wrappers.kratos.particle_mechanics_dirichlet_wrapper](../Coupling_Operations/Particle_Mechanics_(Dirichlet).html)
- - [solver_wrappers.kratos.particle_mechanics_neumann_wrapper](../Coupling_Operations/Particle_Mechanics_(Neumann).html)
+ - [solver_wrappers.kratos.mpm_dirichlet_wrapper](../Coupling_Operations/MPM_Dirichlet.html)
+ - [solver_wrappers.kratos.mpm_neumann_wrapper](../Coupling_Operations/MPM_Neumann.html)
- [solver_wrappers.kratos.pfem_fluid_dynamics_wrapper](../Coupling_Operations/PFEM_Fluid_Dynamics.html)
- [solver_wrappers.kratos.potential_flow_wrapper](../Coupling_Operations/Potential_Flow.html)
- [solver_wrappers.kratos.structural_mechanics_wrapper](../Coupling_Operations/Structural_Mechanics.html)
@@ -270,7 +270,7 @@ The available ```"type"``` are listed below:
- [relative_norm_previous_residual](../Convergence_Criteria/relative_norm_previous_residual.html)
### Convergence Accelerators
-The convergence of the coupling strategy such as the strong coupling can be improved by using convergence accelerator.
+The convergence of the coupling strategy such as the strong coupling can be improved by using convergence accelerator.
```json
"convergence_accelerators" : [
{
@@ -288,7 +288,7 @@ The available convergence accelerators are listed below:
- [mvqn](../Convergence_Accelerators/MVQN.html)
### Predictors
-Predictors helps the solver by predicting the solution for the next timestep . It can be used both in a weak coupling and a strong coupling.
+Predictors helps the solver by predicting the solution for the next timestep . It can be used both in a weak coupling and a strong coupling.
The available predictors are listed below:
- [average_value_based](../Predictors/Average_Value_Based.html)
- [linear](../Predictors/Linear.html)
@@ -340,7 +340,7 @@ The operators that has been established here can be executed before or after tra
"solver" : "fluid",
"data_name" : "force"
},
- "Coupling_Operation_B" : {
+ "Coupling_Operation_B" : {
"type" : "impose_mesh_displacement",
"solver" : "fluid",
"data_name" : "disp"
diff --git a/docs/pages/Applications/CoSimulation_Application/General/Overview.md b/docs/pages/Applications/CoSimulation_Application/General/Overview.md
index 6fb4be5cd5cd..9bf7916e870f 100644
--- a/docs/pages/Applications/CoSimulation_Application/General/Overview.md
+++ b/docs/pages/Applications/CoSimulation_Application/General/Overview.md
@@ -1,24 +1,24 @@
---
title: Overview
-keywords:
+keywords:
tags: [Overview.md]
sidebar: cosimulation_application
-summary:
+summary:
---
## Overview
This application handles the interaction between two or more solver in a CoSimulation. Generally, the user can control which coupling strategy to be used, the order of solver to be executed, and how the data are transfered between the solvers. Each solver will have their own mesh file and their json file containing the solver's settings
-
+
A detailed explaination of the json structure can be found [here](../General/JSON_Structure.html)
The following solver wrappers are available:
-- [Convection-Diffusion](../Solver_Wrappers/Convection-Diffusion.html)
-- [DEM](../Solver_Wrappers/DEM.html)
-- [Fluid Dynamics](../Solver_Wrappers/Fluid_Dynamics.html)
-- [Particle Mechanics (Dirichlet)](../Solver_Wrappers/Particle_Mechanics_(Dirichlet).html)
-- [Particle Mechanics (Neumann)](../Solver_Wrappers/Particle_Mechanics_(Neumann).html)
-- [PFEM Fluid Dynamics](../Solver_Wrappers/PFEM_Fluid_Dynamics.html)
+- [Convection-Diffusion](../Solver_Wrappers/Convection-Diffusion.html)
+- [DEM](../Solver_Wrappers/DEM.html)
+- [Fluid Dynamics](../Solver_Wrappers/Fluid_Dynamics.html)
+- [MPM Dirichlet](../Solver_Wrappers/MPM_Dirichlet.html)
+- [MPM Neumann](../Solver_Wrappers/MPM_Neumann.html)
+- [PFEM Fluid Dynamics](../Solver_Wrappers/PFEM_Fluid_Dynamics.html)
- [Potential Flow](../Solver_Wrappers/Potential_Flow.html)
- [Rigid Body Solver](../Solver_Wrappers/Rigid_Body_Solver.html)
-- [Structural Mechanics](../Solver_Wrappers/Structural_Mechanics.html)
-- [SDOF Solver](../Solver_Wrappers/SDOF_Solver.html)
+- [Structural Mechanics](../Solver_Wrappers/Structural_Mechanics.html)
+- [SDOF Solver](../Solver_Wrappers/SDOF_Solver.html)
diff --git a/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/MPM_Dirichlet.md b/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/MPM_Dirichlet.md
new file mode 100644
index 000000000000..55fbc36823ba
--- /dev/null
+++ b/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/MPM_Dirichlet.md
@@ -0,0 +1,7 @@
+---
+title: MPM Dirichlet
+keywords:
+tags: [MPM_Dirichlet.md]
+sidebar: cosimulation_application
+summary:
+---
diff --git a/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/MPM_Neumann.md b/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/MPM_Neumann.md
new file mode 100644
index 000000000000..41ac53a01513
--- /dev/null
+++ b/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/MPM_Neumann.md
@@ -0,0 +1,7 @@
+---
+title: MPM Neumann
+keywords:
+tags: [MPM_Neumann.md]
+sidebar: cosimulation_application
+summary:
+---
diff --git a/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/Particle_Mechanics_(Dirichlet).md b/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/Particle_Mechanics_(Dirichlet).md
deleted file mode 100644
index 89d549046f87..000000000000
--- a/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/Particle_Mechanics_(Dirichlet).md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Particle Mechanics (Dirichlet)
-keywords:
-tags: [Particle_Mechanics_(Dirichlet).md]
-sidebar: cosimulation_application
-summary:
----
diff --git a/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/Particle_Mechanics_(Neumann).md b/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/Particle_Mechanics_(Neumann).md
deleted file mode 100644
index a7bd5b1a3cbd..000000000000
--- a/docs/pages/Applications/CoSimulation_Application/Solver_Wrappers/Particle_Mechanics_(Neumann).md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Particle Mechanics (Neumann)
-keywords:
-tags: [Particle_Mechanics_(Neumann).md]
-sidebar: cosimulation_application
-summary:
----
diff --git a/docs/pages/Applications/Particle_Mechanics_Application/Examples/Cylinder_on_inclined_plane.md b/docs/pages/Applications/MPM_Application/Examples/Cylinder_on_inclined_plane.md
similarity index 76%
rename from docs/pages/Applications/Particle_Mechanics_Application/Examples/Cylinder_on_inclined_plane.md
rename to docs/pages/Applications/MPM_Application/Examples/Cylinder_on_inclined_plane.md
index 02c163d59e36..0000e45fc53e 100644
--- a/docs/pages/Applications/Particle_Mechanics_Application/Examples/Cylinder_on_inclined_plane.md
+++ b/docs/pages/Applications/MPM_Application/Examples/Cylinder_on_inclined_plane.md
@@ -2,11 +2,11 @@
title: Cylinder on inclined plane 2D - comparison between analytical and numerical solution with MPM
keywords:
tags: [Cylinder_on_inclined_plane.md]
-sidebar: particle_mechanics_application
+sidebar: mpm_application
summary:
---
**Author:** Philip Franz\
-**Source files:** [cylinder_on_inclined_plane_2D](https://github.com/KratosMultiphysics/Examples/tree/master/particle_mechanics/validation/cylinder_on_inclined_plane/source)
+**Source files:** [cylinder_on_inclined_plane_2D](https://github.com/KratosMultiphysics/Examples/tree/master/mpm/validation/cylinder_on_inclined_plane/source)
## Case Specification
@@ -15,13 +15,13 @@ Linear, unstructured, triangular elements with a size of 0.01m are used to initi
However, in contrast to section 4.5.2 of (Iaconeta, 2019), the inclined plane is modelled by a line with unstructured elements with size 0.01m. On that line a non conforming Dirichlet boundary condition is imposed by using the penalty method based on (Chandra et al., 2021).
The following applications of Kratos are used:
-- [ParticleMechanicsApplication](https://github.com/KratosMultiphysics/Kratos/tree/master/applications/ParticleMechanicsApplication)
+- [MPMApplication](https://github.com/KratosMultiphysics/Kratos/tree/master/applications/MPMApplication)
- [LinearSolversApplication](https://github.com/KratosMultiphysics/Kratos/tree/master/applications/LinearSolversApplication)
The problem geometry as well as the boundary conditions are sketched below. The non conforming boundary condition is respresented by the copper coloured line.
- 
+ 
A hyper elastic Neo Hookean Plane strain (2D) constitutive law with unit thickness is considered with the following material parameters:
@@ -37,16 +37,16 @@ The contact between cylinder and inclined plane is modelled with the option "con
The analytical and numerical solution for the displacement function of the respective case of the above stated problem are compared afterwards:
- 
+ 
The left image displays the rolling cylinder - modelled with option "contact". The right one shows the sliding cylinder (frictionless) - modelled with option "slip".
- 
+ 
- 
+ 
diff --git a/docs/pages/Applications/Particle_Mechanics_Application/Examples/Granular_flow_2d.md b/docs/pages/Applications/MPM_Application/Examples/Granular_flow_2d.md
similarity index 81%
rename from docs/pages/Applications/Particle_Mechanics_Application/Examples/Granular_flow_2d.md
rename to docs/pages/Applications/MPM_Application/Examples/Granular_flow_2d.md
index bee283257665..c00a51153c9e 100644
--- a/docs/pages/Applications/Particle_Mechanics_Application/Examples/Granular_flow_2d.md
+++ b/docs/pages/Applications/MPM_Application/Examples/Granular_flow_2d.md
@@ -2,23 +2,23 @@
title: Granular Flow 2D Validation Test
keywords:
tags: [Granular_flow_2d.md]
-sidebar: particle_mechanics_application
+sidebar: mpm_application
summary:
---
**Author:** Bodhinanda Chandra\
-**Source files:** [granular_flow_2D](https://github.com/KratosMultiphysics/Examples/tree/master/particle_mechanics/validation/granular_flow_2D/source)
+**Source files:** [granular_flow_2D](https://github.com/KratosMultiphysics/Examples/tree/master/mpm/validation/granular_flow_2D/source)
## Case Specification
This is a 2D non-cohesive granular material simulation according to the experiment conducted by (Bui et al., 2008). Here, linear structured triangular elements are used to initialize the MPs and as the background mesh. The structured mesh arrangement is chosen to avoid the irregularities of the generated MP’s density, which, by further, improving the numerical solutions.
The following application of Kratos is used:
-- [ParticleMechanicsApplication](https://github.com/KratosMultiphysics/Kratos/tree/master/applications/ParticleMechanicsApplication)
+- [MPMApplication](https://github.com/KratosMultiphysics/Kratos/tree/master/applications/MPMApplication)
The problem geometry as well as the boundary conditions are sketched below:
- 
+ 
An elasto-plastic Mohr-Coulomb plane stress constitutive law with unit thickness is considered with the following material parameters:
@@ -36,7 +36,7 @@ The time step is 0.00005 seconds, while the total simulation time is 2.0 seconds
The problem stated above has been solved with a structured mesh with 3 material points per cell is considered with average mesh size of 0.002 m. The obtained numerical result is compared with experimental and simulation results conducted by (Bui et al., 2008) as depicted by the following figures:
- 
+ 
(a.) Experiment conducted by (Bui et al., 2008), (b.) comparison of final surface configuration and failure line, (c.) simulation results of (Bui et al., 2008) by using SPH method, (d.) simulation results obtained by implicit MPM method
diff --git a/docs/pages/Applications/Particle_Mechanics_Application/General/Overview.md b/docs/pages/Applications/MPM_Application/General/Overview.md
similarity index 72%
rename from docs/pages/Applications/Particle_Mechanics_Application/General/Overview.md
rename to docs/pages/Applications/MPM_Application/General/Overview.md
index 3920bc55d7e5..74acfe8ffd11 100644
--- a/docs/pages/Applications/Particle_Mechanics_Application/General/Overview.md
+++ b/docs/pages/Applications/MPM_Application/General/Overview.md
@@ -1,17 +1,14 @@
---
-title: Particle Mechanics Application
+title: MPM Application
keywords:
tags: [Overview.md]
-sidebar: particle_mechanics_application
+sidebar: mpm_application
summary:
---
-This application features continuum-based meshfree and particle methods with main motivations of simulating non-linear large deformable materials, such as free-surface flows, geomechanical phenomena, and extreme events involving impact, penetration, fragmentation, blast, multi-phase interaction, failure evolution, etc.
+This application implements the Material Point Method (MPM) with main motivations of simulating non-linear large deformable materials, such as free-surface flows, geomechanical phenomena, and extreme events involving impact, penetration, fragmentation, blast, multi-phase interaction, failure evolution, etc.
-
-
-
-The recent research and development have been focused solely on the Material Point Method (MPM) and on partiotioned coupled formulations MPM-FEM and MPM-DEM.
+
## Getting Started
@@ -24,7 +21,7 @@ Build Kratos and check the [configuration files](https://github.com/KratosMultip
In LINUX: check that in the /path_to_kratos/scripts/configure.sh the followinglines are written:
``` cmake
--DPARTICLE_MECHANICS_APPLICATION=ON
+-DMPM_APPLICATION=ON
-DLINEAR_SOLVERS_APPLICATION=ON
```
@@ -32,18 +29,17 @@ In WINDOWS: check that in the /path_to_kratos/scripts/configute.bat the followin
```set KRATOS_APPLICATIONS=
CALL :add_app %KRATOS_APP_DIR%\LinearSolversApplication;
-CALL :add_app %KRATOS_APP_DIR%\ParticleMechanicsApplication;
+CALL :add_app %KRATOS_APP_DIR%\MPMApplication;
```
-so the Particle Mechanics application is compiled along with auxiliary linear solvers required.
+so the MPM application is compiled along with auxiliary linear solvers required.
## Examples
-Some use-cases and validation examples are available in the Particle Mechanics section of the [Examples](https://kratosmultiphysics.github.io/Examples/) repository.\
-Also, some unit tests of the main features can be found in the [tests](https://github.com/KratosMultiphysics/Kratos/tree/master/applications/ParticleMechanicsApplication/tests) folder.
+Some use-cases and validation examples are available in the MPM section of the [Examples](https://kratosmultiphysics.github.io/Examples/) repository. Also, some unit tests of the main features can be found in the [tests](https://github.com/KratosMultiphysics/Kratos/tree/master/applications/MPMApplication/tests) folder.
**GiD Interface**
-A GiD user interface for the MPM application is also available. It is located in [GiD interface repository](https://github.com/KratosMultiphysics/GiDInterface/tree/master/).\
+A GiD user interface for the MPM application is also available. It is located in GiD interface repository in [GiD interface repository](https://github.com/KratosMultiphysics/GiDInterface/tree/master/).
It requires [GiD](https://www.gidhome.com/) - Pre and Post Processing software.
## Theory
@@ -52,20 +48,19 @@ Particle or meshfree methods are a category of methods where the state of a syst
**Material Point Method**
-The MPM is an hybrid thechnique which uses a fixed background grid (or mesh) for solving the governing equations in a FEM fashion and set of material particles (MP) for storing all the hystorical variables and material informations. MPM has gained a remarkably increasing popularity due to its capability in simulating problems involving historically dependent materials and large deformations. As MPM is able to combine the strengths of Eulerian and Lagrangian methods, it has been utilized in various engineering applications and industrial purposes, in particular in geomechanics and environmental fluid dynamics field.
+The MPM is an hybrid thechnique which uses a fixed background grid (or mesh) for solving the governing equations in a FEM fashion and set of material particles (MP) for storing all the hystorical variables and material informations. MPM has gained a remarkably increasing popularity due to its capability in simulating problems involving historically dependent materials and large deformations. As MPM is able to combine the strengths of Eulerian and Lagrangian methods, it has been utilized in various engineering applications and industrial purposes, in particular in geomechanics and environmental fluid dynamics field.
Recommended references for implementation details of MPM in Kratos:
-
- Singer, V.; Sautter, K.B., Larese, A., Wüchner, R.; Bletzinger, K.U.; A partitioned material point method and discrete element method coupling scheme, Advanced Modeling and Simulation in Engineering Sciences, 9(16), (2022); DOI: https://doi.org/10.1186/s40323-022-00229-5
-- Chandra, B., Singer, V., Teschemacher, T., Wuechner, R., & Larese, A. (2021). Nonconforming Dirichlet boundary conditions in implicit material point method by means of penalty augmentation. Acta Geotechnica, 16(8), 2315-2335.
+- Chandra, B., Singer, V., Teschemacher, T., Wuechner, R., & Larese, A. (2021). Nonconforming Dirichlet boundary conditions in implicit material point method by means of penalty augmentation. Acta Geotechnica, 16(8), 2315-2335. DOI: 10.1007/s11440-020-01123-3
- Wilson, P., Wüchner, R., & Fernando, D. (2021). Distillation of the material point method cell crossing error leading to a novel quadrature‐based C 0 remedy. International Journal for Numerical Methods in Engineering, 122(6), 1513-1537.
-- Iaconeta, I., Larese, A., Rossi, R., & Oñate, E. (2018). A stabilized mixed implicit Material Point Method for non-linear incompressible solid mechanics. *Computational Mechanics*, 1-18.
-- Iaconeta, I., Larese, A., Rossi, R., & Zhiming, G. (2016). Comparison of a material point method and a Galerkin meshfree method for the simulation of cohesive-frictional materials. *Materials*, 10(10), p. 1150.
+- Iaconeta, I., Larese, A., Rossi, R., & Oñate, E. (2018). A stabilized mixed implicit Material Point Method for non-linear incompressible solid mechanics. *Computational Mechanics*, 1-18. DOI 10.1007/s00466-018-1647-9
+- Iaconeta, I., Larese, A., Rossi, R., & Zhiming, G. (2016). Comparison of a material point method and a Galerkin meshfree method for the simulation of cohesive-frictional materials. *Materials*, 10(10), p. 1150. doi: 10.3390/ma10101150
## Features
-The following features are currently available and subject to development within the Particle Mechanics Application:
+The following features are currently available and subject to development within the MPM Application:
- Formulation:
* Irreducible formulations (U displacement based)
* Mixed UP formulations
@@ -91,10 +86,10 @@ The following features are currently available and subject to development within
* Neumann: Line load (a distributed load applied over a line)
* Neumann: Surface load (a distributed load applied over a face)
* Dirichlet: Slip and No slip condition on arbitrary boundary.
- * Particle-Based Conditions (non conforming): applied in moveable boundary particles
+ * Material Point-Based Conditions (non conforming): applied in moveable boundary particles
* Neumann: Moving point load
* Dirichlet: Imposition of displacements (homogeneous and inhomogeneous) using penalty method
-
+
- Strategies and schemes:
* Implicit - Newmark/Bossak prediction and correction scheme for static, quasi-static, and dynamic problems
* Explicit
@@ -102,11 +97,12 @@ The following features are currently available and subject to development within
- Other features:
* Partitioned coupling with Finite Element Method - weak and strong coupling of nonconforming discretization
* Partitioned coupling with the Discrete Element Method
- * Particle erase features - to delete particle outside the interest domain
+ * material point erase features - to delete material points outside the interest domain
+
## License
-The Particle Mechanics Application is OPEN SOURCE. The main code and program structure is available and aimed to grow with the need of any user willing to expand it. The BSD (Berkeley Software Distribution) licence allows to use and distribute the existing code without any restriction, but with the possibility to develop new parts of the code on an open or close basis depending on the developers.
+The MPM Application is OPEN SOURCE. The main code and program structure is available and aimed to grow with the need of any user willing to expand it. The BSD (Berkeley Software Distribution) licence allows to use and distribute the existing code without any restriction, but with the possibility to develop new parts of the code on an open or close basis depending on the developers.
## Contact
diff --git a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/calculation.md b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/calculation.md
similarity index 81%
rename from docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/calculation.md
rename to docs/pages/Applications/MPM_Application/MPM_example_in_GiD/calculation.md
index bb3efebc4539..b88c9c65f23a 100644
--- a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/calculation.md
+++ b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/calculation.md
@@ -2,17 +2,17 @@
title: Calculation
keywords:
tags: [Description.md]
-sidebar: particle_mechanics_application
+sidebar: mpm_application
summary:
---
## 4. Calculation
-By now, the setup of the model of the cantilever is complete. To calculate the displacement of the cantilever, click in the top toolbar on **`Calculate`→`Calculate`**, as shown in the image below.
+By now, the setup of the model of the cantilever is complete. To calculate the displacement of the cantilever, click in the top toolbar on **`Calculate`→`Calculate`**, as shown in the image below.
-Then the calculation of the problem is carried out. As already mentioned in the first paragraph, the calculation is done within the [KRATOS Multiphysics](https://github.com/KratosMultiphysics/Kratos) framework. More information on the material point method and its implementation within KRATOS is available under [ParticleMechanicsApplication](https://github.com/KratosMultiphysics/Kratos/tree/master/applications/ParticleMechanicsApplication).
+Then the calculation of the problem is carried out. As already mentioned in the first paragraph, the calculation is done within the [KRATOS Multiphysics](https://github.com/KratosMultiphysics/Kratos) framework. More information on the material point method and its implementation within KRATOS is available under [MPMApplication](https://github.com/KratosMultiphysics/Kratos/tree/master/applications/MPMApplication).
After the calculation, one can find in the project folder the following files (among others):
@@ -23,8 +23,8 @@ After the calculation, one can find in the project folder the following files (a
- project_name_Grid.mdpa
- project_name_Body.post.res
-- project_name_Grid.post.bin
+- project_name_Grid.post.bin
-The files *MainKratos.py*, *ProjectParamters.json*, *ParticleMaterials.json*, *project_name_Body.mdpa* and *project_name_Grid.mdpa* contain the data that is required for the calculation of the problem with KRATOS.
+The files *MainKratos.py*, *ProjectParamters.json*, *ParticleMaterials.json*, *project_name_Body.mdpa* and *project_name_Grid.mdpa* contain the data that is required for the calculation of the problem with KRATOS.
The last two files *project_name_Body.post.res* and *project_name_Grid.post.bin* contain essential results of the calculation and are used in the post-processing.
diff --git a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/introduction.md b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/introduction.md
similarity index 95%
rename from docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/introduction.md
rename to docs/pages/Applications/MPM_Application/MPM_example_in_GiD/introduction.md
index 2911ea4dd3e7..d82eb1b1b96d 100644
--- a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/introduction.md
+++ b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/introduction.md
@@ -2,7 +2,7 @@
title: Introduction
keywords:
tags: [introduction.md]
-sidebar: particle_mechanics_application
+sidebar: mpm_application
summary:
---
# MPM example in GiD
diff --git a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/menu_info.json b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/menu_info.json
similarity index 100%
rename from docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/menu_info.json
rename to docs/pages/Applications/MPM_Application/MPM_example_in_GiD/menu_info.json
diff --git a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/meshing.md b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/meshing.md
similarity index 99%
rename from docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/meshing.md
rename to docs/pages/Applications/MPM_Application/MPM_example_in_GiD/meshing.md
index 1b1354381895..4628ad7ece89 100644
--- a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/meshing.md
+++ b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/meshing.md
@@ -2,7 +2,7 @@
title: Meshing
keywords:
tags: [meshing.md]
-sidebar: particle_mechanics_application
+sidebar: mpm_application
summary:
---
diff --git a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/post_processing.md b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/post_processing.md
similarity index 78%
rename from docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/post_processing.md
rename to docs/pages/Applications/MPM_Application/MPM_example_in_GiD/post_processing.md
index 9477718541cf..81b6b3f6acde 100644
--- a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/post_processing.md
+++ b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/post_processing.md
@@ -2,7 +2,7 @@
title: Post processing
keywords:
tags: [post_processing.md]
-sidebar: particle_mechanics_application
+sidebar: mpm_application
summary:
---
@@ -12,32 +12,32 @@ When the calculation finished, examine the results in the post-processing mode o
-Then GiD automatically switches to its post-processing surface and loads the results file. Now, we can see the particles that we assigned to the domain of the cantilever in a previous step:
+Then GiD automatically switches to its post-processing surface and loads the results file. Now, we can see the material points that we assigned to the domain of the cantilever in a previous step:
-Often it is useful to compare the behaviour of the particles with the geometry of the background mesh. To add the background mesh to the post-processing, click on **`Files`→`Merge`** and select the file *project_name_Grid.post.bin* to open.
-
+Often it is useful to compare the behaviour of the material points with the geometry of the background mesh. To add the background mesh to the post-processing, click on **`Files`→`Merge`** and select the file *project_name_Grid.post.bin* to open.
+
-Then we can see the particles as well as the background domain.
+Then we can see the material points as well as the background domain.
-To adapt the depiction of the background mesh, we click in the right toolbar in the line of the backgroundmesh on the yellow quadrat that contains a black cross. Subsequently, another dropdown menu opens and we click on the first entry, as depicted in the image below.
+To adapt the depiction of the background mesh, we click in the right toolbar in the line of the backgroundmesh on the yellow quadrat that contains a black cross. Subsequently, another dropdown menu opens and we click on the first entry, as depicted in the image below.
-Now we can see the particles within the outer edges of the background mesh:
+Now we can see the material points within the outer edges of the background mesh:
-To see the deformation of the particles due to the dead load of the structure, one has to select the depiction of the displacement of the
-material points (particles). This is done by clicking on the following symbol and selecting **`MP Displacement`**.
+To see the deformation of the structure, one has to select the depiction of the displacement of the
+material points. This is done by clicking on the following symbol and selecting **`MP Displacement`**.
diff --git a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/set_up.md b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/set_up.md
similarity index 88%
rename from docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/set_up.md
rename to docs/pages/Applications/MPM_Application/MPM_example_in_GiD/set_up.md
index 8247d451f3c2..97c7af78adb0 100644
--- a/docs/pages/Applications/Particle_Mechanics_Application/MPM_example_in_GiD/set_up.md
+++ b/docs/pages/Applications/MPM_Application/MPM_example_in_GiD/set_up.md
@@ -2,12 +2,12 @@
title: Set up of example
keywords:
tags: [set_up.md]
-sidebar: particle_mechanics_application
+sidebar: mpm_application
summary:
---
## 2.Set up a Material Point Method problem in GiD
### 2.1 Load the MPM GUI
-The very first step is to open GiD. Then we need to load the Kratos GiD GUI. Therefore click on **`Data` → `Problem type` → `Kratos`** in the top toolbar. In the opening window, the Kratos Application Market, select then the **MPM** application.
+The very first step is to open GiD. Then we need to load the Kratos GiD GUI. Therefore click on **`Data` → `Problem type` → `Kratos`** in the top toolbar. In the opening window, the Kratos Application Market, select then the **MPM** application.
@@ -19,17 +19,17 @@ Following this, another window is going to appear where one has to choose the di
-In the sidebar with the title 'Particle mechanics' on the left, we can adjust different parameters for the solution of the problem. The most important are:
+In the sidebar with the title 'MPM' on the left, we can adjust different parameters for the solution of the problem. The most important are:
- **Solver Type:** Since the regarded problem is static, we select the corresponding solver type.
-- **Parts:** Within 'parts' the domains for the body mesh (particles) and the background grid are chosen and important parameters are defined. **Solid** contains the data for the body mesh; **Grid** the data for the background mesh.
+- **Parts:** Within 'parts' the domains for the body mesh (material points) and the background grid are chosen and important parameters are defined. **Solid** contains the data for the body mesh; **Grid** the data for the background mesh.
- **Boundary conditions:** Here we can assign Dirichlet boundary conditions to the problem domain.
- **Loads and other conditions:** In this section different types of loads and slip conditions can be defined.
### 2.2 Set up the example geometry
In our example we will regard a cantilever beam under gravity forces. As already mentioned above, we choose therefore the solver type **static**.
-To set up the geometry of the problem, two domains have to be defined: one for the background grid and one for the body domain. For that purpose we define at first the background domain. By clicking on the **create object**-icon and choosing a rectangle, we define the background domain. In the next step we define another, smaller rectangle that represents the cantilever.
+To set up the geometry of the problem, two domains have to be defined: one for the background grid and one for the body domain. For that purpose we define at first the background domain. By clicking on the **create object**-icon and choosing a rectangle, we define the background domain. In the next step we define another, smaller rectangle that represents the cantilever.
@@ -37,16 +37,16 @@ After clicking on the indicated button a menu opens. To create a rectangle click
-Now follow the instructions given in the command line:
+Now follow the instructions given in the command line:
-We create two rectangles by entering the coordinates of the left lower and the right upper corner point in the command line. We enter the coordinates in the format shown in the image above and confirm them by pressing **`Enter`**. The first rectangle that is going to represent the background domain has its corner points at **(0,0)** and **(5,2)**. The second one that represents the cantilever has its corner points at **(0, 0.5)** and **(5,1.5)**. Now the geometry should be
+We create two rectangles by entering the coordinates of the left lower and the right upper corner point in the command line. We enter the coordinates in the format shown in the image above and confirm them by pressing **`Enter`**. The first rectangle that is going to represent the background domain has its corner points at **(0,0)** and **(5,2)**. The second one that represents the cantilever has its corner points at **(0, 0.5)** and **(5,1.5)**. Now the geometry should be
displayed in GiD's main window as in the picture below:
-Subsequently, we assign the geometries to the different domains, choose element formulations and specify the material parameters of the structures. We start with the body structure. Click on **`Solid`**, then a menu opens above the command line.
+Subsequently, we assign the geometries to the different domains, choose element formulations and specify the material parameters of the structures. We start with the body structure. Click on **`Solid`**, then a menu opens above the command line.
@@ -57,23 +57,23 @@ Then we have to assign the data that we just entered to a domain of our problem.
-With the mouse that has now a different cursor, a little quadrat with a smaller quadrat inside, click on the purple rectangle that lies within the area of the 'cantilever-rectangle'. After clicking on it, this inner purple line should change its color to red, as indicated in the image below.
+With the mouse that has now a different cursor, a little quadrat with a smaller quadrat inside, click on the purple rectangle that lies within the area of the 'cantilever-rectangle'. After clicking on it, this inner purple line should change its color to red, as indicated in the image below.
Then leave the selection of areas by clicking **`ESC`** and confirm your choice by clicking **`OK`**. The same procedure we repeat with the 'background rectangle'. We start by clicking on **`Grid`**. In the opening menu we click on **`Select`** and choose now the inner purple rectangle of the 'background rectangle'. Then we hit **`ESC`** and confirm our choice by clicking **`OK`**. Now we assigned element formulations, material parameters and the domains to our problem geometry. In the next step we will deal with the boundary conditions.
### 2.2 Definition of the boundary conditions
-The cantilever has a fixed support on the left. So we set there all displacements permanently to 0. On the right side, the cantilever can deflect freely, so we assign there a slip condition. To impose the Dirichlet boundary condition on the left side, we click on **`Boundary Conditions` → `Displacements`**.
+The cantilever has a fixed support on the left. So we set there all displacements permanently to 0. On the right side, the cantilever can deflect freely, so we assign there a slip condition. To impose the Dirichlet boundary condition on the left side, we click on **`Boundary Conditions` → `Displacements`**.
-Afterwards, a new menu opens above the command line. Here we choose, as already indicated in the picture, line conditions. We click again on **`Select`** and choose the left edge of the large rectangle. This edge changes its color from blue to red, then we end the selection by hitting **`ESC`** and clicking **`OK`**.
+Afterwards, a new menu opens above the command line. Here we choose, as already indicated in the picture, line conditions. We click again on **`Select`** and choose the left edge of the large rectangle. This edge changes its color from blue to red, then we end the selection by hitting **`ESC`** and clicking **`OK`**.
-To assign a slip condition on the right side of the background rectangle, click on **`Loads and other conditions`→`Slip`**. Then select the right edge of the background rectangle in the same way as we selected the left edge. Now we imposed all the necessary boundary conditions on the example problem. Note, that the boundary conditions were imposed in this case on the background mesh. In MPM it is also possible to impose boundary conditions on the body mesh.
+To assign a slip condition on the right side of the background rectangle, click on **`Loads and other conditions`→`Slip`**. Then select the right edge of the background rectangle in the same way as we selected the left edge. Now we imposed all the necessary boundary conditions on the example problem. Note, that the boundary conditions were imposed in this case on the background mesh. In MPM it is also possible to impose boundary conditions on the body mesh.
### 2.3 Application of Loads
diff --git a/docs/pages/Applications/Particle_Mechanics_Application/menu_info.json b/docs/pages/Applications/MPM_Application/menu_info.json
similarity index 66%
rename from docs/pages/Applications/Particle_Mechanics_Application/menu_info.json
rename to docs/pages/Applications/MPM_Application/menu_info.json
index bf7283d558b8..9bd46e52cd32 100644
--- a/docs/pages/Applications/Particle_Mechanics_Application/menu_info.json
+++ b/docs/pages/Applications/MPM_Application/menu_info.json
@@ -1,8 +1,8 @@
{
- "side_bar_name": "particle_mechanics_application",
+ "side_bar_name": "mpm_application",
"landing_page": "General/Overview.md",
"additional_menu_options": {
- "product": "Particle Mechanics Application",
+ "product": "MPM Application",
"title": "sidebar"
},
diff --git a/kratos/KratosMultiphysics-all.json b/kratos/KratosMultiphysics-all.json
index 08004def2265..4452382cec67 100644
--- a/kratos/KratosMultiphysics-all.json
+++ b/kratos/KratosMultiphysics-all.json
@@ -15,7 +15,7 @@
"KratosLinearSolversApplication==${KRATOS_VERSION}",
"KratosMappingApplication==${KRATOS_VERSION}",
"KratosMeshingApplication==${KRATOS_VERSION}",
- "KratosParticleMechanicsApplication==${KRATOS_VERSION}",
+ "KratosMPMApplication==${KRATOS_VERSION}",
"KratosPoroMechanicsApplication==${KRATOS_VERSION}",
"KratosShallowWaterApplication==${KRATOS_VERSION}",
"KratosStructuralMechanicsApplication==${KRATOS_VERSION}",
diff --git a/scripts/wheels/linux/configure.sh b/scripts/wheels/linux/configure.sh
index d5e7043eb892..1ab694dbf3e3 100644
--- a/scripts/wheels/linux/configure.sh
+++ b/scripts/wheels/linux/configure.sh
@@ -25,7 +25,7 @@ add_app ${KRATOS_APP_DIR}/StructuralMechanicsApplication
add_app ${KRATOS_APP_DIR}/FluidDynamicsApplication
add_app ${KRATOS_APP_DIR}/DEMApplication
add_app ${KRATOS_APP_DIR}/ContactStructuralMechanicsApplication
-add_app ${KRATOS_APP_DIR}/ParticleMechanicsApplication;
+add_app ${KRATOS_APP_DIR}/MPMApplication;
add_app ${KRATOS_APP_DIR}/ConvectionDiffusionApplication;
add_app ${KRATOS_APP_DIR}/DamApplication;
add_app ${KRATOS_APP_DIR}/PoromechanicsApplication;
diff --git a/scripts/wheels/linux/configure_mpi.sh b/scripts/wheels/linux/configure_mpi.sh
index f3e3cd403da7..62d8a1cf2471 100644
--- a/scripts/wheels/linux/configure_mpi.sh
+++ b/scripts/wheels/linux/configure_mpi.sh
@@ -26,7 +26,7 @@ add_app ${KRATOS_APP_DIR}/StructuralMechanicsApplication
add_app ${KRATOS_APP_DIR}/FluidDynamicsApplication
add_app ${KRATOS_APP_DIR}/DEMApplication
add_app ${KRATOS_APP_DIR}/ContactStructuralMechanicsApplication
-add_app ${KRATOS_APP_DIR}/ParticleMechanicsApplication;
+add_app ${KRATOS_APP_DIR}/MPMApplication;
add_app ${KRATOS_APP_DIR}/ConvectionDiffusionApplication;
add_app ${KRATOS_APP_DIR}/DamApplication;
add_app ${KRATOS_APP_DIR}/PoromechanicsApplication;
diff --git a/scripts/wheels/windows/configure.bat b/scripts/wheels/windows/configure.bat
index 363527e544c2..86e1c8dcc918 100644
--- a/scripts/wheels/windows/configure.bat
+++ b/scripts/wheels/windows/configure.bat
@@ -16,7 +16,7 @@ CALL :add_app %KRATOS_APP_DIR%\StructuralMechanicsApplication
CALL :add_app %KRATOS_APP_DIR%\FluidDynamicsApplication
CALL :add_app %KRATOS_APP_DIR%\DEMApplication
CALL :add_app %KRATOS_APP_DIR%\ContactStructuralMechanicsApplication
-CALL :add_app %KRATOS_APP_DIR%\ParticleMechanicsApplication;
+CALL :add_app %KRATOS_APP_DIR%\MPMApplication;
CALL :add_app %KRATOS_APP_DIR%\ConvectionDiffusionApplication;
CALL :add_app %KRATOS_APP_DIR%\DamApplication;
CALL :add_app %KRATOS_APP_DIR%\PoromechanicsApplication;
+ 