Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kelvin-Voigt Boundary Benchmark Case #20

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

cgeudeker
Copy link

Describe the PR
This is a benchmark case to test the Kelvin-Voigt boundary addition.

Related Issues/PRs
Kelvin-Voigt Boundary Implementation for #692

Additional context
General Notes: The mesh represents a 1m column loaded with 1000 rows and 6 cells in each row. The boundary conditions are 1 kN particle surface traction applied to the top, roller boundaries along the sides of the columns and the Kelvin-Voigt boundary at the base.

There are three different particle files with varying densities (6000, 24000, and 54000 particles). These files have associated with respective entity sets for the application of particle surface traction.

Also, in these files, the absorbing boundary and velocity constraint are both placed on the bottom corner nodes.

@jgiven100
Copy link
Contributor

@cgeudeker Thanks for uploading!

@jgiven100
Copy link
Contributor

@cgeudeker Couple thoughts:

  1. We might want to simplify these inputs to a single case (i.e., remove different particle densities)
  2. The 0.1 m model will run much faster as a benchmark and shows the same successful implementation
  3. Including an jupyter notebook that shows the displacement converges to the analytical value will be good (e.g., when \delta=0.1 diplacement converges to 0.0001 meters)

image

@jgiven100
Copy link
Contributor

@cgeudeker
After putting results in a jupyter notebook, numerical displacement is <0.5% relative error after only 30k steps; this seems pretty good to me. If you're ok with the all of the above changes, I can push the updates into your branch whenever!

2d/absorbing_example/mpm.json Outdated Show resolved Hide resolved
@jgiven100
Copy link
Contributor

Just pushed updates with 3d model & matched the existing naming convention for the 2d model. Both 2D and 3D benchmarks are the 1D column

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants