Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • alchemiscale.org user group

    • user questions / issues / feature requests

    • compute resources status

    • current stack versions:

      • alchemiscale: 0.2.1

      • gufe: 0.9.4

      • openfe: 0.13.0

      • perses: protocol-neqcyc

      • openmmforcefields: 0.12.0

  • JW : alchemiscale working group governance

  • IP : Protein-ligand benchmarks working group update

  • IP : feflow development:

    Github link macro
    linkhttps://github.com/choderalab/feflow

  • alchemiscale development : current sprint spans 10/25 - 11/6

Discussion topics

Notes

  • alchemiscale.org user group

    • user questions / issues / feature requests

    • compute resources status

    • current stack versions:

      • alchemiscale: 0.2.1

      • gufe: 0.9.4

      • openfe: 0.13.0

      • perses: protocol-neqcyc

      • openmmforcefields: 0.12.0

  • JW : alchemiscale working group governance

    • Goal of existing governance structure was to have major stakeholders able to propose/approve/block scope changes and vote on clarifications to Dotson’s work on Alchemiscale.

    • We’ve largely completed the mutually agreed-upon goals laid out on that page.

    • Do we want to plan for additional goals or phases beyond incremental reliability/UX improvements? If so, who would be interested in that, and should the list of stakeholders be changed?

    • This meeting has been a useful touchpoint to sync up between users and developers, though it’s also been a source of confusion when messaging gets jumbled with different channels.

  • Should we:

    • Keep stakeholders/governance structure?

    • Keep this meeting as a user group and informal developer sync up?

    • Define new goals?


  • IP : Protein-ligand benchmarks working group update

  • IP : feflow development:

    Github link macro
    linkhttps://github.com/choderalab/feflow

Action items

  •  

Decisions