Python in Academia by Marco Bardoscia

  • 139 views
Uploaded on

Python in Academia by Marco Bardoscia

Python in Academia by Marco Bardoscia

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
139
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Python in Academia Marco Bardoscia International Centre forTheoretical Physics
  • 2. Background > Theoretical (statistical) physicist > Economic systems (financial markets, economies) > Social systems (social networks) > Computational problems (SAT extensions) > Biological systems (metabolic networks)
  • 3. Tools in Science “Using regular adhesive tape they managed to obtain a flake of carbon with a thickness of just one atom.” nobelprize.org
  • 4. ComputationalTools > MATLAB > A single FORTRAN file (5000 lines of code) > C++ for data analysis > R
  • 5. ComputationalTools > MATLAB > A single FORTRAN file (5000 lines of code) > C++ for data analysis > R … mostly true for small groups.
  • 6. > General-purpose > Plenty of packages > Nicely extendable > Interactive But Python is:
  • 7. > General-purpose > Plenty of packages > Nicely extendable > Interactive But Python is: … but many people in academia care about different things!
  • 8. What people care about: > Is it fast (enough)? > Is it at least always faster than MATLAB? > What about my legacy code? (wrapping in Cython is hardly a choice) > Can I get nice publication-ready plots? (using defaults?)
  • 9. What about reproducibility? If what I have done is interesting, someone else will do it from scratch. If they find the same results (modulo some tiny details) using an entirely different code, then we didn’t do anything terribly wrong…
  • 10. > Up-to-date comparison with Matlab for the most relevant functions > Nice(r) defaults for Matplotlib plots > Simpler integration with compiled code What can be done?