[API] consistent naming of InvInertiaBF in HCSITS (7f7c96ab) · Commits · Markus Holzer / waLBerla · GitLab

Skip to content

GitLab

Explore

Sign in

Primary navigation

Project

W

waLBerla
- Activity
- Members
- Labels
- Issues
  0
- Issue boards
- Milestones
- Wiki
- Releases
- Package Registry
- Environments
- Terraform modules
- Incidents
- Service Desk

Snippets Groups Projects

Admin message

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Markus Holzer
waLBerla
Commits
7f7c96ab

Commit 7f7c96ab authored 4 years ago by

Sebastian Eibl

Downloads
- Patches
- Plain Diff

[API] consistent naming of InvInertiaBF in HCSITS

parent 3a7c3244

Changes 7

Hide whitespace changes

Inline Side-by-side

Showing

python/mesa_pd/templates/kernel/HCSITSRelaxationStep.templ.h 27 additions, 27 deletions

python/mesa_pd/templates/kernel/HCSITSRelaxationStep.templ.h
python/mesa_pd/templates/kernel/InitContactsForHCSITS.templ.h 2 additions, 2 deletions

...on/mesa_pd/templates/kernel/InitContactsForHCSITS.templ.h
python/mesa_pd/templates/kernel/InitParticlesForHCSITS.templ.h 2 additions, 2 deletions

...n/mesa_pd/templates/kernel/InitParticlesForHCSITS.templ.h
src/mesa_pd/kernel/HCSITSRelaxationStep.h 27 additions, 27 deletions

src/mesa_pd/kernel/HCSITSRelaxationStep.h
src/mesa_pd/kernel/InitContactsForHCSITS.h 2 additions, 2 deletions

src/mesa_pd/kernel/InitContactsForHCSITS.h
src/mesa_pd/kernel/InitParticlesForHCSITS.h 2 additions, 2 deletions

src/mesa_pd/kernel/InitParticlesForHCSITS.h
tests/mesa_pd/kernel/HCSITSKernels.cpp 2 additions, 2 deletions

tests/mesa_pd/kernel/HCSITSKernels.cpp

with 64 additions and 64 deletions

0% or .

You are about to add 0 people to the discussion. Proceed with caution.

Finish editing this message first!

Please register or sign in to comment