Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Date

Participants

Goals

  • QCSubmit for ANI2x calculations

Discussion topics

Item

Presenter

Notes

Permanent database or ephemeral?

Josh

  • XL: Thinking more about the just getting ANI results for single molecules.

    • JH: Recommend using the Snowflake instance for getting calculations back in a way that’s more like a script.

  • Want to be able to have a single callable for torsiondrive evaluation.

    • A single torsion

Demonstration of QCSubmit for ANI2x calculations

Josh

  • JH: Use QCSubmit factories to generate Dataset objects with reasonable parameters populated. Validation proceeds on generated datasets before submission to the target QCArchive instance

  • Can add molecules to the dataset via molecule objects, .smi files, etc.

  • XL: Looks straightforward to run, but what do the dependencies look like?

Aims in industry

Gary

  • GT : want to do evaluation of the forcefield on internal molecules

    • can’t have OEToolkit expenses

    • want to be able to rerun scripts for coverage

    • interested in permanent instance for large molecule sweeps

    • take 500 molecules and repeat the analysis done before

    • We want a workflow to set up the archive sub in our molecules and run the analysis and then combine results at the end.

    • also need torsion analysis

  • Don’t want to get into a situation of having to install everything at every pharma partner (Janssen’s?)

  • DD we are working on the benchmark dash as well which should cover this kind of workflow and add the functions.

  • DH : at the moment we only want optimizations torsiondrives will be useful later.

  • DD: installing is an issue and so far with workers we have used docker images to help get workers up faster this could also work in this case if the full environment was in docker with an entry point that we can insert the molecues into.

  • DH: we are working on a more deployable workflow which I am testing, I have been running torsiondrives locally and that works with the old scripts from Lim.

  • DD: lets set up a regular meeting for this time so we can keep a tight feedback loop.

  • GT: We want to work out exactly what we want but probably set up the archive and all dependencies then run optimizations would be a great start.

Action items

  • Joshua Horton will remove the Fragmenter hard dependency; tuck imports into places where it is absolutely needed with exceptions indicating install requirements
  • Joshua Horton prepare two production conda envs targeting the needs laid out by Xavier, Gary respectively
  • Joshua Horton will prototype the functionality for Xavier’s single-callable TorsionDrive request
  • David Dotson set up a recurring meeting with the folks on this call every 3 weeks
  • David Dotson will prioritize Fragmenter refactor (remove hard OpenEye dep by calling toolkit instead).

Decisions

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.