2024-09-17 alchemiscale : dev group meeting notes

Participants

  • @Matt Thompson

  • @John Chodera

  • @Iván Pulido

  • @Mike Henry

  • Ian Kenney

  • @Irfan Alibay

 

Meeting recording: https://drive.google.com/file/d/1sHGdgilOBwElA9IDTh15LSfP3YqYmRtt/view?usp=sharing

Goals

  • alchemiscale roadmap 2024

    • Q1 : complete “living networks” performance improvements

    • Q1 : Folding@Home compute services deployed in production

      • finish MVP, with integration test suite by 2024.03 2024.06

      • perform FAH tests with volunteers during 2024.04 2024.06 2024.07 2024.08

        • public work server up by 2024.03.15 2024.06.11 2024.07.19 2024.07.31 2024.09.15 2024.10.01

        • confidential work server up by 2024.04.01 2024.07.01 2024.07.31 2024.09.30 2024.11.01

    • Q2 Q3 : develop Strategy structure, initial implementations

    • Q3 : enable automated Strategy execution by end of Q3, 2024 (2024.10.01) mid Q4, 2024 (2024.11.15)

      • performing design in parallel with Strategy structure above

  • DD : alchemiscale advancement opportunities in 2025

  • IK : Strategys design proposal

  • DD : alchemiscale-fah 0.1.0 release imminent

    • was blocked by openmm-core deployment issues with OpenCL; new openmm-core deployed last week

    • finishing out remaining changes noted from live test here:

  • DD : reorganized alchemiscale project coordination

    • alchemiscale and alchemiscale-fah now under OpenFreeEnergy Github org

    • created new alchemiscale.org-deployment repo:

      • will host deployment environments, Docker build automation for alchemiscale.org

    • created new alchemiscale.org-site repo:

      • will host the alchemiscale.org static site, using Hugo

    • will use Github Discussions as a hub for user questions that fall outside of issues, are more to do with usage questions

    • OpenFE : meeting notes platform in place?

  • DD : large ProtocolDAGResults produced by RelativeHybridTopologyProtocol

  • alchemiscale development : new sprint spanning 9/18 - 9/30

    • now focusing effort on milestones for alchemiscale v0.5.1 and v0.6.0 releases

    • aim is to complete 0.5.1 fairly quickly, and produce a 0.6.0 release with major new features by the end of the month

    • coordination board : alchemiscale : advancement sprints

Discussion topics

Notes

Notes

  • DD : alchemiscale advancement opportunities in 2025 - Mind Map

    • IA: Could units in a DAG that spawn from a single protocol be parallelized in different compute resources?

    • DD: There’s no global state knowledge on alchemiscale that could easily check what resources are available.

    • DD: DOes it make sense to take the mindmap pieces and put them in the OpenFE roadmap?

      • IA: I have to think about it.

  • IK: Strategies discussion

    • Looking for feedback on https://github.com/OpenFreeEnergy/alchemiscale/discussions/303

    • JC: Does the strategy object have information on how many work units or similar data?

      • IK: We are still working on what should be there.

      • JC: We want to standardize a minimal amount of information that gets there.

    • We want to implement initially the NetBFE approach

    • JC: How periodically will the “strategizer” be called? Is that something that could be user configurable?

      • DD: there will be a maximum frequency imposed server-side. Users would be able to use a smaller frequency.



Action items

Decisions