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

Version 1 Next »

Participants

Goals

  • Updates from MolSSI

    • duplicate tasks deleted?

  • User questions/issues, new submissions

  • Science support needs

  • Infrastructure needs / advances

Discussion topics

Item

Presenter

Notes

Updates from MolSSI

Ben

  • Fixed issues with inconsistent state

    • 10s of thousands of jobs in task queue associated with complete records

    • if you resubmit a record that already exists, even if COMPLETE, a task will get created

      • know where this hole is; can fix and produce new release, deploy to public QCArchive

  • BP: removed all duplicate tasks

    • DD: will turn managers back on to compute industry datasets, put them on their own compute tag and observe if backward-forward behavior persists

User issues, new submissions


  • PB: #220 - need new qcsubmit

    • JH: just have one PR on qcsubmit blocking release; working on this

    • PB: have one compute spec on this submission DF-CCSD(T)/CBS that will take up to 150 GiB of memory for 16 heavy atoms

    • PB: typically also use 48 cores

  • JH: working on #223, blocked by validation issues as well

    • going to add some ANI specs, will need some ANI workers

      • will still use ANI2x we had issues with, but relaxing convergence criteria

      • DD: until we have a release from Adrian, unfortunately can’t use the latest fixes to this in prod

  • JH: ML stuff, adding HDF5 support for QCSubmit

    • instead of a ton of SDFs, can use one file

    • JW: what are the contents

    • JH: conformers and mapped SMILES

    • JW: is this file going to contain the same content as the other files, or is there something fundamentally different here?

      • one thing that makes SDF safer is that readers and writers are not something we’re defining

      • JH: there’s a lot of repeated info in the SDF

        • also want to pave the way for multimolecule support, dimers, etc.

      • JW: good point

      • JH: understand concerns on future variability; would like to get a spec down as much as possible

    • JH: any feedback anyone has on this issue ( ) appreciated

  • DD: concerned about collection size; will run into same issue as before

    • SB+JH: not clear if it’s a single collection with a million conformers, or spread across several collections, or multiple million conformer collections

    • BP: the metadata object for a collection gets very big as more and more objects are involved (molecules, specs), so this becomes an issue in the way collections are currently implemented

      • is getting fixed in the next branch

    • SB: can see this taking another month for John and Peter to resolve; what is the timeline for next branch deployment?

      • BP: end of the year earliest? Can’t make a guarantee there, though

    • JW:

Action items

  •  

Decisions

  • No labels