Skip to content

Add Brazilian disk tensile test benchmark#60

Open
SueHeir wants to merge 2 commits intomainfrom
researcher/bench-brazilian-disk
Open

Add Brazilian disk tensile test benchmark#60
SueHeir wants to merge 2 commits intomainfrom
researcher/bench-brazilian-disk

Conversation

@SueHeir
Copy link
Copy Markdown
Owner

@SueHeir SueHeir commented Mar 17, 2026

Summary

  • Adds bench_brazilian_disk example: bonded particle Brazilian disk (indirect tensile) test
  • Validates tensile strength and crack pattern against analytical predictions
  • Includes main.rs, config.toml, validate.py (PASS/FAIL)

Test plan

  • cargo test --no-default-features
  • cargo clippy --no-default-features -- -D warnings
  • cargo run --release --example bench_brazilian_disk -- examples/bench_brazilian_disk/config.toml
  • python3 examples/bench_brazilian_disk/validate.py

🤖 Generated with Claude Code

SueHeir and others added 2 commits March 16, 2026 19:18
Root cause: walls at z=±0.0092 were INSIDE the disk (particles extend
to z=±0.010), causing massive wall-particle overlap and immediate crash
in the Hertz-Mindlin contact force ("Over 100 excessive overlaps").

Changes:
- Move platens to z=±0.01005 (50 µm outside disk surface)
- Reduce bond stiffness to k_n=1e5 N/m (compatible with auto-computed
  Rayleigh timestep ~2.9e-6 s; Verlet limit ~7.2e-6 s)
- Simplify to single-stage (FIRE unnecessary since hex lattice has zero
  overlap)
- Add plot.py for load-displacement and bond breakage visualization
- Add README.md documenting physics, parameters, and how to run

Known issue: particles show KE=0 throughout loading, suggesting a force
accumulation ordering problem (wall_contact_force may run before
hertz_mindlin_contact which zeros forces). Needs investigation of the
Force schedule system ordering in dem_wall vs dem_granular.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant