3 ms·
> the code in Matlab seems like a disaster as far as ever > making this or similar approaches modular and so usable- > by-others goes. As always, it depend
by apl 14y ago
> the code in Matlab seems like a disaster as far as ever
> making this or similar approaches modular and so usable-
> by-others goes.
As always, it depends. I've seen very well maintained MATLAB code bases, and I've seen the opposite (with the latter greatly outweighing the former). We should give these guys the benefit of the doubt. Somewhere Karr mentions Hudson CI, so they don't seem fully removed from good practices. Interfacing with MATLAB from C is reasonable.
In an ideal world, this would be a NumPy/SciPy prestige project, but neither the community nor Python for that matter are quite there yet.
- joe_the_user 14y agoThe thing is that Matlab is problematic for further extension even if the basic code is well done simply because of Matlab's weird function composition architecture and other weirdnesses. Consider that if biological simulations are going to go to a larger scale, you won't want to simply call a bunch of Matlab simulations from a single C program but rather have a bunch of distinct programs that would be modified to call each other (with each of these programs running as they do now in their Matlab instance).
- nagrom 14y agoI'm confused. In what way is Python not there? If one specifies, e.g. Python 2.7, what do you consider to be the short-comings? I'd also like to know how you think numpy/scipy are short compared to Matlab. I've not run into their limitations yet.
- lazyjeff 14y agoI think the main thing is libraries. I was looking for graphical model software that supported DBNs once, and could only find Matlab ones. There was a python wrapper for one of the Matlab libraries but was not widely supported.