Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • lbmpy lbmpy
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • 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
  • #1

Closed
Open
Created Nov 08, 2018 by Stephan Seitz@seitzMaintainer

Relace `update_with_default_parameters`

LBM methods and kernels can be constructed in a fabricator pattern with a lot of magic parameters bundled as dict. Users need to read the documentation or the source code to know about all the option. Some lazy users are to lazy to read.

Wouldn't it be better to provide a dict-like type for that with a __init__ that replaces update_with_default_parameters to provide the user with autocomplete and documentation (member-wise) about which fixed members this dict has? The type could still duck type or subclass a dict and would be explicitly convertible via dict(vars(type))

Assignee
Assign to
Time tracking