<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by yoyehudi on Medium]]></title>
        <description><![CDATA[Stories by yoyehudi on Medium]]></description>
        <link>https://medium.com/@yoyehudi?source=rss-3d25a2d2bfc8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ViDmgy455qJuwuBcKBMQUQ.png</url>
            <title>Stories by yoyehudi on Medium</title>
            <link>https://medium.com/@yoyehudi?source=rss-3d25a2d2bfc8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:01:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yoyehudi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Announcing OSScience.org, a curated spotlight on good practice in research code and hardware]]></title>
            <link>https://osscience.org/announcing-osscience-org-a-curated-spotlight-on-good-practice-in-research-code-and-hardware-a26253aca7e2?source=rss-3d25a2d2bfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a26253aca7e2</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[open-hardware]]></category>
            <category><![CDATA[open-science]]></category>
            <category><![CDATA[open-data]]></category>
            <dc:creator><![CDATA[yoyehudi]]></dc:creator>
            <pubDate>Wed, 26 May 2021 15:52:01 GMT</pubDate>
            <atom:updated>2021-05-26T15:52:01.316Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Software, hardware tooling, and code are integral to research. 7 out of 10 researchers report that they couldn’t work without software, and scientific hardware is typically forbiddingly expensive to purchase and maintain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y0j12mdVj1lOfHdz-qLnHg.jpeg" /><figcaption>Software, hardware tooling, and code are integral to research.</figcaption></figure><h3>Sharing work openly makes science stronger</h3><p>In many cases, the software, code, or scripts used by researchers form part of their scientific method, aka a <a href="https://www.protocols.io/what-is-protocol">protocol</a>. Research method needs to be clear and well-described, such that other researchers can peer-review and/or repeat the work.<br> <br> An effective way to make sure that research code is peer-reviewable and re-usable is to put it online, and <a href="https://choosealicense.com/">add a licence that permits re-use</a> — aka making it <a href="https://opensource.org/osd">Open Source</a>.</p><p>Science needs open hardware, too. Instructions to make machines and tooling to perform science can also be shared openly — and in the context of research and science, this can make a massive impact, especially when using readily available materials that are accessible from any common setting. The <a href="https://openhardware.science/gosh-manifesto/">Global Open Source Hardware Manifesto</a> explains this better than we ever could.</p><h3>Shining a spotlight on the good</h3><p>Making your work open source isn’t always as straightforward as simply putting it online, though — <a href="https://www.software.ac.uk/blog/2020-12-17-ten-arguments-against-open-science-you-can-win">many barriers exist that may make it harder to share</a> (institutional, cultural, and personal), and even if the code is online, there is a range of ways to make sharing more effective and useful for others, from writing good documentation, creating automated testing pipelines to prevent bugs re-occurring, making it easy for others to report bugs or contribute new features, incredible training, great accessibility or internationalisation features, or building a community of users or developers.</p><p><a href="http://osscience.org/">OSScience.org</a> represents a curated view into what makes open source science good, including “<a href="https://doi.org/10.1371/journal.pcbi.1005510">good enough</a>” practices, recognising that few projects are perfect but many have specific elements that demonstrate good standards.</p><h3>Call for editors and collaborators</h3><p>Read more about the <a href="https://osscience.org/become-a-guest-editor-6cb2d53c08ca">editor positions</a> available. To apply, please email <a href="/service/mailto:O.Science@wellcome.org">O.Science@wellcome.org</a> to express your interest, and a short statement why you think you’re a good candidate. We expressly do NOT require a PhD or information about the number of scientific publications — instead we’re looking for people with experience in open source software development, documentation, community management, and leadership.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a26253aca7e2" width="1" height="1" alt=""><hr><p><a href="https://osscience.org/announcing-osscience-org-a-curated-spotlight-on-good-practice-in-research-code-and-hardware-a26253aca7e2">Announcing OSScience.org, a curated spotlight on good practice in research code and hardware</a> was originally published in <a href="https://osscience.org/">Open Source Science</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good software practice is for everyone]]></title>
            <link>https://medium.com/wellcome-digital/good-software-practice-is-for-everyone-4042ccc0ec24?source=rss-3d25a2d2bfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4042ccc0ec24</guid>
            <category><![CDATA[research-software]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[good-practices]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability]]></category>
            <dc:creator><![CDATA[yoyehudi]]></dc:creator>
            <pubDate>Thu, 12 Nov 2020 10:07:05 GMT</pubDate>
            <atom:updated>2020-11-12T10:07:05.789Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Three people look over pen and paper sketched mockups for a user interface. In the background is a computer and postits" src="https://cdn-images-1.medium.com/max/1024/1*zGHaOHYGV4LRCqSlyAtMBg.jpeg" /><figcaption>Early stage software design tests help to make software easier to use</figcaption></figure><p><em>Authors: Yo Yehudi, Katie Taylor, Aoife Spengeman</em></p><blockquote>“Design stuff isn’t a good use of your time. So long as it works, it doesn’t really matter if it looks pretty or not.” <br>- Anonymous principal investigator</blockquote><h3>Hulk smash computer</h3><p>Think back to a recent time when you wanted to say a few rude words, or imagined tossing your computer out the window, when a program wasn’t doing what you hoped, or forced you to do it in a painfully laborious way. Computers are supposed to make many tasks easier, but sometimes can end up being a huge hassle instead. I’ve heard many people say “I’m not very good at X”, when after a few minutes of investigation it becomes pretty clear that the software that they’re using is at fault, rather than the person sitting in front of the computer.</p><p>Part of the process of designing software tools, if you want them to be good, is to run research, often known as “user testing”, “usability testing” or “UX (user experience) research”. We generally prefer the term “user research” over “user testing”, as research can apply more broadly to user interviews, diary studies, and other meaningful research types that can improve a software user’s experience. The idea is that by observing people using the software we’ve created, we can discover where the tricky bits are, the places where doing something takes a lot of time or isn’t intuitive, and probably find some bugs as well. Other types of user research come before any code is implemented, to help us understand the problem we are trying to solve. To learn more about different <a href="https://www.nngroup.com/articles/which-ux-research-methods/">UX research methods and when each one is appropriate</a>, consider visiting <a href="https://www.nngroup.com/">Nielsen-Norman</a>, a research group that provides evidence-based advice on UX.</p><p>The reason user research is needed is because software engineers may not think of all the real-world scenarios that come into play when they’re designing their work, and since they’ve created it themselves, they always know exactly what a given button does or where to click to move on to the next step. They sometimes forget that others can’t see into their brains to understand the design intent. This isn’t a dig at software engineers — I’m one myself — but a simple statement of fact: we’re humans, and we can really only see things from our own perspective. Bringing in others from a variety of different viewpoints always results in a better product design.</p><p>The quote at the head of this article was a statement from a principal investigator I’d approached — let’s call them Jesse — hoping to use their work as a case-study for software I was designing that would help scientists analyse their experiment results. I’d sketched an idea for what the software interface might look like on paper, using my best guesses as to how it might be used by someone else, and then I’d converted those pen-and-paper sketches into slightly prettier mockups on my computer. I wanted to ask Jesse, a potential user of my software, if they could help test the mockups based on the real scientific data they had. This almost certainly would have revealed shortcomings in my thinking that I could then improve upon. Their derogatory response effectively shut down the conversation before it got started — they considered it to be nothing more than making the design pretty and couldn’t see any point going ahead, even though UX is so much more.</p><h3>UX in science, research, and health</h3><p>Jesse’s attitude towards UX research is unfortunately reasonably common, both within science/research and elsewhere. Despite this, having software that works and is efficient (maybe even pleasurable?!) to use <a href="https://www.nngroup.com/articles/usability-101-introduction-to-usability/">is hugely important</a> — increasing usability of a tool offers time savings, reduces mistakes and the need for training, and indeed can be the difference between someone using a tool at all and abandoning it in frustration. Better UX broadens your range of potential users — people are more likely to stick with your software and more likely to recommend it to others.</p><p>A couple of years ago I attended a UX in life sciences conference known as <a href="https://uxls.org/">UXLS</a>. The conference was reasonably commercial-oriented, so many big pharma organisations were talking about ways UX was applied in life science contexts, and when they referred to software created by scientists, the opinions were not always kind about how good the UX was. As someone working on scientific software at the time, this hit a nerve for me — I always tried my hardest to make things pleasant to use — but the point is nevertheless a reasonable one: all too often people creating software in research don’t value UX or don’t feel like they can justify spending time on it.</p><p>Good UX can make or break scientific results or output. Peter Cock wrote <a href="https://blastedbio.blogspot.com/2015/12/blast-max-target-sequences-bug.html">a series of blogs</a> running back to 2015 about a poorly documented feature in <a href="https://blast.ncbi.nlm.nih.gov/Blast.cgi?PAGE_TYPE=BlastDocs&amp;DOC_TYPE=Download">BLAST+</a> (<a href="https://en.wikipedia.org/wiki/BLAST_(biotechnology)">a scientific software tool for analysing DNA and RNA sequences</a>) that doesn’t behave in the way people might intend, and could easily result in scientific results being misunderstood, incorrect, or impossible to reproduce. Testing designs with real-life users won’t ever pick up everything, but it can help reveal underlying assumptions like this one and ensure they aren’t used incorrectly by accident.</p><h3>Moving Forwards: Good practice doesn’t stop at UX</h3><p>If software for science and health is to be useful and worthwhile funding, it should be good to use (good UX for software that’s being re-used by people other than its creator is never a waste of time), and make people want to adopt it, but it should also be easy to maintain and update. This reaches further than user experience, to topics such as community management for open software — integral if you want to create pathways for others to contribute to your work — and typical “good practices” for software engineering such as testing, continuous integration, and documentation for users and developers.</p><p>In order for researchers who write code — or who get others to write code for them — to feel like best practices can be justified, funders, research institutes and journals all need to make clear that good quality research code and software is not wasteful, and not just a nice “fluffy” addition — but instead is time well-spent on creating a first-class research output.</p><p><em>Title image: Photo by </em><a href="https://unsplash.com/@uxindo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>UX Indonesia</em></a><em> on </em><a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Unsplash</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4042ccc0ec24" width="1" height="1" alt=""><hr><p><a href="https://medium.com/wellcome-digital/good-software-practice-is-for-everyone-4042ccc0ec24">Good software practice is for everyone</a> was originally published in <a href="https://medium.com/wellcome-digital">Wellcome Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BOSC 2017 Day 2, Part 3: Keynote #BOSC2017 #ISMBECCB]]></title>
            <link>https://medium.com/plos-comp-biol-field-reports-2016/bosc-2017-day-2-part-3-keynote-bosc2017-ismbeccb-5a1598be50c4?source=rss-3d25a2d2bfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a1598be50c4</guid>
            <category><![CDATA[ismb]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[virus]]></category>
            <category><![CDATA[bosc]]></category>
            <category><![CDATA[bioinformatics]]></category>
            <dc:creator><![CDATA[yoyehudi]]></dc:creator>
            <pubDate>Fri, 28 Jul 2017 11:22:14 GMT</pubDate>
            <atom:updated>2017-08-09T13:18:36.358Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>In which Nick Loman teaches us about making real-world differences to epidemics using genomics, the importance of speedy response to viral outbreaks, and sequencing viruses in the field with no pants. Previous posts: </em><a href="https://medium.com/@yoyehudi/bosc-2017-day-1-fbe73f01de2e"><em>Day 1</em></a><em> of </em><a href="https://www.open-bio.org/wiki/BOSC_2017_Schedule"><em>BOSC</em></a><em>, </em><a href="https://medium.com/@yoyehudi/bosc-2017-day-2-part-1-bosc2017-ismbeccb-9d4d8fda000c"><em>Day 2 part 1,</em></a><em> and </em><a href="https://medium.com/@yoyehudi/bosc-2017-day-2-part-2-bosc2017-ismbeccb-af4bf4a63a84"><em>Day 2 part 2</em></a><em>.</em></p><p>Nick Loman’s talk was the perfect mix of entertaining humour and uplifting real-world-impacting science. As I mentioned in a previous post, he nearly forgot to provide a title for his talk, which resulted in some gentle, but polite Twitter shaming from the BOSC Twitter account:</p><h3>BOSC on Twitter</h3><p>@pathogenomenick hasn&#39;t chosen a title for his #BOSC2017 keynote talk, so we&#39;re crowd-sourcing it. What do YOU think it should be?</p><p>Amongst the <a href="https://twitter.com/OBF_BOSC/status/874646469764014082">entertaining responses</a> was Nick’s favourite, “Talky McTalkface”, so without further ado, he got stuck into the talk.</p><h3>Peter Cock on Twitter</h3><p>BOSC2017 final talk, open data keynote from @pathogenomenick &quot;Talky McTalkface&quot; https://t.co/KnC06pXr9Q</p><p>The basic premise of the talk was the fact that viruses can have their genomes sequenced, and when you sequence the virus in enough patients, you are able to trace where the virus came from, and where it has been.</p><h3>Ebola</h3><p>Nick’s tale began when Ebola was sweeping through Africa a few years ago. When his team decided to get involved with sequencing the virus, they had a problem: for some strange reason, courier companies were reluctant to ship samples of a virulent, deathly virus internationally. So, after some deliberation, they decided to send the sequencer to the virus, rather than the virus to the sequencer!</p><p>Nick’s student, <a href="http://www.birmingham.ac.uk/schools/biosciences/staff/students/quick-joshua.aspx">Josh Quick</a>, was willing to take on this grand humanitarian adventure. Armed only with a single large suitcase of lab equipment, <a href="https://nanoporetech.com/products/minion">a tiny portable sequencer</a>, and <a href="https://twitter.com/yoyehudi/status/889135574149472256">a small personal bag for his pants</a>, Josh was shipped off to <a href="https://en.wikipedia.org/wiki/Guinea">Guinea</a>.</p><p>Useful results began to pop through after a couple of days, and better yet, another group had begun similar, but less portable sequencing in the neighbouring country of <a href="https://en.wikipedia.org/wiki/Sierra_Leone">Sierra Leone</a>. Combining the two sets of results (open data sharing!) allowed higher-quality analyses than might have been available otherwise — for example, it quickly became clear from the way the virus lineages were moving across borders that border quarantine control needed to be tightened.</p><p>The sequencing eventually allowed the entire outbreak to be traced down to an initial index case. “Patient zero” was probably a child, unlucky enough to be playing near a burnt out tree where they managed to pick up the virus. Whilst the exact animal source isn’t clear, it’s possible it might have been bats.</p><p>Given the vast amount of data they’d gathered, visualisation of it was a logical next step for further analysis. <a href="http://www.nextstrain.org/">NextStrain</a> at the time was focused primarily on the spread of influenza outbreaks, but they expanded their efforts. You can explore the data yourself here: <a href="http://www.nextstrain.org/ebola?c=division&amp;r=division">http://www.nextstrain.org/ebola</a>. Useful takeaways from the visualisations include the fact that the virus was primarily clustered in urban centres, and that it would often be exported long-distance to other areas. Nick even mentioned someone who’d survived the virus two years ago, but still had enough viral load to be contagious! (<a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4817224/">Paper</a>)</p><p>Nick also showed us an animation that was beautiful, but staggeringly heartbreaking. It visualised the spread of the disease from location to location, with different colours indicating evolved sub-strains. As pretty as the graph may be, I can’t help but remember that it’s mapping human suffering.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fj4Ut4krp8GQ%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dj4Ut4krp8GQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fj4Ut4krp8GQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0ca6cef4d1d6cc4936a885c82e97f6bd/href">https://medium.com/media/0ca6cef4d1d6cc4936a885c82e97f6bd/href</a></iframe><h3>A different virus rears its head</h3><p>About the same time Ebola began to truly fade, a new outbreak occurred, this time in South America: Zika.</p><p>Logically, fast response times are incredibly important in terms of preventing outbreaks from becoming epidemics or pandemics. Nick’s team applied for a grant in hopes of heading out to the field to sequence Zika. The turnaround was remarkable — two weeks after the grant application, they had the funding in hand, and were able to set out, as a team, on a South American gene-sequencing road trip.</p><p>This time results were a bit harder to get. As Nick explained, when someone is sick with Ebola, their viral load is very high, so sequencing the virus isn’t too hard. By comparison, however, the viral load in an afflicted Zika victim isn’t nearly as high, making results far less useful. Others eventually did have more success with this protocol, sequencing Zika in lab conditions.</p><h3>Yellow fever and beyond</h3><p>The rapid action in terms of funding, sharing results openly, and heading to the field all had their part in creating a protocol that was re-usable by others; Nick reported that sequencing of the <a href="http://www.who.int/csr/don/04-april-2017-yellow-fever-brazil/en/">Brazilian yellow fever outbreak</a> is being managed successfully by researchers, without his team needing to head out themselves.</p><h3>Wrap up — what a great talk!</h3><blockquote>Outbreaks are inevitable; epidemics are not — Peter Piot</blockquote><p>Sage words, quoted to the audience by Nick Loman. The earlier we get involved in a viral outbreak, the less likely it is to become an epidemic or pandemic. Hopefully, in the future, our viral surveillance will be sufficient that we will be able to prevent further epidemics and loss of life; in the meantime, the work Nick and his team have been performing is truly astonishing, and probably couldn’t have been achieved without open data sharing, swift funding calls, and a dynamite community.</p><p>This ends the series of posts I’ve been writing for ISMB/ECCB and specifically the BOSC 2017 COSI. Thanks for reading!</p><p><strong><em>Disclaimer: </em></strong><em>Any views expressed are my own, not necessarily those of PLOS.</em></p><h4>References:</h4><p>Quick J, Loman NJ, Duraffour S, Simpson JT, Severi E, Cowley L, et al. Real-time, portable genome sequencing for Ebola surveillance. Nature. 2016; 530: 228–232.</p><p>doi: <a href="https://dx.doi.org/10.1038%2Fnature16996">10.1038/nature16996</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a1598be50c4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/plos-comp-biol-field-reports-2016/bosc-2017-day-2-part-3-keynote-bosc2017-ismbeccb-5a1598be50c4">BOSC 2017 Day 2, Part 3: Keynote #BOSC2017 #ISMBECCB</a> was originally published in <a href="https://medium.com/plos-comp-biol-field-reports-2016">PLOS Comp Biol Field Reports Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BOSC 2017 Day 2, Part 2 #BOSC2017 #ISMBECCB]]></title>
            <link>https://medium.com/plos-comp-biol-field-reports-2016/bosc-2017-day-2-part-2-bosc2017-ismbeccb-af4bf4a63a84?source=rss-3d25a2d2bfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/af4bf4a63a84</guid>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[bioinformatics]]></category>
            <category><![CDATA[bosc]]></category>
            <category><![CDATA[ismb]]></category>
            <dc:creator><![CDATA[yoyehudi]]></dc:creator>
            <pubDate>Tue, 25 Jul 2017 16:05:23 GMT</pubDate>
            <atom:updated>2017-07-25T16:42:44.519Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>This is the part of the story in which I summarise the final BOSC lightning talks, open data panel, and FAIR bingo. You may wish to read about </em><a href="https://medium.com/@yoyehudi/bosc-2017-day-1-fbe73f01de2e"><em>Day 1</em></a><em> of </em><a href="https://www.open-bio.org/wiki/BOSC_2017_Schedule"><em>BOSC</em></a><em>, or </em><a href="https://medium.com/@yoyehudi/bosc-2017-day-2-part-1-bosc2017-ismbeccb-9d4d8fda000c"><em>Part 1 of Day 2</em></a><em>, before you read this section!</em></p><h4>ToolDog</h4><p>I left off part way through the late-breaking lightning talks in my previous post. Picking back up, we were treated to a short talk about<a href="https://github.com/bio-tools/ToolDog"> ToolDog</a> by Kenzo-Hugo Hillion. ToolDog provides common descriptive wrappers for tools in <a href="https://www.elixir-europe.org/">Elixir</a>’s bioinformatics <a href="https://bio.tools/">tool registry</a>. You can see a <a href="https://f1000research.com/posters/6-767">poster about it here on F1000</a>.</p><h4>BioThings SDK</h4><p>Chunlei Wu gave the second <a href="http://biothings.io/">BioThings</a> talk of the conference, focusing on the <a href="http://biothingsapi.readthedocs.io/en/latest/">SDK</a>, which gives you the tools to create your own BioThings API.</p><h4>Standing on the shoulders of giants to fight superbugs</h4><p>Kai Blin spoke about the scary prospect of antibiotics potentially stopping working altogether at some point in the not-too-far future — as we all know, antibiotics are regularly overused and misused. He followed up by giving us a ray of hope and inspiration: there <em>are </em>efforts to discover new ways to fight off infection. Often, these are computational efforts.</p><p>And what software stack does science use, overwhelmingly? It’s open source. We may contribute just a line of code here, a pull request there, or maybe even maintain a larger package — but without the work of open source software, the future might be a bleaker place than it is. Three cheers for open source!</p><h3>Lunch and BoFs</h3><p>I was terribly torn about which BoF — “Birds of a Feather” — session to attend at lunchtime. On the one hand, there was the <a href="http://joss.theoj.org/">JOSS</a> BoF, and the <a href="https://medium.com/plos-comp-biol-field-reports-2016/bosc-2017-day-2-part-1-bosc2017-ismbeccb-9d4d8fda000c#6a56">JOSS talk earlier in the day</a> had been really interesting. On the other hand, the <a href="https://elifesciences.org/about">eLife</a> BoF sounded so very interesting, too!</p><p>I flipped a mental coin and ended up at eLife, where Naomi Penfold ran a fantastically targeted session, discussing ways to handle scientific code <em>appropriately</em>, given that traditional models of publishing papers can result in lost and obfuscated data, code that can’t be re-run, and poorly examined code that may not have undergone any peer review at all.</p><p>I was fascinated by the discussions about how this could be solved, and how much of the onus is on the journal. Early on I argued that journals being strict about software quality and reproducibility was just sensible, a necessary step to create valid science, but it quickly became clear that my viewpoint was somewhat naive — if a journal is too laborious to submit your work to, many people will simply go to a less rigorous journal, because a lower quality bar is an easier bar to pass. The summary of the discussion was taken in real time by Naomi on <a href="https://public.etherpad-mozilla.org/p/publishing-reproducible-research-BOSC2017">etherpad</a>.</p><h3>Hans Zauner on Twitter</h3><p>One take home message of the BoF: &quot;Journals need to allow people to publish in the way they practise.&quot; #BOSC2017</p><h3>Afternoon Sessions</h3><h4>RADAR-CNS</h4><p>Nivethika Mahasivam gave a strong technical overview of <a href="https://www.radar-cns.org/">RADAR-CNS</a>, an open source project which creates tooling for tracking personal medical devices such as wearables and phones. It’s designed to enable real-time and retrospective analysis of the data, helping people with depression, multiple sclerosis and epilepsy. It must be incredibly rewarding to work on a project that helps people out like this!</p><h4>WikiData</h4><p>Andrew Su introduced <a href="https://www.wikidata.org/wiki/Wikidata:Main_Page">WikiData</a> to the audience. You’re probably familiar with <a href="https://en.wikipedia.org/wiki/Main_Page">Wikipedia</a>, which shares data in a human-readable format. WikiData represents the same types of data, but in a format designed to be read by machines, and consumed via <a href="https://en.wikipedia.org/wiki/SPARQL">SPARQL</a> (pronounced “sparkle”). He also pointed out that <a href="https://creativecommons.org/licenses/by/2.0/">CC-BY</a> — a <a href="https://creativecommons.org/">Creative Commons</a> licence which permits re-use of the content, but requires attribution of the original source — is often a sub-optimal licence and can make re-using data very difficult. It’s hard enough to comply with CC-BY that data under this licence can’t be used on Wikidata. Instead, consider using <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC-0</a>, a dedicated public domain licence:</p><h3>Marc RobinsonRechavi on Twitter</h3><p>Important note by @andrewsu: wikidata can only integrate CC0 resources #ismbeccb #bosc2017</p><h4>Open Clinical Data &amp; ClinVar</h4><h3>GigaScience on Twitter</h3><p>Interesting to see Steve Lincoln from @Invitae presenting clinical data examples in the #opendata track of #BOSC2017 #ismbeccb</p><p>Steve Lincoln from <a href="https://www.invitae.com/en/">Invitae</a> discussed publishing clinical datasets publicly, highlighting <a href="https://www.ncbi.nlm.nih.gov/clinvar/">ClinVar</a> as an open clinical data aggregator. Invitae boasts the <a href="https://www.ncbi.nlm.nih.gov/clinvar/docs/submitter_list/">third-highest submission rate on the portal</a> — something to be extremely proud of!</p><h4>BioCADDIE</h4><p>Philippe Rocca-Serra presented <a href="https://biocaddie.org/">BioCADDIE</a>, an index ecosystem for biomedical / healthcare data. Explore the data yourself at <a href="https://datamed.org/">datamed.org</a></p><h4>Bioschemas</h4><p>“<a href="https://twitter.com/search?q=%23BOSC2017%20FAIR%20bingo&amp;src=typd">FAIR Bingo</a>” became a running joke at BOSC; as one of the many original creators of the FAIR data principles of Findability, Accessibility, Interoperability, and Reproducibility (<a href="https://www.nature.com/articles/sdata201618">paper</a>), it’s only natural that Carole Goble would introduce us to <a href="http://bioschemas.org/">Bioschemas</a>, an effort to make the biological web FAIRer. The Bioschemas working group includes quite a few organisations, including my own workplace, <a href="http://intermine.org/">InterMine</a>.</p><h3>yoyehudi🏳️‍🌈 on Twitter</h3><p>@bioschemas extends https://t.co/ZElOmPKpoV and specifies minimum information to describe a biological entity. #bosc2017 #ismbeccb</p><h4>Brassica Information Portal</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cyj660B7o17bTjiFl_z9wQ.jpeg" /><figcaption>Image Credit: U.S. Department of Agriculture/ Flickr (public domain)</figcaption></figure><p>The <a href="https://bip.earlham.ac.uk/">Brassica Information Portal</a> was introduced to us by Annemarie Eckes. Brassicas include cabbage, mustard, broccoli, and rapeseed/canola, among other delicious foodstuffs. The portal encompasses both a GUI and an API, allowing researchers to access and update data programatically or graphically, as preferred.</p><h3>Open Data — Standards, Opportunities and Challenges</h3><p>This panel discussion drew together several of the speakers from BOSC: Madeleine Ball, who gave <a href="https://medium.com/plos-comp-biol-field-reports-2016/bosc-2017-day-1-fbe73f01de2e">the Open Human keynote on day 1</a>, Carole Goble, who introduced Bioschemas earlier in the day, Nick Loman, who delivered the keynote after this panel, and Andrew Su, who discussed WikiData and CC0 licensing. Mónica Muñoz-Torres chaired the discussion.</p><p>Some of the key points:</p><h4>Attitudes toward data sharing: a generational problem?</h4><p>Carole Goble shared the interesting but somewhat disappointing fact that whilst younger people (e.g. PhD students) are generally pro- open data, PIs in projects are more likely to be resistant to it, considering the challenges of time and money spent to be too great to justify the effort. In an ideal world, data would be open by default (excluding scenarios where open data is inappropriate, such as personal privacy, health, etc.), creating an environment where anyone who <em>isn’t</em> sharing their data appears to be the odd one out.</p><h4>Data “Flirting”</h4><p>A phrase shared by Carole Goble: incomplete data sharing can be used as a marketing ploy, revealing just enough to interest others without actually providing anything of real use!</p><h4>Open data: how do you prevent its misuse?</h4><p>An insightful audience member asked the panel how to prevent open data from being misused. Madeleine Ball responded to point out that truly open data may indeed be misused, and there isn’t really any way to stop it, without making the data less open. A double-edged sword, perhaps?</p><p>Nick Loman further pointed out that Open Source also cuts both ways, with North Korea benefiting from Open Source software as much as anyone else. Indeed, when I googled this briefly, I noted that Wikipedia has an article on <a href="https://en.wikipedia.org/wiki/Red_Star_OS">Red Star OS</a>, a modified North Korean <a href="https://en.wikipedia.org/wiki/Linux">Linux</a> distribution.</p><h4>Not all data should be open</h4><p>This seems surprising when coming from a panel discussing open data, but even pushing the issues of ethics in personal genomics, health, location, privacy, etc., there are other reasons to keep data hidden.</p><p>Conservation and ecology are good examples of this. Publishing the location of rare, interesting, or vulnerable animals could result in their harm or death, whether the people using that data are malicious or merely curious to see the animal. I actually had an experience with this myself recently — I live in the <a href="https://en.wikipedia.org/wiki/The_Fens">Cambridgeshire Fenlands</a>, (exact locations intentionally kept vague) and whilst birdwatching I was privileged to spot a pair of <a href="https://www.rspb.org.uk/birds-and-wildlife/bird-and-wildlife-guides/bird-a-z/c/crane/index.aspx">cranes</a>, a bird so rare in the UK that their single breeding site is kept secret for their own safety.</p><h4>Re-digitisation</h4><p>Hilmar Lapp mentioned from the audience that sometimes merely having data “open” isn’t enough — it needs to be in a sensible format. This is probably a place where the academic publishing model has room for improvement — for example, large amounts of tabular data shouldn’t be converted into PDF format, where one might have to literally re-type the entire dataset by hand in order to re-use the data.</p><p>He further asserted that the act of re-digitising data is a transformative enough act that it’s not only legal to licence the data openly, but is in fact a duty, lest the same data be re-digitised repeatedly by different parties. (A side note — can anyone verify this claim? I’d love to hear more.)</p><p>In my mind, this problem is kin to the <a href="https://en.wikipedia.org/wiki/Digital_dark_age">Digital Dark Age</a>, the very real problem that as technology moves on, we’ll no longer have the hardware or software to read old data formats.</p><p>Thanks for reading with me this far. I’ll finish up my final post, coming soon, which will summarise the keynote for Day 2 of BOSC, an inspiring talk delivered by Nick Loman, about making a difference in epidemic-infested countries by sequencing the genomes of viral outbreaks.</p><p><strong><em>Disclaimer: </em></strong><em>Any views expressed are my own, not necessarily those of PLOS.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af4bf4a63a84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/plos-comp-biol-field-reports-2016/bosc-2017-day-2-part-2-bosc2017-ismbeccb-af4bf4a63a84">BOSC 2017 Day 2, Part 2 #BOSC2017 #ISMBECCB</a> was originally published in <a href="https://medium.com/plos-comp-biol-field-reports-2016">PLOS Comp Biol Field Reports Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BOSC 2017, Day 2, part 1 #BOSC2017 #ISMBECCB]]></title>
            <link>https://medium.com/plos-comp-biol-field-reports-2016/bosc-2017-day-2-part-1-bosc2017-ismbeccb-9d4d8fda000c?source=rss-3d25a2d2bfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d4d8fda000c</guid>
            <category><![CDATA[bosc]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[bioinformatics]]></category>
            <category><![CDATA[ismb]]></category>
            <category><![CDATA[reproducibility]]></category>
            <dc:creator><![CDATA[yoyehudi]]></dc:creator>
            <pubDate>Sun, 23 Jul 2017 23:45:00 GMT</pubDate>
            <atom:updated>2017-07-25T16:20:14.160Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>For a BOSC Intro, see my </em><a href="https://medium.com/@yoyehudi/bosc-2017-day-1-fbe73f01de2e"><em>Day 1 post</em></a></p><p>BOSC talks today were more varied, with themes running from citizen science to Open Data, a great panel towards the end of the day, and an entertaining and inspiring keynote from Nick Loman, that was <em>nearly</em> entitled “Talky McTalkface” when he failed to turn in an appropriate title to the conference organisers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CODVbI-tC8PSUGcN62xi-g.jpeg" /><figcaption>Beer photo by Landfeldt. Creative Commons <a href="https://creativecommons.org/licenses/by-nc-nd/2.0/">CC BY-ND 2.0</a> via <a href="https://www.flickr.com/photos/landfeldt/2400107273">https://www.flickr.com/photos/landfeldt/2400107273</a></figcaption></figure><h3>Community building and citizen science sessions</h3><h4>Beer Decoded</h4><p>Day 2 of BOSC opened with a subject close to many a person’s heart: beer. Jonathan Sobel introduced us to <a href="http://www.genome.beer/">Beer Decoded</a>, a citizen science beer metagenome sequencing project. He discussed some of the barriers to citizen science, particularly funding — it’s harder to get grants for scientific projects that have no academic body backing them. Eventually they turned to <a href="https://www.kickstarter.com/projects/489252126/beerdecoded-the-1000-beer-genomes">kickstarter</a>, allowing beer enthusiasts worldwide to get their inner geek on and fund delicious science. In total, 39 beer samples were analysed (via science and probably a tasting or two, too) and open sourced on <a href="https://github.com/beerdecoded/Beer_ITS_analysis">GitHub</a>.</p><h4>Community Curation &amp; Apollo Project</h4><p>Jokingly lamenting how hard it is to follow on from a talk about beer, Monica Munoz-Torres introduced Apollo as a curation tool, describing it as a “social network for curators” where the social objects were genomes and their annotations. Following a web-based re-release and community engagement plan, Apollo saw its use soar significantly over the last few years, now boasting around 150 servers and 1,200 unique users. The large open source community helped by feeding back new developments into the project, helping Apollo grow even further.</p><h4>JOSS — the Journal for Open Source Software</h4><p>Getting credit for your academic software without having to write papers that may be ill-suited to your needs: every scientific software engineer’s dream. <a href="http://joss.theoj.org/">JOSS</a> aims to enable this with a completely GitHub-based submission system, the only real requirements being little more than a paragraph or two of description alongside good quality open source code. It’s also free!</p><p>Reviewers, submitters, and editors all manage new submissions on GitHub, keeping the process transparent and speedy. Naturally, for a geeky project, the <a href="https://github.com/whedon">JOSS GitHub bot</a> is named, pleasingly, “<a href="https://en.wikipedia.org/wiki/Joss_Whedon">Whedon</a>”.</p><h4>Galaxy Training</h4><p>Bérénice Batut provided an overview of <a href="https://galaxyproject.org/">Galaxy</a>’s training network. Built in markdown, centralised neatly on GitHub, with metadata, Zenodo DOIs, and crediting the creators of the content. <a href="https://galaxyproject.org/teach/gtn/">The training network</a> addresses the strong need for formal computing training amongst biologists — too many are forced to pick up skills on the job, either self-taught or with the help of a colleague. Training packages are also automatically exported to <a href="https://tess.elixir-europe.org/">Elixir’s TESS training portal</a>!</p><h3>Lightning talks</h3><p>Next came two short talks, with Dexter Pratt discussing <a href="https://t.co/FCtiuiHBFp">NDex</a>: infrastructure for biological-network community sourced content — or in plainer English, it allows communities to be created around tools for biological networks of any kind.</p><h4>Bioinformatics training in Africa</h4><p>Nicola Mulder shared the inspiring story of <a href="http://www.h3abionet.org/">h3abionet</a>, bringing bioinformatics training to places across Africa, including rural areas with poor or no internet connection. Lectures were pre-recorded and also delivered online live, with the recordings available offline in case of connectivity problems.</p><h4>Galaxy updates</h4><p>Martin Cech brought us up-to-date with new <a href="https://galaxyproject.org/">Galaxy</a> developments, including a nice <a href="https://jupyter.org/">Jupyter</a> notebook integration (<a href="http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005425">paper</a>) and a gradual transition to using <a href="https://conda.io/docs/">Conda</a> for package management.</p><h4>Continuous Analysis</h4><p>Brett Beaulieu-Jones discussed the importance of reproducibility, citing the example of <a href="http://brainarray.mbni.med.umich.edu/Brainarray/Database/CustomCDF/CDF_download.asp">Custom CDF</a>, where the version used will affect results significantly, yet the version number is rarely specified in papers! <a href="http://www.nature.com/nbt/journal/v35/n4/full/nbt.3780.html">Continuous analysis</a> is a solution for automated computational reproducibility.</p><h4>GATK4</h4><p><a href="https://software.broadinstitute.org/gatk/">GATK4</a>, introduced by Kate Voss, was an exciting moment for open source, as previous versions of GATK (Genome Analysis Tool Kit, release by the <a href="https://www.broadinstitute.org/">Broad Institute</a>) had been released closed source. GATK4 is not only open source, but also runs up to 5 times faster than its predecessor, GATK3! There were some interesting pronunciation discussions, too…</p><h3>Peter Cock on Twitter</h3><p>At #BOSC2017 learnt @gatk_dev pronounce GATK by letter, but WDL as Widdle https://t.co/UlAFy0UdGe Did the dog just widdle on the floor? 🤣🐕💦</p><p>More on the lightning talks, open data panel, and keynote in <a href="https://medium.com/@yoyehudi/bosc-2017-day-2-part-2-bosc2017-ismbeccb-af4bf4a63a84">part 2</a>!</p><p><strong><em>Disclaimer: </em></strong><em>Any views expressed are my own, not necessarily those of PLOS.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d4d8fda000c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/plos-comp-biol-field-reports-2016/bosc-2017-day-2-part-1-bosc2017-ismbeccb-9d4d8fda000c">BOSC 2017, Day 2, part 1 #BOSC2017 #ISMBECCB</a> was originally published in <a href="https://medium.com/plos-comp-biol-field-reports-2016">PLOS Comp Biol Field Reports Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bosc 2017, Day 1]]></title>
            <link>https://medium.com/plos-comp-biol-field-reports-2016/bosc-2017-day-1-fbe73f01de2e?source=rss-3d25a2d2bfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbe73f01de2e</guid>
            <category><![CDATA[bosc]]></category>
            <category><![CDATA[bioinformatics]]></category>
            <category><![CDATA[ismb]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[yoyehudi]]></dc:creator>
            <pubDate>Sun, 23 Jul 2017 00:33:00 GMT</pubDate>
            <atom:updated>2017-07-24T10:09:23.202Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>BOSC 2017, Day 1 #BOSC2017 #ISMBECCB</h3><h3>Open Source, Common Workflow Language, Containers, &amp; War of the Package Managers</h3><p><em>Note: I’ve made an attempt to link to relevant sites for further info, but this article </em><strong><em>does</em></strong><em> assume familiarity with technical terms associated with bioinformatics software engineering.</em></p><p><a href="https://www.open-bio.org/wiki/BOSC_2017_Schedule">BOSC</a> — the Bioinformatics Open Source Conference — kicked off this morning, as one of the COSIs (Communities of special interest) associated with <a href="https://www.iscb.org/ismbeccb2017">ISMB/ECCB</a>. Overall, popular themes included open source (unsurprisingly!), reproducibility, containerisation, package management, and a love/hate relationship with <a href="https://www.docker.com/">Docker</a>.</p><h3>Morning Sessions</h3><h4>Common Workflow Language</h4><p>After the intro sessions, we entered straight into a set of talks on <a href="https://github.com/common-workflow-language/common-workflow-language">Common Workflow Language (CWL)</a> — a specification that has recently been growing steadily more popular. Tools from the <a href="https://github.com/rabix">Rabix suite</a> included visualisation libraries like <a href="https://github.com/rabix/cwl-svg">CWL-SVG</a> and <a href="https://www.typescriptlang.org/">TypeScript</a> development libraries such as the <a href="https://github.com/rabix/cwl-ts">CWL-TS</a>.</p><h4><strong>Global Alliance for Genomics and Health</strong></h4><p>While “GA4GH” might sound eerily like a <a href="http://memory-alpha.wikia.com/wiki/Gagh">Klingon delicacy</a>, the <a href="http://genomicsandhealth.org/">Global Alliance For Genomics and Health</a> produced quite a few interesting tool talks: the <a href="https://github.com/ga4gh/tool-registry-schemas">Tool Registry Service</a> paves the way for sharing containerised workflow tools, the <a href="https://github.com/ga4gh/dockstore">DockStore</a> provides infrastructure for them, the Task Execution Schema helps manage bulk tasks, akin to docker run, and GA4GH/DREAM aims to try packaging and re-running containers of all types on all platforms, hoping to build a truly bullet-proof reproducible stack. If you’d like to help with this, join the <a href="https://www.synapse.org/#!Synapse:syn8507133/wiki/415976">GA4GH/DREAM challenge</a> yourself!</p><h4>Morning Lightning Talks</h4><p>The morning lightning talks covered Kevin Sayers’ talk on <a href="https://github.com/nextflow-io">NextFlow/CWL integrations</a> — NextFlow is a bioinformatics workflow language designed to be human-readable and concise, while CWL is more machine-oriented. Stian Soiland-Reyes reminded us that <a href="https://en.wikipedia.org/wiki/Metadata">metadata</a> is extremely difficult to generate, because it’s boring, and suggested that providing visualisations such as <a href="https://view.commonwl.org/">Common Workflow Language Viewer</a> might be an appropriate incentive. Rephrasing in my own words here:</p><h3>yoyehudi🏳️‍🌈 on Twitter</h3><p>ismbeccb #BOSC2017 Incentivising people to include metadata is *always* hard. It&#39;s boring until you need to consume it ;)</p><p>Single-cell epigenomic reproducible workflows are also apparently an area that doesn’t have a lot of work in it, but Kieran O’Neill introduced <a href="https://github.com/Epigenomics-Screw/Screw">Epigenomics-SCREW</a> as a possible solution.</p><p>Next up came a talk on <a href="https://github.com/biothings/biothings_explorer">BioThings Explorer</a>, which integrates genomic data on the fly using APIs and <a href="https://json-ld.org/">json-ld</a>. Integrating disparate data via its identifiers, which may be labelled differently between datasources, is a tricky problem, so this short talk seemed very impressive.</p><p>Anil Thanki introduced discovery of homology and gene families using <a href="https://galaxyproject.org/">Galaxy</a> tools such as <a href="https://toolshed.g2.bx.psu.edu/repository?repository_id=fb9f6eb252c95b91">GeneSeqToFamily</a> and <a href="http://aequatus.earlham.ac.uk/">Aequatus</a>. The last talk of the morning was on <a href="https://github.com/alesssia/YAMP">YAMP</a>, by Alessia Visconti. “Yet another Metagenomic pipeline” addresses usability &amp; difficult setup issues in other tools, using NextFlow and Docker to get there.</p><h3>Lunch and BoFs</h3><p>Three lunchtime BoF discussions, standing for “Birds of a feather”, had been arranged for BOSC. I attended the “Future of BioJS” BoF. <a href="https://biojs.net/">BioJS</a> is a <a href="http://biojs.io/">great suite of Javascript-based tools</a> designed to visualise, parse, and process biological data, but over the last year or so, several maintainers had moved on, meaning the project needed a new set of volunteers to help provide infrastructure (domains names, server space, general admin), as well as developers, designers, and community / marketing managers. We managed to secure a general plan going ahead, but if anyone would like to volunteer an hour or three a week in any of the above roles, join the <a href="https://groups.google.com/forum/#!forum/biojavascript">Google Group</a> and ask to get involved — your help would be incredibly welcome!</p><h3>Afternoon Sessions</h3><h4><strong>Developer tools and libraries for open science and reproducibility</strong></h4><p>After the break, Phil Ewels introduced us to <a href="http://multiqc.info/">MultiQC</a>, a tool designed to generate static HTML reports from common biological data formats, born from the frustration that command lines shouldn’t be the only way to analyse data. MultiQC is a python command line tool that doesn’t run pipelines, instead analysing the output from pipelines that have already been run. It’s designed to work offline if no internet is available, and uses <a href="https://www.highcharts.com/">highcharts</a> for interactive data visualisation, or can be configured to generate <a href="https://matplotlib.org/">matplotlib</a> static images for scenarios where the data are so big they’d likely cause an interactive browser diagram to grind to a halt. Future plans include expansion to MegaQC, analysing across multiple data sets in a broader way.</p><h4>More lightning talks</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q63S0s52xvoqjw39WBREfQ.png" /><figcaption>Screenshot of the NGL codepen gallery</figcaption></figure><p>Alexander S Rose introduced us to <a href="https://github.com/arose/ngl">NGL</a>, a beautiful web-based molecular visualiser. The <a href="http://nglviewer.org/ngl/gallery/index.html">gallery</a> (pictured above) was stored as a set of C<a href="http://codepen.io/">odePen</a> instances. CodePen is an online javascript source code editor, which allows you to interact with the visualisation or tweak the code and see results in real time — a really nice way to present such gorgeous content!</p><p>Aditya Bharadwaj talked about a network visualiser called <a href="https://github.com/Murali-group/GraphSpace">GraphSpace</a>, Timothy Booth discussed detecting well-hopping duplicate reads, and Monther Alhamdoosh discussed <a href="http://www.biorxiv.org/content/early/2016/03/11/042580">ways to detect relevant genes</a> when you have really big datasets to explore, using the <a href="https://bioconductor.org/packages/release/bioc/html/EGSEA.html">EGSEA R package</a>.</p><p>Brad Chapman eloquently introduced <a href="https://github.com/chapmanb/bcbio-nextgen">bcbio</a>, designed to take analyses to the data files, rather than copying data around.</p><h3>James Taylor 🤖🌹🚀 on Twitter</h3><p>BOSC2017 Now @chapmanb presenting &quot;a bunch of python that integrates a bunch of tools&quot;, aka bcbio.</p><p>Before coffee break, Kees van Bochove described <a href="http://thehyve.nl/">The Hyve</a>’s worldwide open source work. The Hyve is also a BOSC sponsor.</p><h4>Data Science and Visualisation: The package manager wars</h4><p>Following a nice half-hour re-caffeination break, we entered the data science and visualisation section of the afternoon. Here lay many differences of opinion with regards to the best way to create reproducible software, the best package managers, and whether or not Docker is the solution to reproducibility (<a href="https://twitter.com/yoyehudi/status/888747030104944640">it’s not</a>), or indeed even necessary.</p><p>Björn Grüning introduced us to the package manager <a href="https://conda.io/">Conda</a>, and its biologically-oriented sibling, <a href="https://bioconda.github.io/">BioConda</a>. Conda describes itself as “Package, dependency and environment management for any language: Python, R, Ruby, Lua, Scala, Java, Javascript, C/ C++, FORTRAN”. Bioconda has only been around for about a year, but has over 2400 packages available and an active contributor community. Bioconda packages automatically generate Docker instances when they’re updated, saving effort maintaining separate dockerfiles. <a href="https://biocontainers.pro/registry/#/">Browse the registry</a> to get an idea of the packages it offers.</p><p><a href="https://www.gnu.org/software/guix/">Guix</a>, which I learned was pronounced “geeks”, was introduced by Ricardo Wurmus as a competing package manager solution to Bioconda, that doesn’t require Docker (but can use it if you really wish).</p><p>Kei Ono discussed <a href="http://www.cytoscape.org/">Cytoscape</a>, which grew from an early single Java visualisation package to become an entire ecosystem of related tools, including <a href="http://www.ndexbio.org/#/">NDex</a>, which he described as a “GitHub for biological networks”.</p><p>Olga Vrousgou introduced the <a href="http://www.ebi.ac.uk/spot/ontology/">SPOT ontology toolkit</a>, providing all your biological ontology lookup and data mapping needs. When Olga asked who knew about and used ontologies, hands went up across the room — it was definitely a popular subject!</p><p>Last talk before the keynote was a <a href="http://biopython.org/">BioPython</a> update. As shown above, they have a <a href="http://biopython.org/wiki/Biopython">great new logo</a>, created to loosely mimic the <a href="https://www.python.org/psf/">Python software foundation</a> colours with the foundation’s permission. Project updates include the plan to move from their old custom licence to the <a href="https://tldrlegal.com/license/bsd-3-clause-license-(revised)">3-clause BSD licence</a> — a long-winded task as all past contributors must be contacted to confirm their acceptance — as well as the fact that they’ll eventually be discontinuing support for Python 2.7 by 2020.</p><h3>Open Source Yourself: the keynote we were all waiting for</h3><p>Madeleine Ball’s talk was inspiring. Her project, <a href="https://www.openhumans.org/">Open Humans</a>, aims to break down barriers to gaining useful research data by open-sourcing genomes and personal health data. She discussed the concerns around sharing these types of data — whether it’s discovering you have a dangerous disease, perhaps one of your ancestors wasn’t actually your grandma, or something else — there are lot of reasons people might prefer to keep this data a secret.</p><p>Nonetheless, a surprising number of people <em>do</em> share anyway. Open Humans makes sure that people who share their personal health data know what they’re getting into when they share it, making people complete a quiz that proves they understand the potential risks.</p><p>She also shared the impressive story of Dana Lewis, who hacked her own artificial pancreas system in order to create a more effective glucose monitor alarm — one she couldn’t accidentally sleep through when the built-in one was too quiet! She went on to build a community around this as well: <a href="https://openaps.org/">OpenAPS</a>.</p><p>If OpenHumans sounds exciting to you, consider applying for their small grant project for <a href="https://www.openhumans.org/research/">ideas up to $5000</a>, or apply for their software developer vacancy.</p><p>That’s it for tonight folks! More after tomorrow’s talks.</p><p>Thirsty for more? Check out <a href="https://medium.com/@yoyehudi/bosc-2017-day-2-part-1-bosc2017-ismbeccb-9d4d8fda000c">BOSC Day 2</a></p><p><strong><em>Disclaimer: </em></strong><em>Any views expressed are my own, not necessarily those of PLOS.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbe73f01de2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/plos-comp-biol-field-reports-2016/bosc-2017-day-1-fbe73f01de2e">Bosc 2017, Day 1</a> was originally published in <a href="https://medium.com/plos-comp-biol-field-reports-2016">PLOS Comp Biol Field Reports Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BOSC / ISMB / ECCB 2017 plans]]></title>
            <link>https://medium.com/@yoyehudi/bosc-ismb-2017-plans-4f836de83b46?source=rss-3d25a2d2bfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f836de83b46</guid>
            <category><![CDATA[ismb]]></category>
            <category><![CDATA[bioinformatics]]></category>
            <category><![CDATA[eccb]]></category>
            <category><![CDATA[bosc-2017]]></category>
            <dc:creator><![CDATA[yoyehudi]]></dc:creator>
            <pubDate>Thu, 20 Jul 2017 11:24:07 GMT</pubDate>
            <atom:updated>2017-07-20T20:31:58.537Z</atom:updated>
            <content:encoded><![CDATA[<p>BOSC / ISMB / ECCB 2017 plans</p><p><a href="https://www.iscb.org/ismbeccb2017-registration">ISMB</a>/ECCB this year is being held in Prague; As an InterMiner I’ll be attending the COSI (Community of Special Interest) known as <a href="https://www.open-bio.org/wiki/BOSC_2017">BOSC</a> ( Bioinformatics Open Source Conference), run by OBF (Open Bioinformatics Foundation). Phew, that’s a lot of acronyms for a first sentence!</p><p>I’m really looking forward to the conference and have (probably) over-filed my time. Here are the current plans:</p><p>Friday 21 July: Arriving in the evening and settling in, feeling slightly jealous of anyone who came early and attended <a href="https://www.open-bio.org/wiki/Codefest_2017">Codefest</a> over Thursday / Friday.</p><h3>Saturday 22 July:</h3><p>Generally, I’ll be live tweeting from <a href="https://www.open-bio.org/wiki/BOSC_2017_Schedule">BOSC sessions</a> — probably both as @yoyehudi and @intermineorg - but there are a few other highlights:</p><p><strong>9:30–10:00</strong>: At the <a href="https://twitter.com/ELIXIREurope/status/887609626946043904">Elixir booth</a>. Pop by to learn more about <a href="http://intermine.org/">InterMine</a> or <a href="http://bluegenes.apps.intermine.org/">BlueGenes</a>!</p><p><strong>12:30–13:40</strong>: The Future of BioJS <a href="https://docs.google.com/document/d/1pCkjxooRxHhh3mcqxy7h083mUxt2Ldh1N0kJRwNdjx8/edit">BoF</a> “Bird of a feather” lunchtime meetup. Yep, another acronym! <a href="https://biojs.net/">BioJS</a> is a great project but recently it’s been a little bit neglected as its maintainers have moved on; we need to make some serious decisions about how to continue the project.</p><p><strong>18:00–19:00</strong>: Elixir booth again.</p><p>I’m *not* attending the BOSC dinner the first evening — largely because the menu didn’t have anything I could eat comfortably ( I prefer not to eat animal products and never eat meat) — but also because I’ll hopefully be posting blogs for <a href="https://medium.com/u/347c4e059ba8">PLOS Comp Biol</a>. This is massively exciting and something I’m really anticipating!</p><h3>Sunday 23 July:</h3><p><strong>9:30–10:00</strong>: Elixir booth. Come say hi and <a href="https://twitter.com/intermineorg/status/887674138365755392">get some awesome swag</a>!</p><p><strong>18:00–19:00</strong>: Poster time! I’ll be presenting a poster about BlueGenes, InterMine’s new UI. Preview the poster on <a href="https://figshare.com/articles/yoyehudi_micklemlab_intermine_pdf/5220763">figshare</a>, or admire BlueGenes directly: <a href="http://bluegenes.apps.intermine.org/">http://bluegenes.apps.intermine.org/</a></p><p>Finally, wrapping up with dinner at this lovely-looking restaurant: <a href="http://podoli.restauracepodolka.cz/menu/">http://podoli.restauracepodolka.cz/menu/</a></p><p>Monday I’ll be heading home; looking forward to seeing you all there!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f836de83b46" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>