Best practice for working between Matlab python

adamjhepburn

Hi,

I am trying to work between Matlab and python in order to effectively work with some collaborators with no Matlab access.

Is there best practice for exporting models between the two?

I am trying to export pre-solve versions of my model using write_netCDF (the src/m/netcdf/ version) and get these into python 3.12.

My input model from matlab has Schoof friction, glads hydrology, and uses smb components, but when I export the netcdf file and import it in python my md reverts to the default (e.g., empty Budd, shreve, and the default SMB) except for md.mesh, which matches the matlab version.

My .py file includes the line: from read_netCDF import read_netCDF

Thanks!
Adam

mathieumorlighem

Hello @adamjhepburn

these functions "sort of" work, but have not been tested thoroughly, so I think we are going to need your help to make them work. One student worked on it about a year ago and has alternative functions in src/m/contrib/musselman. Can you take a look and see what you think, feel free to make changes as you see fit (e.g., it looks like the inversion class is properly handled, we should do the same for all fields... probably automatically)
Mathieu

adamjhepburn

Hi @mathieumorlighem

Ah okay, yeah the inversion field works fine so I'll follow that structure and try to get hydrology, friction, and SMB to work that way and let you know!

Adam

justinquinn

adamjhepburn
Hi Adam,
Thanks for poking around at this. As Mathieu said, we can't verify that it works and a few people have taken a crack at it over the years. One big gotcha is subproperties of the results field if you get as far as wanting to pass already computed results around. Let us know if you hit any snags.