JHJames Hetherington

James Hetherington

*This is an algorithmically generated author record based on publicly available information.

Current Organizations / Institutes

The organizations/institutes from the scholar's latest article

Previous Organizations / Institutes

The organizations / institutes from the scholar's other articles in the past ten years


James Hetherington has a total of 146 co-authors. Here are the top co-authors by number of shared publications:


Latest Publications

  • Open Access

    Assertion Errors: Why AI-Generated Research Code Still Needs Epistemic Infrastructure

    by Joseph Shingleton, James Hethrington, Ana Basiri

    The validity of computational research depends not only on the functionality of research code, but on how that code is made trustworthy. We argue that research software engineering (RSE) practices constitute part of the epistemic infrastructure of computational science: the practices, norms, and social arrangements through which software-mediated claims become warranted. This has important consequences for AI-assisted coding in research. Generative AI can produce functional code, but such code does not become scientifically meaningful by virtue of execution alone. Its outputs acquire trustworthiness only when embedded within the practices of RSE. As generative AI increases the supply of plausible research code, the need to establish its scientific status becomes more pressing. RSE therefore becomes more important, not less, since its value lies not in the generation of functional code, but in creating the conditions under which that code can responsibly contribute to knowledge.

  • Open Access

    3D Line Radiative Transfer & Synthetic Observations with Magritte

    by Frederik De Ceuster, Thomas Ceulemans, Atulit Srivastava, Ward Homan, Jan Bolte, Jeremy Yates, Leen Decin, Peter Boyle, James Hetherington


  • Open Access

    CMakeCatchTemplate: A C++ template project

    by Thomas Dowrick, Mian Ahmad, Stephen Thompson, James Hetherington, Jonathan Cooper, Matt Clarkson

    CMakeCatchTemplate (https://github.com/MattClarkson/CMakeCatchTemplate) is a project to provide a starting structure for C++ projects configured with CMake, that can be customised to work in a variety of scenarios, allowing developers to deploy new algorithms to users in a shorter timeframe. Main features include a SuperBuild to build optional dependencies; unit tests using Catch; support for CUDA, OpenMP and MPI; examples of command line and GUI applications; Doxygen integration; Continuous Integration templates and support for building/deploying Python modules.

  • Open Access

    Design choices for productive, secure, data-intensive research at scale in the cloud

    by Diego Arenas, Jon Atkins, Claire Austin, David Beavan, Alvaro Cabrejas Egea, Steven Carlysle-Davies, Ian Carter, Rob Clarke, James Cunningham, Tom Doel, et al.

    We present a policy and process framework for secure environments for productive data science research projects at scale, by combining prevailing data security threat and risk profiles into five sensitivity tiers, and, at each tier, specifying recommended policies for data classification, data ingress, software ingress, data egress, user access, user device control, and analysis environments. By presenting design patterns for security choices for each tier, and using software defined infrastructure so that a different, independent, secure research environment can be instantiated for each project appropriate to its classification, we hope to maximise researcher productivity and minimise risk, allowing research organisations to operate with confidence.

  • Open Access

    Assessing Simulations of Imperial Dynamics and Conflict in the Ancient World

    by Jim Madge, Giovanni Colavizza, James Hetherington, Weisi Guo, Alan Wilson

    The development of models to capture large-scale dynamics in human history is one of the core contributions of cliodynamics. Most often, these models are assessed by their predictive capability on some macro-scale and aggregated measure and compared to manually curated historical data. In this report, we consider the model from Turchin et al. (2013), where the evaluation is done on the prediction of “imperial density”: the relative frequency with which a geographical area belonged to large-scale polities over a certain time window. We implement the model and release both code and data for reproducibility. We then assess its behavior against three historical datasets: the relative size of simulated polities versus historical ones; the spatial correlation of simulated imperial density with historical population density; and the spatial correlation of simulated conflict versus historical conflict. At the global level, we show good agreement with population density (R2<0.75), and some agreement with historical conflict in Europe (R2<0.42). The model instead fails to reproduce the historical shape of individual polities. Finally, we tweak the model to behave greedily by having polities preferentially attacking weaker neighbors. Results significantly degrade, suggesting that random attacks are a key trait of the original model. We conclude by proposing a way forward by matching the probabilistic imperial strength from simulations to inferred networked communities from real settlement data. Page numbers for this article were updated on 01/05/2021.

  • Open Access

    Critical care data processing tools

    by Sinan Shi, David Pérez-Suárez, Steve Harris, Niall MacCallum, David Brealey, Mervyn Singer, James Hetherington


  • Open Access

    FabSim: Facilitating computational research through automation on large-scale and distributed e-infrastructures

    by Derek Groen, Agastya P. Bhati, James Suter, James Hetherington, Stefan J. Zasada, Peter V. Coveney


  • Open Access

    Report on the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3)

    by Daniel S. Katz, Sou-Cheng T. Choi, Kyle E. Niemeyer, James Hetherington, Frank Löffler, Dan Gunter, Ray Idaszak, Steven R. Brandt, Mark A. Miller, Sandra Gesing, et al.

    This report records and discusses the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3). The report includes a description of the keynote presentation of the workshop, which served as an overview of sustainable scientific software. It also summarizes a set of lightning talks in which speakers highlighted to-the-point lessons and challenges pertaining to sustaining scientific software. The final and main contribution of the report is a summary of the discussions, future steps, and future organization for a set of self-organized working groups on topics including developing pathways to funding scientific software; constructing useful common metrics for crediting software stakeholders; identifying principles for sustainable software engineering design; reaching out to research software organizations around the world; and building communities for software sustainability. For each group, we include a point of contact and a landing page that can be used by those who want to join that group's future activities. The main challenge left by the workshop is to see if the groups will execute these activities that they have scheduled, and how the WSSSPE community can encourage this to happen.

  • Open Access

    Report on the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3)

    by Daniel S. Katz, Sou-Cheng T. Choi, Kyle E. Niemeyer, James Hetherington, Frank Löffler, Dan Gunter, Ray Idaszak, Steven R. Brandt, Mark A. Miller, Sandra Gessing, et al.

    This report records and discusses the Third Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE3). The report includes a description of the keynote presentation of the workshop, which served as an overview of sustainable scientific software. It also summarizes a set of lightning talks in which speakers highlighted to-the-point lessons and challenges pertaining to sustaining scientific software. The final and main contribution of the report is a summary of the discussions, future steps, and future organization for a set of self-organized working groups on topics including developing pathways to funding scientific software; constructing useful common metrics for crediting software stakeholders; identifying principles for sustainable software engineering design; reaching out to research software organizations around the world; and building communities for software sustainability. For each group, we include a point of contact and a landing page that can be used by those who want to join that group’s future activities. The main challenge left by the workshop is to see if the groups will execute these activities that they have scheduled, and how the WSSSPE community can encourage this to happen


  • Open Access

    Summary of the First Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE1)

    by Daniel S. Katz, Sou-Cheng T. Choi, Hilmar Lapp, Ketan Maheshwari, Frank Löffler, Matthew Turk, Marcus D. Hanwell, Nancy Wilkins-Diehr, James Hetherington, James Howison, et al.

    Challenges related to development, deployment, and maintenance of reusable software for science are becoming a growing concern. Many scientists' research increasingly depends on the quality and availability of software upon which their works are built. To highlight some of these issues and share experiences, the First Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE1) was held in November 2013 in conjunction with the SC13 Conference. The workshop featured keynote presentations and a large number (54) of solicited extended abstracts that were grouped into three themes and presented via panels. A set of collaborative notes of the presentations and discussion was taken during the workshop. Unique perspectives were captured about issues such as comprehensive documentation, development and deployment practices, software licenses and career paths for developers. Attribution systems that account for evidence of software contribution and impact were also discussed. These include mechanisms such as Digital Object Identifiers, publication of "software papers", and the use of online systems, for example source code repositories like GitHub. This paper summarizes the issues and shared experiences that were discussed, including cross-cutting issues and use cases. It joins a nascent literature seeking to understand what drives software work in science, and how it is impacted by the reward systems of science. These incentives can determine the extent to which developers are motivated to build software for the long-term, for the use of others, and whether to work collaboratively or separately. It also explores community building, leadership, and dynamics in relation to successful scientific software.