Not Invented Here: Porting Scientific Software to Python
summary
Porting Matlab conformal‑mapping code to Python proves much harder than the topic alone suggests: an initial week yields a basic object model, a second week only five files, then one painful character fix. Concrete interoperability paths are demonstrated: ctypes for one or two C functions, scipy.weave inline C++ compilation plus siphon/cython and the Jupyter bridge to call Matlab. The notebook approach runs Matlab pieces and returns plots; full ports require deep dives into sparse matrices, complex arithmetic and buildable extension modules.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:10NOT INVENTED HERE PORTING SCIENTIFIC SOFTWARE TO PYTHON
- 0:53WHAT MAKES SCIENTIFIC SOFTWARE DIFFERENT?
- 4:01NOT INVENTED HERE SYNDROME
- 5:18TWO REASONS TO LEARN ABOUT INTEROPERABILITY
- 5:34High Performance Python
- 6:44A WHIRLWIND TOUR OF INTEROPERABILITY TOOLS
related talks
32mNot Invented Here: Porting Scientific Software to Python
27mEngineers to Data-Scientists with Python
32mFrom Fortran to Python: A Conversation Across Generations of Scientific Computing
30mFrom Matlab to Lambda: Transforming Structural Engineering Research Tools
49mPython for High Performance and Scientific Computing
23mPython(x,y): diving into scientific Python
29mC++ ♥ Python: from modules to hybrid applications
30mEmpowered by Python - A success story