Roadmap for pymt?

[aufdenkampe]

@mdpiper & @mcflugen, Our team is beginning to implement BMI coupling among a number of water models for USACE, and we're exploring various approaches for moving forward.

PyMT seems like a great tool, yet I've noticed limited recent development activity in this repo and mention of moving the capabilities of PyMT into Landlab (https://csdms.colorado.edu/csdms_wiki/images/2023_CSDMS_PMESP.pdf).

Does this mean that PyMT will be deprecated?

[gregtucker]

@aufdenkampe good to hear from you! I'll let @mcflugen or @mdpiper respond re PyMT, but the short answer is that the capabilities of PyMT aren't going away; rather, the intent is to combine them with Landlab for a more integrated package.

[aufdenkampe]

@gregtucker, it's good to reconnect with you too. You and your team have done a great job building the LandLab and BMI 2.0 software and user community. It's quite impressive!

That's great to hear that PyMT isn't going away. I'm looking forward to hearing more from @mcflugen or @mdpiper on the roadmap for PyMT, especially what features are staying vs moving to Landlab.

We'll likely eventually want to try coupling our water quality process modules to LandLab, but there are numerous reasons to maintain the codebase separately and rather invoke the much lighter-weight PyMT for the purposes of coupling, grid management, and dealing with units.

[aufdenkampe]

@mcflugen or @mdpiper, to followup on the response from @gregtucker, can you describe whether PyMT will be maintained as a stand-alone package? When I reread the response from @gregtucker, it sounds like once the PyMT capabilities will get rolled into LandLab, then it may get abandoned. Is that right?

[gregtucker]

@aufdenkampe we just talked about this in our team meeting. For sure the PyMT capabilities won't go away. They will continue to be developed and supported. We're still working on the high-level design, partly with the goal of making it easier for people to use PyMT tools/capabilities together with Landlab tools/capabilities - that's what "merge" means for us. But at least for now PyMT remains supported and developed under the package name "pymt", and if in the future there are any changes to its high-level packaging we would help users cross any bridges that need to be crossed - i.e., we have no plans to abandon anything.

Actually we'd be interested to learn more about your use case!