Hidden Test Set and Testing Server

[rbharath]

One of the biggest limitations of the original MoleculeNet was that there was no hidden test set. This means that many of the papers that have used MoleculeNet datasets test their methods on subset of the datasets and it's very hard to do an apples-to-apples comparisons of different methods. The next generation of MoleculeNet should features a common benchmark challenge with a hidden test set that can be used to evaluate models proposed by different research groups on a fair playing field.

[rbharath]

Forgot to mention, we'll also need a good testing server that groups can submit models to and a leaderboard for new models.

[lilleswing]

This is tricky -- my only ideas would be for only Quantum Mechanics Datasets. We can calculate energies using psi4 at some level of theory for molecules selected from a known library. We then release a training set but hide the test set and heavily limit the time for inference so real DFT cannot be run.

[lilleswing]

Any datasets that require physical experimentation are too expensive and there would be too many arguments about data quality of the Assay.

[rbharath]

Cross referencing this with https://github.com/deepchem/deepchem/issues/1903.

Would setting up a Jenkins build server be a good design for this? An alternative is that we have a manual once-a-month update process. This could perhaps be done automatically with an AWS cron job (https://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduled_tasks.html)