Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • lbmpy lbmpy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • pycodegen
  • lbmpylbmpy
  • Issues
  • #29

Closed
Open
Created Feb 09, 2022 by Markus Holzer@holzerOwner

Relaxation Rate Grouping

As shown in the literature it is not a particularly good idea to define the relaxation rate of the moments by the ordering. In fact, there are different things that need to be considered. The most prominent one is the isotropy condition. This means that moments that are rotated forms of others should be relaxed with the same relaxation rate. The idea is defined here.

Furthermore, the big problem with MRT-like methods is that moments are not statistically independent. Thus moments sharing information with each other should not be relaxed with different relaxation rates. This could lead to another approach when thinking about the grouping of the relaxation rates.

Assignee
Assign to
Time tracking