Research

F1000 Research has issued an open call for submissions for their Innovations in Research Assessment collection which aims to bring together articles on innovations in research assessment and evaluation across disciplines and around the world.

Studies carried out by the Software Sustainability Institute.

 

Shaping AHRC policy on software and data

Researchers: Dr. Rebecca Taylor (PI), Prof. Simon Hettrick (Co-I), Prof. David De Roure (Co-I), Johanna Walker. 

Funder: AHRC

Participant Information Sheet

 

Understanding the software used to analyse social sciences data

Researchers: Mr. Neil Chue Hong (PI), Dr. Mario Antonioletti, Ms. Selina Aragon, Johanna Walker. 

The UK government has promised to double funding on research and development to £18 billion, roughly 0.7% of GDP, by 2024-25. Where should it invest? And where should it invest to support software-reliant research? We want to hear your ideas! You can respond on Twitter: 

 

If we want research to benefit from reliable software, we need to create a home in academia for Research Software Engineers (RSEs). In the long term, this means the creation of an RSE career path, but that involves a rather heavyweight shift in the way that universities deal with staff. Fortunately, there’s also a short-term solution: create more “research software groups”. This week, leaders of these groups met to discuss how they can work together, and how they can support the formation of new research software groups across the UK.

No one knows how much software is used in research. Look around any lab and you’ll see software – both standard and bespoke – being used by all disciplines and seniorities of researchers. Software is clearly fundamental to research, but we can’t prove this without evidence. And this lack of evidence is the reason why we ran a survey of researchers at 15 Russell Group universities to find out about their software use and background.

No one knows how much software is used in research. Look around any lab and you’ll see software – both standard and bespoke – being used by all disciplines and seniorities of researchers. Software is clearly fundamental to research, but we can’t prove this without evidence. And this lack of evidence is the reason why we ran a survey of researchers at 15 Russell Group universities to find out about their software use and background.

Over the last few months, we’ve been working on improving our understanding of the size of the research software community. In previous posts, I’ve discussed our plans for this research. Although we've not yet finished our analysis, we thought that it would be interesting to release some early results. First of all, how much money do the Research Councils invest into research that relies on software? The answer: at least a third of the entire RCUK budget - or £840 million in 2013.

By Mike Jackson, Software Architect.

Working with researchers is something the Institute has been doing for many years now. So we thought it was about time to put together our top tips for software developers working with researchers, to help foster productive, and enjoyable, collaborations.

1. Remember they are not software developers

You may know the difference between centralised and distributed revision control, classes and objects, pass-by-value and pass-by-reference, upcasting and downcasting, coupling and cohesion, processes and threads, or a stack overflow…

One of the biggest problems facing researchers is the best way to share their research to as broad an audience as possible. In fact, it’s this important part of research impact, or how academic research makes a contribution to wider society, that is used as one of the yardsticks to judge the success of a research project.

The Software Sustainability Institute has been addressing this problem through its blog, which regularly features articles by researchers from across the disciplines, all of whom have used software to enhance and develop their work. The question, however…