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
  • #2

Closed
Open
Created May 15, 2018 by Martin Bauer@bauerReporter1 of 3 tasks completed1/3 tasks

Fluctuating (Randomized, Thermalized) LBM

  • get random number from external field, add kernel to test suite @winterhalter
  • physical test case to check random number correlation (auto correlation function?) @kuron
  • final version should compute random numbers in the kernel itself. 'mulhi' / 'mullo' functions are required - philox RNG - write a pystencils function similar to bitoperations for these operations - on x86 there are intrinsics for mulhi/mullo, alternatively one could also use AES instead of philox since there is also a intrinsic for that - on GPU there should also be an intrinsic - C fallback as one-liner - two versions required for drawing float & double random numbers - fast versions produce 2 or more RN per step, how to handle this?

Fixes walberla/walberla#80 (closed)

Edited Aug 02, 2019 by Martin Bauer
Assignee
Assign to
Time tracking