Skip to content

GitLab

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

Closed
Open
Created Mar 01, 2021 by Fakher F. Assaad@fassaadOwner

Flavor_symmetries

How should we at best implement flavor symmetry in the code?

Question: Concerning OP_T and OP_V

  1. should we provide just minimal changes to programs that are blind to flavor symmetry?
    Upshot: offers more possibilities for debugging.
  2. should we design the program with flavor symmetry in mind? Upshot: has no redundancies.
  3. General structure --> will follow from 1) and 2).

Please all think about that.

Assignee
Assign to
Time tracking