Edit me

In KratosMultiphysics, boundary and initial conditions are typically imposed by means of Python classes extending the base Process class, which is implemented in the KratosCore. More details about the Process class can be found the dedicated documentation webpage and in the Kratos Crash Course. The parameters required by python processes must be defined in the "processes": {} section of the ProjectParameters.json file (more details about this input file can be found here).

In the MPMApplication, the following processes are implemented.

  • AssignGravityToMaterialPointProcess ( code) - Process assigning gravity to the material point elements of an MPM submodel part
  • AssignInitialVelocityToMaterialPointProcess ( code) - Process assigning an initial velocity to the material point elements of an MPM submodel part
  • Grid-based boundary conditions (or conforming/fitted boundary conditions) - Processes imposing boundary conditions on the nodes of a background grid submodel part
    • AssignVectorVariableProcess ( code) - Process implemented in the Kratos Core for assigning a value to the nodes of a model part and here used for imposing a zero displacement boundary condition
    • ApplyMPMSlipBoundaryProcess ( code) - Process imposing zero displacement in the direction orthogonal to the conditions of a background grid submodel part (no constraints in the tangent direction)
    • AssignVectorByDirectionToConditionProcess ( code) - Process implemented in the Kratos Core for assigning a vector value to the conditions of a model part and here used for imposing point, line and surface loads
  • Material Point-based boundary conditions (or non-conforming/unfitted boundary conditions) - Processes imposing boundary conditions by means of (moving) boundary material points