Photo by Markus Spiske on Unsplash
By Dr Marion Weinzierl, Research Software Engineer at Durham Univ
A one-day meeting will be help at the University of Leeds on 30 January, from 10.30am – 4pm, to look at similarities, challenges and opportunities for research software engineering groups across the N8 Research Partnership.
The complexity and difficulty of installing scientific software can often hamper its uptake and use within research communities. Douglas Lowe, a Research Software Engineer in Research IT, has been working with Dr Eric Prestat from the School of Natural Sciences to solve this problem for Prismatic, a cross-platform research software toolkit.
By Diego Alonso Alvarez, Senior Research Software Engineer, Imperial College London
Imperial College London is recruiting a developer to join its Research Computing Service (RCS) as a Research Software Engineer (RSE).
Vanessa Villamia Sochat, an engineer for the Stanford Research Computing Center, has begun creating a glossary of terms just for research software engineering.
“The near-ubiquity of software [in research] means that it is not possible to disentangle the quality of the software from the quality of the research.
By Mark Woodbridge, Research Software Engineering Team Lead, Imperial College London
We previously described three RSE-related use cases for Microsoft’s Azure platform, ranging in deployment granularity from VMs to individual JavaScript functions. In this post we’ll explain further how we use those and other Azure services to complement our on-premise infrastructure – helping us to deliver our RSE projects faster.
When researchers Drs Gary Motteram, Susan Dawson and Amanda Banks Gatenby from the School of Environment, Education and Development wanted to run analysis on WhatsApp messages, they came to Research IT for help.
By Neil Chue Hong, founding Director and Principal Investigator of the Software Sustainability Institute
Why do open source research software projects appear to have a low rate of success? Is it because we lack appropriate models for sustaining research software development or is it because the community isn’t seeing the results?