Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
ALF
ALF
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ALF
  • ALFALF
  • Issues
  • #170

Closed
Open
Opened Nov 09, 2020 by Jefferson Stafusa E. Portela@stafusaOwner

Joining all possible global updates options

Langevin and HMC are now options of Global_update_scheme - what about integrating into this variable also the custom/user-defined global update option (Global_moves, ? Global_tau_moves ?), to avoid having conceptually similar options scattered into different parameters.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
Nov 30, 2020
Due date
Nov 30, 2020
Reference: ALF/ALF#170