using the command \input{|"path-to-script.py"} . I think you'd better to put all the parameters in a single python (or whatever language is your favorite) file and use command line parameter to access it like \input{|"path-to-script.py param-name"} . In this case you can include the param file into other scripts to run the simulations. However, it makes the compilation slower and has some other negative points. -- Mohsen Aug 2 at 9:28 Even more important, in my opinion, is making sure that you can figure out how to re-generate all your results from scratch in a month or a year (for instance, when referees ask you to add or modify something). For that purpose, what I do is include a text file with very detailed directions on how to reproduce all results. It's best if you test these out by having someone else (like a co-author) try them. I recommend that you also provide these instructions (and all your code) to referees and readers. I've done that before (for my own sanity), and thankfully, it paid off when my adviser asked me to re-generate and re-check results. I've since switched to just dumping the source code of a script that runs everything into an appendix of my drafts so it's there, I know what I did, and I can click one button to get all of the numbers and figures. -- Geoff Oxberry ? Jun 18 at 13:10 The script doesn't do any installation right now, because it's just a MATLAB