Research data springSoftware Reuse, Repurposing and Reproducibility10/12/2015

Heading

Landing Page: Software/abc/001

Metadata describing the

Software Object

Source Code

Play It

Orcid link/Research Object

Research data springSoftware Reuse, Repurposing and Reproducibility10/12/2015

Research data springSoftware Reuse, Repurposing and Reproducibility10/12/2015

Research data springSoftware Reuse, Repurposing and Reproducibility10/12/2015

Video demo at any of

https://tinyurl.com/RRRVidhttps://youtu.be/wfLqcuwbk30

http://rrr.cs.st-andrews.ac.uk

01/05/2023

Software Reuse, Repurposing and Reproducibility 5

Team

»Project Team: › Ian Gent, John McDermott, Chi-Jui Wu, Simon

Dobson (St Andrews) ; › Catherine Jones, Brian Matthews, Steven

Lamerton, Paulina Lach (STFC) › Jonathan Tedds (Leicester)

01/05/2023

Software Reuse, Repurposing and Reproducibility 6

What we have done in Phase 2

» Technical Progress› Work on linking to GitHub to build

containers› Mantid used to compare Docker

and Vagrant› Leicester case study to examine

guidelines and recomputation hosting & provisioning» Outreach

› Discussions with Computational Scientists and Research Software Engineers

› Poster at iPres 2015 › Talk at Software Credit workshop & Knowledge Exchange

workshop› Guidelines input into Force11 review of the state of the art

01/05/2023

Software Reuse, Repurposing and Reproducibility 7

What we learnt talking to stakeholders

» The further from the creation of the code, the greater the interest in preserving it is.› Research software engineers:

– “Good software management practice is all that is needed”– We suspect those who need to reuse code may not agree …

› Computational scientists who write code: – Haven’t thought about it but acknowledgement/credit and reproducibility are good

in theory› Digital Preservation experts:

– Very interested as they know they will have to do it – Recognised as a key trend in 2016 at iPres

» The idea of being able to prove reproducibility of results from software analysis is gaining traction but this is still an area which is novel to many we spoke to.

» There are overlaps with Continuous Integration tools (eg Jenkins), or deployment processes (eg Puppet ).

01/05/2023

Software Reuse, Repurposing and Reproducibility 8

How this has amended our plans»Greater distinction between live development

and sustainability of code in our planning for Phase 3

»Recognition that more outreach needs to be done alongside further technical development

»Key time to influence developments in the wider community so need to prototype this work to understand the pros and cons

01/05/2023

Software Reuse, Repurposing and Reproducibility 9

Summary Objectives for Phase 3 »Code in active development: 

› Prototype the integration into Build Service infrastructure› Case study for research code under active development › Case study using generic hosting container on Microsoft

Azure »Preservation of code which has ceased active

development: › 3 case studies

– Cancer Biobank (use of OpenSpecimen); – NIHR Leicester-Loughborough Physical Activity BRU (CiviCRM); – 100k Genomes (CiviCRM / OpenClinica)

»Outreach & Dissemination

01/05/2023

Software Reuse, Repurposing and Reproducibility 10

Detailed Objectives for Phase 3 » Code in active development: 

› STFC will prototype the integration of persistent identifiers of software and the production of appropriate containers such as Docker and/or Vagrant virtual machines into the build process. This will be prototyped within the Software Engineering Support Centre’s evolving Build Service infrastructure, based on Jenkins.

› St Andrews will lead a case study of using the above for research code under active development by an individual researcher or small group

› Leicester will advance generic hosting container build (using Puppet) on MS Azure for Research Platform so that resources are available to any UK based academic.

» Preservation of code which has ceased active development: › Leicester will utilise these techniques for 3 bespoke, tailored applications of BRISSKit

software components including Cancer Biobank (use of OpenSpecimen); NIHR Leicester-Loughborough Physical Activity BRU (CiviCRM); 100k Genomes (CiviCRM / OpenClinica) and make code available via nationally available repositories.

» Outreach & Dissemination:› including continued activities within Force11 working group on software citation.