{"id":3754,"date":"2016-10-11T07:45:53","date_gmt":"2016-10-11T14:45:53","guid":{"rendered":"https:\/\/mozillascience.org\/?p=3754"},"modified":"2016-10-11T07:45:53","modified_gmt":"2016-10-11T14:45:53","slug":"intro-to-bruno","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/foundation-archive\/mozilla-science\/intro-to-bruno\/","title":{"rendered":"Introducing the 2016 Mozilla Science Fellows: Bruno Vieira"},"content":{"rendered":"

Hey everyone, my name is Bruno<\/a>. I’m from Portugal but I’ve lived in Switzerland (Geneva) and I’m currently based in London. I’m finishing a PhD at WurmLab.github.io<\/a> (Queen Mary University of London<\/a>) in Bioinformatics and Population Genomics. Specifically, I’m comparing the genetic diversity of social insect species (like ants and bees) to closely related solitary species. My aim is to test the hypothesis that social insect species have a lower genetic diversity since only a small number of individuals in the colony (e.g., the queen and a single male) are contributing offspring. Among other reasons, this research is relevant to understand evolution, and for conservation efforts.<\/p>\n

\"eusociality-in-insects\"<\/a>

Ants, bees and termites are so called eusocial species, with colonies where usually only the queen and a male reproduces. Cockroaches are solitary species closely related to termites. Photos\u00a0from https:\/\/commons.wikimedia.org\/wiki<\/a> (files WeaverAntDefense.JPG<\/a>, Honeybee_landing_on_milkthistle02.jpg<\/a>, Coptotermes_formosanus_shiraki_USGov_k8204-7.jpg<\/a> and Bush_Cockroach.jpg<\/a>).<\/em><\/p><\/div>\n

I learned Node.js (JavaScript) and became a full stack web developer in 2013, when I was part of the organisation of a big evolution conference, ESEB 2013<\/a>, (1500 participants<\/a>, 400 talks<\/a>, 800 posters<\/a>). I built the website and a platform for managing the conference and since then I realised that Node.js also has many advantages for scientific code.<\/p>\n

\"eseb2013\"<\/a>

A: The whole ESEB 2013 team<\/a>; B: The big auditorium; C: Me and another Bruno keeping the backend up and running during the conference: D: My previous boss and main organiser, Oct\u00e1vio S. Paulo<\/a>; E and F: The 1500 participants<\/a> enjoying Portuguese weather and food; G: My current supervisor, Yannick Wurm<\/a>, giving a talk at ESEB 2013 right before we met for the first time.<\/em><\/p><\/div>\n

For my research, I rely heavily on publicly available data and metadata. Thus I’m very aware of Open Data issues, data discoverability, and metadata quality. I also spend a substantial amount of time reusing and combining Open Source Bioinformatics software into complex data analysis pipelines.<\/p>\n

\"bioinformatics-pipelines3\"<\/a>

Example of how complex bioinformatics pipelines can get with just a few steps and tools.<\/em><\/p><\/div>\n

The general theme I would like to work on during this Mozilla Fellowship is Open Genomics on the Web.<\/strong> Since the advent of high throughput DNA sequencing and the fast technological improvements over the last ten years, the field of Genomics is generating so much data that it’s going to surpass astronomical data or YouTube very soon.<\/p>\n

\"genomical-data\"<\/a>

From the paper \u201cBig Data: Astronomical or Genomical?\u201d (Stephens et al. 2015<\/a>).<\/em><\/p><\/div>\n

We are at a critical point! We need to make sure that all the data being generated – and the methods to analyse it – are open and transparent. Science fundamentally relies on the ability to test a hypothesis, under controlled conditions, and get a predicted result consistently. Without access to all the data, code and documented methods, reproducing an experiment might be impossible or extremely time-consuming. For example, it might take take a lab months to figure out the exact conditions used in an experiment originally done by another lab (or the same lab years before). Additionally, some private companies are trying to capitalise on closed data (by creating data silos\/walled gardens), so providing open data alternatives could have a huge positive impact on healthcare.<\/p>\n

Openness<\/strong> is so fundamental to Science that it\u2019s ironic that \u201cOpen Data<\/strong>\u201d and \u201cOpen Source<\/strong>\u201d are concepts we need to fight for. Sadly, it seems that the default in science is now Closed Science. It\u2019s difficult to say how this came about, but the main causes seem to be a mix of misplaced incentives from fundings bodies and cultural issues in academia. But things are improving! I hope that during this fellowship we can make a significant contribution towards boosting the state of Open Science. I hope we can improve best practices in reproducibility and create better credit attribution for scientific outputs such as code.<\/strong><\/p>\n

For reproducibility sake, any code is better than no code. However for reusability (i.e., take an analysis and run it on a different dataset), we need good, maintained, tested code. Thus sometimes communities arise to develop a common library or set of tools. During my PhD, I developed some Node.js (JavaScript) code for my research that I released under an Open Source license. This attracted contributors, and thus the Bionode.io<\/a> community was born<\/strong>.<\/p>\n

Bionode.io motto is “modular and universal bioinformatics”.<\/strong> Our aim is to build highly reusable code and tools that can run everywhere (e.g., a High-Performance Computing server, or a user’s browser) by leveraging Node.js and its fast growing community. Another distinguishable feature of Bionode is its architecture based around Node.js Streams<\/a>, which we believe is essential for processing genomic big data in real-time and in a scalable way.<\/p>\n

Personally, I gained a lot from the Bionode project. For example, I’ve been invited to give talks at places such as the Sanger Institute<\/a> and participate in a hackathon in Japan<\/a> (!). But more importantly, it\u2019s been really exciting to see the Bionode.io communitty grow. This year, with sponsorship of Repositive.io<\/a>, we organised a hackathon at Google Campus London<\/a>. We got around 40 participants and a good mix of half scientist and half JS developers – we managed to prototype five tools in only a day!<\/a> We are going to do a light version of this hackathon as a three hour workshop at MozFest 2016.<\/p>\n

\"bionode-and-dat-at-sanger\"<\/a>

Me and the founder of Dat<\/a>, Max Ogden<\/a>, at the Sanger Institute<\/a> before giving our talks (November 2014).<\/em><\/p><\/div>\n

 <\/p>\n

\"biohack15\"<\/a>

Biohackathon 2015 <\/a>in Nagasaki, Japan. I was invited to give a talk about Bionode, and worked during a week on several things, including GUIX<\/a>, Docker<\/a> and CWL<\/a>.<\/em><\/p><\/div>\n

 <\/p>\n

\"bionode-hackathon2016\"<\/a>

Bionode hackathon 2016<\/a>\u00a0day at Google Campus London<\/a>, sponsored by Repositive.io<\/a>, where 40 participants (scientists and JavaScript developers) prototyped five new tools to fetch and process biological data.<\/em><\/p><\/div>\n

Bionode also supported a student (Julian Mazzitelli<\/a>) working full-time for three months under a Google Summer of Code<\/a> fellowship from the Open Bioinformatics Foundation<\/a>. He developed a workflow engine in Node.js<\/a> with the aim of making it easier to write modular and scalable bioinformatics pipelines, but his tool is applicable in any data processing workflow in other fields.<\/p>\n

\"julian-mazittelli\"<\/a>

Julian Mazzitelli<\/a> dedicated three months in 2016 to Bionode as a Google Summer of Code<\/a> student and we finally met in Toronto during the Mozilla fellowship onboarding<\/a>.<\/em><\/p><\/div>\n

Bionode.io has gone further than I expected as my part-time project and received the help of some occasional contributors. I now intend to dedicate full-time to it with this fellowship bandwidth to give it the push it needs to take off.<\/p>\n

My goals are to make Bionode.io:<\/strong><\/p>\n