JW – Very cool. I did the Stanford ML course with Andrew Ng and really liked it - was very hands-on and I feel I got a good working understanding.
MT – I’d heard that one is good but somewhat outdated (eg doesn’t use pytorch)
Cancel OpenMM meeting Friday?
JW – Worth mentioning OpenMM 8.2 noises from interchange regression tests and OpenFE?
MT – Was unable to isolate our regression test failures to OpenMM. Unfamiliar with OpenFE issues. Should I follow up?
JW – I think OpenFE may be avoiding it due to an abundance of caution until it’s validated. Not worth following up. I fixed some numerical errors recently where ARM mac CI was failing by forcing use of Reference platform in OpenMM. Possibly something up with OS GPU presentation/OpenMM platform seleciton logic.
MT – Good to know.
Aiming to work Mon & Tues of next week, but unstructured (i.e. no agile)
Any odds and ends you want me to look at?
JW – Seeing if OpenFF-units + typing + new pint is happy would be handy. But don’t haver to commit to fixing it if it turns out to still be a hairball.
Triage/support, chipping away at little bits of debt, or whatever catches my attention
Rough pass of all tutorials done, a little confused and pessimistic about the direction of the project
MT – Basically all gromacs stuff fails since we can’t read/write itp files.
JW – Writing itps wouldn’t be a requirement - if we can write a top that gets the same energy then that’s a win.
MT – I estimate that reading itps will be a large amount of work. Can’t recall if we can read tops.
JW – Added to task tracker
JW – I wonder how many of these tutorials we could roundtrip using OpenMM’s parser.
MT – That’s possible, could be worth testing. Kinda kicks the can down the road for a “good” solution and would require OpenMM as major dep. Also adds complexity/information loss by going through different steps+tools.
JW – Added to task tracker
Added new section about next steps to bottom of agenda
Working with Brent on getting torsions running on YDS - Currently torsiondrives are at MVP stage - Can regenerate results and do other handy tasks easily. So I’m working with BW on getting this running. ETA to getting torsions running on YDS is pretty soon (days).
JW – Cool. Thanks for reaching out to work with BW. I think it’s good that the torsiondrive data structure is pretty analysis-agnostic, since the science team is just starting to figure out what kinds of analysis they’ll want to do, and this will offer tehm lots of flexibility.
Re: AmberTools issues, a little frustrating to
document issues, ruffle a lot of feathers about it, and then get feedback about how people were not sufficiently informed about it
JW – I don’t think we should spend significant energy supporting AmberTools. We can spend an hour helping MH or something as part of our “neighborly OMSF” duties.
MT – I’m frustrated that people are asking for summary of current status and I’d made that available before. Unclear that Amber devs are making progress on this. I do have ideas for what to try but if I’m the last one to have opened a PR then I’ll be seen as the responsible party. Ideally MH would take the lead on this and I could probably provide valuable support.
JW
Did I get monthly goals right for ad board? I was preparing after hours and didn’t want to bother you but realized that I’m less aware of what you’re working on with agile/big picture style planning is less evident (but perhaps less necessary). I think solution is for me to start joining planning meetings.
MT – Yes, please join sprint planning. Next one will be Dec 2
JW – Good, I’ll join that.
MT – You kinda got monthly goals right. There’s kinda a vacuum of establishing larger goals. I would need more guidance from org level about big objectives to plan my monthly objectives. So I think this is where JW and JE should come in.
JW – Great, that’s along the lines of what I’m hoping for as well.
MT – Would love for there to be suggestions prepared for sprint planning so it’s not just status quo (me thinking of what I should do)
MT – If CHARMM-GUI’s system prep infrastructure is a 10, I suspect WZW’s is a 2 (where 0 is good). I suspect WZW is still doing a bit of sketchy unvalidated parmed stuff but less than charmm-gui. So I’d take their use cases with a grain of salt, and not rush to thinking that these pathways are production-ready and ready for us to make into a product.
MT – Can we drop testing of intel macs?
JW – Yes. I’ll think about how to announce this but we can discontinue testing now.
Might be an easy win to show that some conversions are possible.
We’d need to think a lot about how we endorse these results if positive - Workflows that go through so multiple tools may have edge cases/bugs that we can’t foresee, warn about, or fix.
This could let us enable users to do things we don’t explicitly validate, eg fancy AMBER glycoproteins or some other niche FFs that are only possible in other ecosystems. Downside is that it’s unvalidated and has huge surface area (eg glycam has custom 1-4s)
Target specific use cases (eg AMBER glycoproteins above)
Much better scoped, somewhat easier to validate.
Limited in applicability but we can enumerate the major use cases without needing to eat the world.
Commit to making GROMACS itp reader (but not necessarily write)
Est a large amount of work (> 1 week)
Commit to supporting OpenMM vsite imports
Lots of types/cases (implementing for just TIP4P is different than generally that type of vsite) - Est 1-2 weeks, mostly tests, will require addl specification of use cases.
Commit to supporting OpenMM metal imports
Neither of us have a good enough understanding of metal handling to know how to define correct here. Questions about topological representation, functional forms. If it’s all straightforward (harmonic bonds + coulomb + LJ) it could be easy.
We’ll need someone with biopolymer-metal simulation experience to help us understand domain.
Some edges here - Not straightforward to say “you can roundtrip metalloproteins to/from OpenMM, but can’t go to GROMACS” - There’s not a record of where the component came from and trying to police this will add a ton of complexity.
JW will raise this to JE’s attention and bring up for discussion.