You don’t have to translate/map everything (just use, or read its mapping if you want to map):
You can also just call to (or from) MATLAB:
You CAN also call to Octave, the MATLAB clone language, then you have standard functions, lose out on toolboxes. But I couldn’t use the library for that at the time, and it’s still unchanged for 4 years now.
But I could call Python (then with PyCall, now would use PythonCall), and to Octave from it… Calliing Python in-process, not to Octave from it, it still works. And I had to disable OpenBLAS threading with an env var, do get around a bug.
This might help you migrate (I did in stages), or actually not migrate, just use MATLAB code.
There IS a MATLAB code translator available online, but it doesn’t handle all syntax, nor semantic differences: