High Performance Computing User Group Meeting [Slides]
We are updating the appropriate use policy for INL HPC resources to align with requirements regarding proprietary and non-proprietary use of government equipment.
SEARCH · Engineering Papers
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
We are updating the appropriate use policy for INL HPC resources to align with requirements regarding proprietary and non-proprietary use of government equipment.
INL HPC team provided updates related to the INL HPC program and HPC systems for HPC User Group Quarterly Review - September 11, 2024
INL HPC team provided updates related to the INL HPC program and HPC systems for HPC User Group Quarterly Review - June 12, 2024
INL HPC team provided updates related to the INL HPC program and HPC systems for HPC User Group Quarterly Review - June 12, 2024
INL HPC team provided updates related to the INL HPC program and HPC systems for HPC User Group Quarterly Review - March 5, 2025
INL HPC team provided updates related to the INL HPC program and HPC systems for HPC User Group Quarterly Review - September 10, 2025
INL HPC team provided updates related to the INL HPC program and HPC systems for HPC User Group Quarterly Review - June 11, 2025
Many scientific applications that support the mission of the US Department of Energy (US-DoE) require modeling complex engineering and/or physical systems. Here, examples of such complex systems arise from: (a) materials science to develop new compounds with exceptional mechanical and thermodynamical properties (e.g., resistance to mechanical stresses and high temperatures), (b) structural and nuclear engineering to model the temporal evolution of the structural damage of concrete shields exposed to continuous neutron and gamma radiations emitted by the nuclear reactor core, (c) urban sciences (e.g., transportation and smart buildings), and (d) power grid systems.
Cybersecurity is one of the largest concerns in modern computing, impacting and dictating how governments, private corporations, and individuals interact with and live in an increasingly digital world. The NSA has recently released a memo [ 1] on “Software Memory Safety” where they highlight that both Microsoft and Google have stated around 70% of software vulnerabilities were due to memory safety issues. Although languages such as C and C++ provide freedom and flexibility with memory management, guaran- teeing safety falls mostly on the developer. The NSA recommends using “memory safe” languages whenever possible. In this paper we introduce Lamellar, an asynchronous tasking and PGAS HPC runtime written in Rust, one such "memory safe" language. We describe the entire Lamellar stack, from network interfaces to high- level abstractions such as distributed LamellarArrays and Active Messages. We conclude by showing comparable performance to legacy PGAS runtimes (e.g. OpenSHMEM) on a subset of the BALE kernel suite while maintaining strong memory safety principles.
Explore the source record for details and available documents.
Results from work on feedback control of a queuing system for HPC jobs with shared storage resources.
Broadening participation initiatives are important for engaging underrepresented groups in science, technology, engineering, and math (STEM). Such initiatives help foster supportive and inclusive work environments that promote creativity and productivity. While there are initiatives that aim to engage students and faculty, opportunities remain to improve faculty support. Hackathons have proved to be a useful approach for student engagement. There are, however, limited insights into whether and how such events would also work for faculty aiming to develop curricula. This paper discusses the design of a faculty-focused hackathon event, FacultyHack, for curriculum development. We outline the logistics and structure for two past FacultyHack events, detail changes between events, and describe potential improvements and lessons learned.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.