Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
A trusted software framework to support and enhance scientific discovery #16
Use Case: A trusted software framework to support and enhance scientific discovery
*Contribtuors: Lesley Wyborn, Ryan Fraser, Ben Evans, Lutz Gross, Jens Klump
Goals and Summary
A trusted software framework is proposed to enable reliable software to be discovered, accessed and then deployed on multiple hardware environments. More specifically, this framework will enable those who generate the software, and those who fund the development of software, to gain credit for the effort, IP, time and dollars spent, and facilitate quantification of the impact of individual codes. For scientific users, the framework delivers reviewed and benchmarked scientific software with mechanisms to reproduce results.
The trusted framework will have five separate, but connected components: Register, Review, Reference, Run, and Repeat.
Why it is important and to whom?
Recent investments in HPC, cloud and Petascale data stores, have dramatically increased the scale and resolution that earth science challenges can now be tackled. These new infrastructures are highly parallelised and to fully utilise them and access the large volumes of earth science data now available, a new approach to software stack engineering needs to be developed. The size, complexity and cost of the new infrastructures mean any software deployed has to be reliable, trusted and reusable.
It is important to scientists so that they can be rapidly guided into finding and then choosing the most effective code for the scientific problem they are trying to achieve. It is important to the funding agencies so that they can measure the impact of the codes that they are funding and judge whether they are worth maintaining. It is important to the programmers as it provides mechanisms for them to benchmark their codes. And for those running the major computational centers it would help them to discern which codes to trust.
Why hasn't it been solved yet?
Individual components have been built, but no one has put it together in total.
Additional Information and Links