2020-03-26 Software Scientist Onboarding notes (Thompson version)

Open Force Field onboarding day 3

Wagner
Dotson

Health of the infrastructure

  • QCSubmit

    • Doesn't exist yet, being built by Horton, who is very careful

  • QCPortal

    • Best corner of the infra, beautifully built by Smith @ MolSSI

  • QCFractal

    • In decent shape

    • Many issues with file systems

  • Property Estimator

  • ForceBalance

    • Frequent pain point

    • Many heterogenous interfaces, file I/O, etc.

    • Fundamental issue of representing molecules: can't have all 3

      • QM - nuclei, charges, not really much else

      • cheminformatics - "graph"-like object, atoms, elements, bonds,
        sterochemistry, aromaticity (everything needed to type using SMIRKS)

      • MM - parametrized system (i.e. including force field)

  • CMILES

Lots of scattered glue for various conversion, some value in unifying at least conversions? I.e. any QM->MM representation is done in the same way across people, projects, labs, etc.

Dotson raised an issue on the QM->MM conversion weeks ago in which Wagner detailed the problem, had a hard time finding it

Build process

  • gh/omnia-md/omnia-recipes

  • Many deprecated recipes, not really a problem since most things don't depend on each other

  • Goal is to migrate everything to conda-forge, no small feat but Jaime is making great progress

  • Major pain point is OpenMM, legacy reasons based around OpenMM's build system conflicting with conda-forge's preference

  • Once OpenMM can migrate, the levee breaks and the rest of the stack can migrate (hopefully!)

  • openforcefield #286: Wagner wrote thorough docs on the standard release process

  • Another time: we will work on improving developer docs (perhaps on another wiki)