Personal Website.

Posts tagged ‘dtc’

Research Update

My Research page still claimed that I am quite indecisive for what I want to do with that PhD position of mine. That has actually been untrue since January, because then I had finally decided that I will leave bioinformatics behind me and engage in more physical fluid dynamics simulations for medical research and Alzheimer’s Disease (AD) in particular. I am still quite unsure of what “field” that now leaves me with. Medical physics Simulation? With a big question mark attached to this I think I can deservedly claim to be in complex systems simulation.

Because I have trouble naming my research in less than 10 words I have finally got round to updating my research page. That also means that it is getting serious now. Soon I will have finished the first taught year in the DTC and in the remaining three years after that I will hopefully manage to answer at least a few of the many unresolved questions surrounding AD resulting in a doctorate degree.


Software Carpentry

I really enjoy the environment of the DTC. We have recently started a weekly event called “Coffee, Cake and Science Talk”. Its main purpose is to get DTC students together and have a chat about their work (or unrelated things…) while enjoying some nice cake.

Last time we entered a really fruitful and encouraging discussion about making you research truly reproducible and coding practices. One website that got mentioned is Software Carpentry, which is exactly about writing code to make your research reproducible. I found this website particularly useful, since recently I had to go on a parameter goose chase for a model that I needed to reimplement.

The website mostly talks about things that actually are (or should be) common sense, but setting up repositories for your code or keeping exact track of software versions you use is a bit annoying. So at least I find it quite useful to be reminded of all these things. After looking at the website I set up a Git repository on Bitbucket, which gives you unlimited private repositories. Normally I would always be on the open source side, but if you’re working on a project that involves unpublished stuff, you might rather choose to not entirely open it to the public straight away.