Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Change in “metadata” field to “extras”, meeting left this ambiguous as to what is coming.
Projects are almost done.
These don’t directly align with our use of QDS but would allow us to use active learning (discussed in onsite)
New developments:
TM calculations will often use a different basis set for a metal versus the remaining elements. Ben says this is not supported. Luckily Genentech’s favorite model chemistry does not follow this common DFT implementation, but this will limit us in what we we can try / will require more basis functions than if we could have multiple. Psi4 supports, not MolSSI.
Could go into additional_keywords like constraints are.
Chodera tmQM dataset ~675k structures times out before all entries are added.
Ben is making an update to improve the efficiency of the code and add a background_add_entries method to resolve.
Requests:
It sounds like their migration to pydantic 2 is holding up our versioning? Should this be a request?
JAC: Likely a version change this week
JW: We aren’t blocked by QCA using pydantic 2 that I know of, we need to check with Matt.
Update on clean force field releases
Recent QCFractal update should be great. Josh showed me the ropes with docker images.
Should we have a docker in each zenodo repo, or make a docker image instance in zenodo that is referenced and periodically updated.
Depends on size of docker image, if less than 2 GB then include.
Are we holding off on Forcefield archival until metadata to extras change?
Yes
JW: We would strongly like for the docker to be included
Basically a collaborator was overwhelmed with the number of datasets and their inability to search them easily. The consensus appears to be that adding tags to differentiate OpenFF data from others is the solution. Then left hanging….