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 3
Next »
Participants
Goals
alchemiscale.org
DD : new proposed stack versions for alchemiscale.org
; awaiting results of QA tests on gufe + openfe 1.0rc1
DD : proposal since still waiting on openfe + gufe QA:
DD : production issue: exhausting neo4j threadpool on alchemiscale.org
due to large AlchemicalNetwork
on asap-public-*
; need to release and deploy alchemiscale
0.4.0 ASAP
Discussion topics
Notes |
---|
alchemiscale.org
DD : proposal since still waiting on openfe + gufe QA: alchemiscale : 0.4.0
neo4j: 5.16 gufe: 0.9.5
openfe: 0.14.0
feflow : main
openmmforcefields : 0.12.0
IA – May need IP to weigh in here. MH – You may need to use a commit of feflow to work with alchemiscale… I changed it in (MH was confused)
DD – We might need to hold off on feflow? Then just roll out alchemiscale 0.4. Then stick with old OpenFE and gufe and drop Perses. Noneqcyc will be in feflow in the future. So there will be a deployment for a little while that can’t do noneq cycling. JS – Will first release with noneqcyc coincide with the first F@H-capable release? DD – Yes. F@H will need to use noneqcyc so that won’t run until feflow is out. DD – Any objections to upgrading alchemiscale to 0.4? JW – MO, are openff-2.2.0 benchmarks complete? JW – DD, would changing alchemsicale version and keeping openfe+gufe versions the same change numerical results?
DD – Ok, I’ll go ahead with this plan JW – Also, happy to turn any extra NRP compute to OpenFE to do their benchmarks
DD : new proposed stack versions for alchemiscale.org ; awaiting results of QA tests on gufe + openfe 1.0rc1 MH – Validation still ongoing. Likely still 1-2 weeks of runtime needed. Realized that I never tried making a PR into ASAP-alchemy repo to see if it’s compatible. I was running on Iris and lost everything once it had tech problems. . alchemiscale : 0.4.0
neo4j: 5.16 gufe : 1.0
openfe : 1.0
feflow : main
openmmforcefields : 0.12.0
DD : production issue: exhausting neo4j threadpool on alchemiscale.org due to large AlchemicalNetwork on asap-public-* ; need to release and deploy alchemiscale 0.4.0 ASAP
|
JS – Looking to run aqueous solvation free energies. Anyone have recommendations for python tools? IA – Chemaxon has a logS tool MT – Check what people used for SAMPL JW – Same as hydration free energy calcs? Perses can do that MH – https://docs.eyesopen.com/toolkits/python/molproptk/molprops.html#logs "Further, it is not suitable for the PK predictions that come late in a project. However, it is useful for eliminating compounds with severe solubility problems early in the virtual-screening process."
JS – DD, could you make a new alchemiscale account for our slackbot?
|
Action items
- David Dotson will investigate slow
set_network_weight
call (due to TaskHub
lock from slow claims from compute services)
Decisions
0 Comments