Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • elsi-interface elsi-interface
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • elsi-devel
  • elsi-interfaceelsi-interface
  • Issues
  • #22

Closed
Open
Created Jul 13, 2017 by William Huhn@huhnMaintainer

Use Homegrown Dictionary Data Structure to Change ELSI Variables?

(Suggested by Alberto Garcia)

Store changes to ELSI state in a dictionary data structure, so that we can add and remove parameters from ELSI and solvers without changing the interface

Assignee
Assign to
Time tracking