Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W waLBerla
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • waLBerla
  • waLBerla
  • Issues
  • #119
Closed
Open
Issue created Jun 18, 2020 by Christoph Rettinger@rettingerContributor

LBM CodeGen and Field Layouts

The current code generation for LBM (the one that generates a lattice model) hard codedly assumes a field layout of fzyx, which is different from the default for fields in walberla (zyxf). The reason is (partially) that codegen most likely will use vectorization which only makes sense for the fzyx layout. For that reason, the following should be done:

  • let the user specify upon generation of the lattice model which layout should be used
  • assert internally that the zyxf layout is not used in combination with any vectorization since it will break the LBM kernel, leading to completely wrong results
Assignee
Assign to
Time tracking