Discover and read the best of Twitter Threads about #OHBMx
Most recents (2)
Brain folds develop together with cytoarchitectonic regions and corticocortical connections. That folding results from a mechanical instability is now relatively well accepted. However, the pattern of these folds is still thought to reflect patterned gene expression #ohbmx 
2
Indeed, a genetic program could encode regionalisation, connectivity and folding patterns. But what if folding *patterns* were of mechanical origin too? That would mean that mechanics have a causal role in the development and evolution of brain organisation! #ohbmx
Indeed, a genetic program could encode regionalisation, connectivity and folding patterns. But what if folding *patterns* were of mechanical origin too? That would mean that mechanics have a causal role in the development and evolution of brain organisation! #ohbmx
3
One hint at the mechanical origin of folding patterns comes from observations made across primate species. Brains of phylogenetically distant species but with similar volume tend to have similar folding patterns despite their common ancestor being likely lissencephalic #ohbmx
One hint at the mechanical origin of folding patterns comes from observations made across primate species. Brains of phylogenetically distant species but with similar volume tend to have similar folding patterns despite their common ancestor being likely lissencephalic #ohbmx
@OHBMequinoX 1. We joke about how terrible academic code often is. But as science becomes more dependant on code, it starts to scare me. Here are 7 tips for reducing the chances of having to retract your paper due to bugs in your analysis scripts. #OHBMx
@OHBMequinoX 2. Divide and conquer to reduce complexity. Tip 1: cut up that 1000+ lines monstrosity of a script. Tip 2: have a strict division of responsibility between individual steps of your pipeline. Tip 3: make it easy to run a single step on a single subject, as well as run all. #OHBMx
@OHBMequinoX 3. Never trust someone else's code. Never *ever* trust your own code. Tip 4: Save the intermediate result of each script. Tip 5: Plot everything! Just because the end result looks reasonable does not mean you didn't screw up somewhere in the middle. users.aalto.fi/~vanvlm1/conpy… #OHBMx
