Confessions of a researchaholic

May 18, 2013

Manage research code

Filed under: Real — liyiwei @ 12:55 pm
Tags: ,

Svn is my choice for revision control. I usually use c++ to write the core components, and perl/php/csh scripts to run them. More information can be found under, which contains public domain code of some of my projects.

Those are all relative toy cases.
Real deals can be found in good tech companies.

The best research software practice I have personally experienced is in the NVIDIA GPU architecture group. Strictly speaking, it is development, but there is plenty research involved due to its cutting edge nature. And it worked. Tens or even hundreds of engineers can collaborate on the c-models for multiple versions and generations of GPUs, each with staggering complexity. The products shipped and nobody lost their mind as far as I know.

PS I always believe the tremendous benefits of having at least a few years industry experience before joining the academia.


  1. I prefer git for source control these days, due to the added flexibility it gives you in manipulating branches and so forth. Have you tried it?

    Comment by Christopher Batty — May 19, 2013 @ 7:32 am | Reply

    • Not yet, but hope to try in the future. We used P4 (perforce) in NVIDIA, and one of the main reasons is branch manipulation. I hope I don’t ever have to do branching for a research project. 🙂

      Comment by liyiwei — May 19, 2013 @ 10:59 am | Reply

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.

Theme: Rubric. Get a free blog at