class: left, title-slide # Welcome to the HPC ReproHack
###
Please Sign in on the Hackpad:
bit.ly/hpc-reprohack-hackpad
--- class: inverse ## Welcome to the 1st ReproHack HPC ReproHack! <!-- Put the link to this slide here so people can follow --> <br> ### 👋 from the organising team #### _David Quigley & Anna Krystalli_ *** ### Event Page: [bit.ly/hpc-reprohack](https://bit.ly/hpc-reprohack) Contains all event information and links to materials ### <svg viewBox="0 0 512 512" style="height:1em;position:relative;display:inline-block;top:.1em;" xmlns="http://www.w3.org/2000/svg"> <path d="M459.37 151.716c.325 4.548.325 9.097.325 13.645 0 138.72-105.583 298.558-298.558 298.558-59.452 0-114.68-17.219-161.137-47.106 8.447.974 16.568 1.299 25.34 1.299 49.055 0 94.213-16.568 130.274-44.832-46.132-.975-84.792-31.188-98.112-72.772 6.498.974 12.995 1.624 19.818 1.624 9.421 0 18.843-1.3 27.614-3.573-48.081-9.747-84.143-51.98-84.143-102.985v-1.299c13.969 7.797 30.214 12.67 47.431 13.319-28.264-18.843-46.781-51.005-46.781-87.391 0-19.492 5.197-37.36 14.294-52.954 51.655 63.675 129.3 105.258 216.365 109.807-1.624-7.797-2.599-15.918-2.599-24.04 0-57.828 46.782-104.934 104.934-104.934 30.213 0 57.502 12.67 76.67 33.137 23.715-4.548 46.456-13.32 66.599-25.34-7.798 24.366-24.366 44.833-46.132 57.827 21.117-2.273 41.584-8.122 60.426-16.243-14.292 20.791-32.161 39.308-52.628 54.253z"></path></svg> @ReproHack #HPCReproHack ??? Welcome everyone on behalf of the organising team, myself and David! I hope you've signed into the hackpad which has a lot of information, as does our event page. Both links should be in the chat. If you want to tweet aout today you can tweet at the reprohack project and/or Let me start with some context into what brings us all here today. --- > # Reprohack: > #### Sandbox Environment for Practicing Research Reproducibility -- > #### One day events using participants' laptops -- > #### Traditional format **excludes the examination of the reproducibility of computationally intensive research!** -- <br> # Enter the 1st High Performance Computing ReproHack! ??? General concept. Authors submit papers with associated code & data and participants try and reproduce the work from submitted materials. Precludes computationally intensive research. A question we were getting at almost every event so we were keen to address it. So when David got in touch with us about a bid he was preparing and suggesting exactly that we jumped at the opportunity to collaborate. Which brings us to why we are here today! The 1st HPC reprohack! This is a pilot and we hope to come up with a blueprint for how to run such events. So what's different: - Access to HPC cluster! - Longer format with opportunity to work in your own time - Mentors --- class: center, middle # Thank you! ## EPSRC for funding <img src="assets/EPSRC_logo.png" width="30%" /> _Grant EP/W032201/1_ ## Sulis for Compute Power ### **David Quigley** for securing funding ### All mentors for papers & support ??? I want to take the opportunity upfront to thank the EPSRC for the funding, Sulis HPC framework for the compute power set aside especially for us --- class: inverse, center, middle # Agenda ??? OK I'll do a quick blast through the agenda, --- # HPC ReproHack Launch ### 21st March | Time | Event | |--- |--- | | 10:00 - 10:15 | **Anna Krystalli:** Welcome, Introduction to event. | | 10:15 - 10:40 | **Martin Callaghan:** HPC in the age of Data Science | | 10:40 - 11:30 | **Twin Karmakharm:** Reproducibility on HPC | | 11:30 - 11:45 | COFFEE | | 11:45 - 12:10 | **Heather Ratcliffe:** Introduction to Sulis | | 12:10 - 12:35 | **Mike Croucher:** Reproducible MATLAB on HPC | | 12:35 - 12:55 | **Mozhgan Kabiri Chimeh:** NVIDIA AI & HPC Containers | | 13:00 - 14:00 | LUNCH | | 14:00 - 14:20 | **Anna Krystalli:** Introduction to ReproHacking | | 14:20 - 17:00 | Initial ReproHack Session | --- # HPC ReproHack ### Drop in sessions | Date | Time | Event | |--- |--- |--- | | 22nd March | 14:00 - 16:00 | Drop In support session | | 24th March | 14:00 - 16:00 | Drop In support session | | 28th March | 14:00 - 16:00 | Drop In support session | | 30th March | 14:00 - 16:00 | Drop In support session | --- # HPC ReproHack ### Closing sessions | Date | Time | Event | |--- |--- |--- | | 31st March | 10:00 - 13:00 | Closing Event | ??? In te afternoon, remember to take a coffee break and also submit your reviews by the end of the day. At 4pm, we'll rejoin to hear from Stephen Eglen on the Code Check project. We'll close by sharing our final thoughts about the experience followed by some closing remarks. --- class: inverse # House Keeping: - ### No fire alarms expected - ### Water point - ### Toilets - ### Code of Conduct <https://reprohack.org/code-of-conduct> ??? So some quick housekeeping --- ## ReproHack hackpad ➡️ [hackmd.io](https://hackmd.io/s/features) notepad <img src="assets/hackmd.png" width="90%" /> ??? As I've mentioned, we're also using a hackpad, specifically a hackmd hackpad. So this pad understands markdown, which is the text shown on the left and it is rendered on the right. If you are not familiar with markdown, don't worry too much, just use it as a plain text editor or you can have a quick look at hack md documentation, there's a link at the top of the hackpad. --- class: inverse # Ice breaker: Introductions <!-- Use this section as an ice-breaker. Introduce yourself, then allow others to go around the room and introduce themselves too --> ??? Now we're going to do a quick round of intriductions, and I'll put you in smaller break out groups and there's three questions Id like you to answer. I'll go first: --- <!-- Add details about yourself the organiser here: --> ## Who am I? > ### Dr Anna Krystalli (@annakrystalli) > > - Research Software Engineer _University of Sheffield_ > > - 2019 Fellow _Software Sustainability Institute_ > > - Software Peer Review Editor _rOpenSci_ > > - Core Team Member _ReproHack_ --- ## Why am I here? > I believe there's lots to learn about Reproducibility from working with other people's materials and engaging with real published research code and data. ??? - I feel very strongly that working with these resources is a really powerful working experience. But also that if we don't engage with the materials, we (the authors who have put all this effort in included) won't really know if they are actually reproducible and therefore fit for purpose. --- ## Who is my favorite animated character? > Stitch! > > ![](https://media3.giphy.com/media/95MU6SEzeLnUc/giphy.gif?cid=790b76115d11033236595055776d483b&rid=giphy.gif) ??? I think he's cute and my friends think that's who I turn into after I've had a couple of strong ciders! --- <!-- Open it up to participants --> # Your turn ### in small groups (5 mins) > - ### Who are you? > - ### Why are you here? > - ### Who is your favorite animated character? ??? OK, so it's your turn now, I'm going to put you into break out groups where you'll have 5 minutes to answer these 3 questions amongst yourself. --- class: inverse ## Welcome back! *** # Talks --- class: talk, middle ![](assets/hex-logo-small.png) ## 📢 Martin Callaghan ### _Research Computing Consultant, University of Leeds_ <br> > # *"HPC in the age of Data Science"* --- class: talk, middle ![](assets/hex-logo-small.png) ## 📢 Twin Karmakharm ### _Research Software Engineer, University of Sheffield._ <br> > # *"Reproducibility on HPC"* --- class: center, middle, bottom background-image: url("assets/coffee-break-cast.jpeg") background-size: cover # COFFEE BREAK ## 11:30 - 11:45 --- class: talk, middle ![](assets/hex-logo-small.png) ## 📢 Heather Ratcliffe ### _Research Software Engineer, University of Warwick_ <br> > # *"Introduction to Sulis"* --- class: talk, middle ![](assets/hex-logo-small.png) ## 📢 Mike Croucher ### _Principal Customer Success Engineer, MathWorks_ <br> > # *"Reproducible MATLAB on HPC"* --- class: talk, middle ![](assets/hex-logo-small.png) ## 📢 Mozhgan Kabiri Chimeh ### _GPU Developer Advocate, NVIDIA_ <br> > # *"NVIDIA AI & HPC Containers"* --- class: center, middle background-image: url("assets/lunch-break.jpeg") background-size: cover # LUNCH ## 13:00 - 14:00 --- class: inverse ## Welcome back! *** # Tips for Reproducing & Reviewing --- ## ReproHack Objectives 1. **Reproduce a paper from associated code and data** 3. **Feedback experiences to Authors** 5. **Think more broadly about opportunities and challenges** <br> -- ### + **Explore Reproducibility of Computationally Intensive research** > #### All papers to be reproduced on the **Sulis High Performance Computing Platform!** --- .pull-left[ ## Code of Conduct Event governed by **ReproHack Code of Conduct** <https://reprohack.org/code-of-conduct> <img src="assets/1728_TURI_Book sprint_7 community_040619.jpg" width="3307" /> ] -- .pull-right[ ### Additional Considerations - #### Reproducibility is hard! - #### Submitting authors are incredibly brave! ### Thank you Authors! 🙌 - #### Without them there would be no ReproHack. - #### Show gratitude and appreciation for their efforts. 🙏 - #### Constructive criticism only please! ] --- class: inverse, center, middle # 🔍 Reproducing & Reviewing <img src="assets/Hackathon.jpg" width="70%" /> --- class: middle .pull-left[ ## Selecting Papers ### [reprohack.org/event/14](https://reprohack.org/event/14) - **Information submitted by authors:** - Languages / tools used (tags) - Why you should attempt the paper. - Register paper using template in hackpad. - Create account on Sulis ] .pull-right[ <img src="assets/paper-list-14.png" width="1217" /> ] --- class: inverse, center, middle # Review as an auditor 📑 -- #### **tl;dr: Don't be this guy!** <img src="https://www.reactiongifs.com/r/O_o.gif" width="60%" /> --- class:centers # 🔍 For FAIR materials <img src="assets/FAIRPrinciples.jpg" width="80%" /> --- .pull-left[ # Access - How **easy** was it to **gain** access to the materials? - Did you manage to download all the files you needed? ] -- .pull-right[ # Installation - How **easy / automated** was **installation**? - Did you have any problems? - How did you solve them? ] --- --- .pull-left[ # Data - Were **data clearly separated from code and other items**? - Were **large data files deposited in a trustworthy data repository** and referred to using a **persistent identifier**? - Were **data documented** ...somehow... ] -- .pull-right[ # Documentation Was there **adequate documentation** describing: - how to **install** necessary software including non-standard dependencies? - how to **use** materials to reproduce the paper? - how to **cite** the materials, ideally in a form that can be copy and pasted? ] --- .pull-left[ # Analysis - **Were you able to fully reproduce** the paper? ✅ - **How automated** was the process of reproducing the paper? - **How easy was it to link** analysis **code** to: - the **plots** it generates - **sections in the manuscript** in which it is described and results reported ] -- .pull-right[ <br> ### If the analysis was not fully reproducible 🚫 - Were there **missing dependencies?** - Was the **computational environment not adequately described** / captured? - Was there **bugs** in the code? - Did **code run but results (e.g. model outputs, tables, figures) differ** to those published? By **how much?** ] --- class: inverse, center, middle # Review as a user 🎮 -- .pull-left[ ### New User <img src="https://25.media.tumblr.com/30906cccedfe97a3d5450a23359ca298/tumblr_ml72i2eL6t1rsudnqo1_500.gif" width="80%" /> ] -- .pull-right[ ### Invested User <img src="https://media.giphy.com/media/9K2nFglCAQClO/source.gif" width="80%" /> ] --- ## Review as a user 🎮 <br> #### What did you find easy / intuitive? > Was the file structure and file naming informative / intuitive? > Was the analysis workflow easy to follow? > Was there missing / confusing documentation? #### What did you find confusing / difficult > Identify pressure points. Constructive suggestions? #### What did you enjoy? > Identify aspects that worked well. --- class: inverse, center, middle # Feed back # 💬 --- ## Feedback as a community member .pull-left[ #### Acknowledge author effort #### Give feedback in good faith #### Focus on community benefits and system level solutions <img src="assets/1728_TURI_Book sprint_11 community_040619.jpg" width="80%" /> ] .pull-right[ > #### _Help build convention on what a Research Compendium should be and how we should be able to use it_ <img src="assets/ResearchCompendium.jpg" width="80%" /> ] --- # Submit review 1. ### Sign up / Log in 2. ### New Review: [reprohack.org/review/new](https://www.reprohack.org/review/new) <img src="assets/new-review.png" width="70%" /> --- class: inverse, center, middle # Participant Guidelines ### [reprohack.org/participant_guidelines](https://www.reprohack.org/participant_guidelines) --- ### Participation guidelines #### During launch day - You have the rest of the afternoon to begin ReproHacking with help from organisers and mentors. - It is recommended you familiarise yourself with the feedback form early on. #### During Drop in support sessions - We have four scheduled drop in sessions (see agenda for details) - RSE and HPC support will be available at these times #### At any time - Schedule time with your team to work on your project. - Contact and schedule support meetings with your mentors. - Feel free to add to the collaborative notes on the hackpad. #### Closing event - Each group will be expected to give a short presentation (5-10 mins) summarising their experiences and lessons learnt. Feel free to create slides if you wish. - Make sure you have completed your feedback form as a team. --- class: center, middle background-image: url("assets/question.jpeg") background-size: cover # Questions? --- class: inverse # Let's go! 🏁 ## Now - 16:30 ### 🔎 Paper List review + Have a look at the [papers available for reproduction](https://reprohack.org/event/14) ### 👥 Team formation / project registration + Fine to work individually + Add your details to the [**hackpad: bit.ly/hpc-reprohack-hackpad**](https://bit.ly/hpc-reprohack-hackpad). + Register your team and paper on the [**hackpad: bit.ly/hpc-reprohack-hackpad**](https://bit.ly/hpc-reprohack-hackpad) ### Mentors will be assigned once papers selected --- class: inverse, middle # First day re-group 💭 > ### Summarise group experiences > - What approaches to reproducibility the papers taken. > - Anything in particular you like about the approaches so far? > - Anything you're having difficulty with? --- # Carry on ReproHacking! #### Join a Drop in Session if you need help. #### Coordinate with your mentors for additional support. #### Use ReproHack slack for communication: [![Slack](https://img.shields.io/badge/slack-join%20us-brightgreen)](https://reprohack-autoinvite.herokuapp.com/) `#warwick-hpc-reprohack` #### Complete a feedback form for the authors ### Regroup on the 31st March --- class: center, middle background-image: url("assets/question.jpeg") background-size: cover # Questions? --- class: middle # THANK YOU ALL! 🙏 ### See you on the 31st March 10:00 - 13:00 # 👋 --- # Acknowledgements Images throughout the slides watermarked with **Scriberia** were created by [Scriberia](https://www.scriberia.co.uk/) for The Turing Way community and is used under a CC-BY licence - _The Turing Way Community, & Scriberia. (2019, July 11). Illustrations from the Turing Way book dashes. Zenodo. http://doi.org/10.5281/zenodo.3332808_ - Coffee Break Photo by <a href="https://unsplash.com/@mindspacestudio?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Mindspace Studio</a> on <a href="https://unsplash.com/s/photos/coffee-break?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Unsplash</a> - Lunch Break Photo by <a href="https://unsplash.com/@ferhadd?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Farhad Ibrahimzade</a> on <a href="https://unsplash.com/s/photos/lunch-break?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Unsplash</a> - Question mark Photo by <a href="https://unsplash.com/@towfiqu999999?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Towfiqu barbhuiya</a> on <a href="https://unsplash.com/s/photos/questions?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Unsplash</a>