fix and test gpu packinfo packet size and direction sets. (2eb890ae) · Commits · Frederik Hennig / sfg-walberla · GitLab

Skip to content

GitLab

Explore

Sign in

Primary navigation

Project

S

sfg-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.

Frederik Hennig
sfg-walberla
Commits
2eb890ae

Commit 2eb890ae authored 2 weeks ago by

Frederik Hennig

Downloads
- Patches
- Plain Diff

fix and test gpu packinfo packet size and direction sets.

parent 4800dcb0

Pipeline #77800 failed with stages

in 3 minutes and 56 seconds

Changes 5
Pipelines 1

Hide whitespace changes

Inline Side-by-side

Showing

lib/walberla/experimental/communication/UniformGpuFieldPackInfoBase.hpp 5 additions, 3 deletions

...xperimental/communication/UniformGpuFieldPackInfoBase.hpp
src/walberla/codegen/api.py 5 additions, 0 deletions

src/walberla/codegen/api.py
src/walberla/codegen/communication/pack_infos.py 10 additions, 5 deletions

src/walberla/codegen/communication/pack_infos.py
tests/BasicLbmScenarios/CMakeLists.txt 6 additions, 2 deletions

tests/BasicLbmScenarios/CMakeLists.txt
tests/BasicLbmScenarios/TestBasicLbmScenarios.cpp 15 additions, 6 deletions

tests/BasicLbmScenarios/TestBasicLbmScenarios.cpp

with 41 additions and 16 deletions

Frederik Hennig @da15siwa
mentioned in commit 2aa8cafb
· 2 weeks ago

mentioned in commit 2aa8cafb

mentioned in commit 2aa8cafb19a37f9e8b4b2f7d223eb872969c0042

Toggle commit list

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