Add geom argument to ESMF_FieldBundleGet()

[tclune]

In MAPL it would be preferable to directly get the GEOM rather than (1) using a set of conditionals on the geomtype, (2) extracting the underlying grid, locstream, etc, and (3) creating a new geom.

At the very least this results in a small memory leak as it is hard to know which geom objects MAPL should destroy.

My team should be able to implement this, but want a thumbs up from ESMF team before we proceed.

[oehmke]

I think that it makes sense to add Geom to ESMF_FieldBundleGet(). If your team is willing to do that, that would be great. The one thing to be aware of is that all the Fields in the FieldBundle are not necessarily on the same Geom. However, there should be logic that handles that for the Grid, etc, so they can use that as a guide for how to deal with that. Let me know if there are any questions. Thanks for offering to put that in!

…

On Oct 17, 2024, at 10:29 AM, Tom Clune ***@***.***> wrote: In MAPL it would be preferable to directly get the GEOM rather than (1) using a set of conditionals on the geomtype, (2) extracting the underlying grid, locstream, etc, and (3) creating a new geom. At the very least this results in a small memory leak as it is hard to know which geom objects MAPL should destroy. My team should be able to implement this, but want a thumbs up from ESMF team before we proceed. — Reply to this email directly, view it on GitHub <#310>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE6A7U24VRKTYTEDR65CMHDZ37QVBAVCNFSM6AAAAABQEELJ4WVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU4TKMRRGIYTQMA>. You are receiving this because you are subscribed to this thread.

[anntsay]

Action: Bob to follow up with Tom's team to see if they are willing to do this and whether they can make dec 6th code freeze for release 8.8.0