Driver | Approver | Contributors | Stakeholder |
---|---|---|---|
Objective | We aim to automate the filtering and submission of molecules to public and local qcarchive instances. |
Due date |
|
Key outcomes | Automate the preparation of optimisation and torsiondrive datasets from input lists of molecules. |
Status |
QCSubmit
Currently submitting molecules to the public QCArchive has involved the use of scripts hosted at this github repo . While this method seems to be stable we aim to expand its capabilities while automating the procedure, this will be particularly helpful in the case of the bespoke workflow, but will also impact on the generation of datasets for general force field fitting.
Must have:
A workflow, the process to filter and prepare the molecules should be easy to configure and control given a large number of settings available. This should be controllable through the API, settings files and a CLI. Spec for how we imagine this to look can be found here .
state enumeration stereoisomers/tautomers
fragmentation
cmiles identifiers on all submissions
WBO on all submissions
filtering based on simple molecule properties (element type size/weight)
Be easy to serialise to file
A convenient way to collect the results as well
Nice to have:
Ability to ensure that calculations can be reused where possible
Not in scope:
Add anything you don't want to include
Use the roadmap planner (/roadmap) to help your team stay on track. To edit workstreams or dates, select the placeholder below and tap the pencil icon.
Type /trello to add a card or board to this page or /jira to include a Jira issue, chart, or project.
Plot out milestones and deadlines using the table below. Put each milestone on its own row, @mention milestone owners, and type /date to quickly add deadlines.
Milestone | Owner | Deadline | Status |
---|---|---|---|
Draft 1 of QCSubmit | |||
Add links to relevant research and any other key documents
Description | Github link | Status | Blocking | |
---|---|---|---|---|
1 | Draft 1 spec for the python API |
|
| |
2 | Report which toolkit was used. |
|
|