http://www.nitrc.org/forum/forum.php?forum_id=101 General Discussion en-us Copyright 2000-2026 NITRC OSI Fri, 03 Jul 2026 23:43:35 GMT http://blogs.law.harvard.edu/tech/rss NITRC RSS generator http://www.nitrc.org/forum/forum.php?thread_id=110&forum_id=101 I am in the process of registering Mindboggle (http://www.binarybottle.com/mindboggle.html) with NITRC, and am about to completely rewrite Mindboggle to have a more efficient, flexible and modular processing pipeline. I am strongly considering porting the codebase over to Python for the following reasons:<br /> <br /> 1. free, open source (unlike Matlab)<br /> 2. easy to program, understand, and maintain<br /> 3. easy for Matlabbers (e.g., python's Matplotlib)<br /> 4. recent development of numpy (scipy.org)<br /> 5. widely used<br /> <br /> As evidence of #5, beyond the recent effort of NiPy (http://neuroimaging.scipy.org/) to create a &quot;full-featured python program and development environment for analyzing functional imaging data,&quot; and the extensive list of scientific programs on scipy.org's website, I'm finding that many software suites are now using Python as the scripting language that &quot;glues&quot; pieces of code together (e.g., ESRI's GIS software).<br /> <br /> I would be very interested to hear what people have to say about porting code over from Matlab to Python for use by the neuroimaging community.<br /> <br /> Thank you!<br /> <br /> Cheers,<br /> @rno Arno Klein Mon, 25 Jun 2007 20:00:40 GMT http://www.nitrc.org/forum/forum.php?thread_id=110&forum_id=101 http://www.nitrc.org/forum/forum.php?thread_id=105&forum_id=101 Welcome to Open-Discussion Christian Haselgrove Mon, 25 Jun 2007 19:24:18 GMT http://www.nitrc.org/forum/forum.php?thread_id=105&forum_id=101