Software and research: the Institute's Blog

Commercialising your software

Latest version published on 6 October, 2016.

Aleksandra Pawlik, a PhD student from the Open University, has been looking into commercialisation of scientific software. Getting people to pay for your software is one of the many routes to software sustainability, so we asked Aleksandra to give us an overview.

If you’re happy to share your cutting-edge software with other researchers, why not make some money by commercialising it? If academics are dying to get a copy of your code, then your software must be a desirable product. Industry is an equally important customer for software, and if nothing else it’s fun to charge…

Ask Steve! - How to develop code to avoid dependency problems

Latest version published on 30 September, 2016.

This post is inspired by a forum question from one of the SeIUCCR Community Champions, regarding software versioning issues on NGS clusters…

Developing code that depends on other code is  common – we do it all the time, even with the simplest program. Software reuse is good practice, but a problem can occur when you take your software from its well-known and tested environment, such as the one within your research group, to a new environment. You can find that the dependent software (the software you reused…

Scientists solve one of Africa’s oldest animal plagues

Latest version published on 6 October, 2016.

An interesting press release originating from our Manchester partners.

NAIROBI, KENYA —An international research team using a new combination of approaches has found two genes that may prove of vital importance to the lives and livelihoods of millions of farmers in a tsetse fly-plagued swathe of Africa the size of the United States. The team’s results were published today in the Proceedings of the National Academy of Sciences (PNAS).

Publish or be damned? An alternative impact manifesto for research software

Latest version published on 6 October, 2016.

In the research world, we're often told that the the only way for our work to have a measurable impact is through the citation of publications based on our work. The mechanisms for this are in place, the stakeholders understand the framework, and everyone is happy... or so we're led to believe.

However, the status quo neglects the many research outputs, including software, that may be generated by a research activity and certainly doesn't encourage their sharing and reuse, let alone give proper credit for their production.

The Ancient Greeks knew a thing or two about software problems

Latest version published on 6 October, 2016.

An Ancient Greek harp, which had been lost to the world, turns out to a fantastic argument for software sustainability.

At a conference last week, I talked to Domenico Vicinanza about the Epigonion: a kind of harp that was popular in Greece around the first century. None of the instruments have survived to the present day, so its existence was only known from historical records (such as the image shown on this page). It’s not just the instrument that has been lost, so have the skills and know-how needed to create one. This led Domenico’s team to set about a digital resurrection…

Coder, programmer or software developer - spot the difference!

Latest version published on 6 October, 2016.

Ask a hundred people what the cloud is and you’ll get a hundred different replies.

Ask a hundred different people what a computer programmer does and what, if any, the difference is between a programmer and a software developer, and you’ll also get a hundred different replies.

Ask me what the difference is, and this is what I’d reply…

Ask Steve! - How to Specify and Implement Data Movement?

Latest version published on 30 September, 2016.

You may recall back in February I talked about the importance of data formats when choosing a programming language for sustainable development.  Since then, I’ve received the following question…

“We’re currently putting together a machine for data intensive research. The machine will have a data-staging node, and 120 other nodes (configured using ROCKS)…

What do we want? Fewer abbreviations! When do we want them? ASAP!

Latest version published on 6 October, 2016.

The EGI is an abbreviation-heavy community.

There's the EGI - European Grid Infrastructure - which provides researchers with access to computing resources. There's also the EMI - the European Middleware Initiative (see my post from yesterday). It's completely different to the EGI, and is working to unify the different middlewares used in Europe (middleware is the software that ties together different computer resources.) Oh, and let’s not forget IGE (not EGI or EMI). It’s the Initiative for Globus in Europe, which coordinates European work on Globus (another middleware…

Three tips on software sustainability from the EGI User Forum

Latest version published on 6 October, 2016.

This week, I'm at the EGI (European Grid Infrastructure) User Forum in Vilnius (if you want to know more about the EGI, see my earlier post).

Before the first plenary was over, the term sustainability had featured at least a dozen times. This is heartening news for the Software Sustainability Institute! I was particularly interested in Alberto Di Meglio’s plenary talk about ‘open-source middleware and the road to sustainability’ (middleware is the software that ties together different computer resources). Alberto is the leader of the European Middleware…

Grid computing explained at the European Grid Infrastructure User Forum

Latest version published on 6 October, 2016.

The European Grid Infrastructure (EGI) provides European researchers with access to computing resources. And not just any computing resources – we’re talking big resources, the kind needed by scientists working on the Large Hadron Collider. There’s some interesting overlap between the EGI's work and the Software Sustainability Institute, especially when it comes to supporting research, so this week I’m at the EGI User Forum to find out more.

If you’re interested in the grid, the EGI has some very good resources to describe their work. They’ve created a guide to the grid, which…