Announcements

We are hosting two webinars to help acquaint you with the allocation process.

Register for either of the upcoming webinars:

1st HPC allocation webinar: May 18, 1 p.m. – 2 p.m. MDT
2nd HPC allocation webinar: May 24, 11 a.m. – noon MDT

NOTE: You do not need to attend both HPC webinars—choose that one that works best for you.

The newest high-performance computing system, Kestrel, is about to take flight at NREL! Follow the journey of EERE’s latest supercomputing technology in the new Kestrel blog! The first components of the Kestrel supercomputer will arrive at NREL on March 20.

Check in often for updates from the team, videos, photos, and more in the Countdown to Kestrel blog!

Kestrel will be shipping soon and is on track for a Q4 availability!

HPC Operations strongly recommends against setting world writeable (chmod o+rwx or 777) permissions on either your /home or /scratch directories

HPC office hours are being held remotely via Teams on a bi-weekly basis alternating between Tuesday and Thursday at 11am. Please see the NREL HPC Training page: NREL HPC Training page.

Support and Help Contact information and sites available in this announcement.

Staff in the Computational Science Center host multiple tutorials and workshops on various computational science topics throughout the year, such as Visualization, Cloud, HPC, and others. 

In Microsoft Teams, a “Computational Sciences Tutorials” public team was just created to be the hub for all such tutorials and workshops.  Benefits to using the the team include the following:

Some people who use Windows 10/11 computers to ssh to Eagle from a Windows command prompt, powershell, or via Visual Studio Code's SSH extension have received a new error message about a "Corrupted MAC on input" or "message authentication code incorrect." Here's how to fix this issue.

Eagle logins are shared resources that are heavily utilized.  We have some controls in place to limit per user process use of memory and CPU that will ramp down your processes usage over time. We recommend any sustained heavy usage of memory and CPU take place on compute nodes, where these limits aren't in place. If you only need a node for an hour, nodes in the debug partition are available. We permit compiles and file operations on the logins, but discourage multi threaded operations or long, sustained operations against the file system. We cannot put the same limits on file system operations as memory and CPU, therefore if you slow the file system on the login node, you slow it for everyone on that login. Lastly, Fastx, the remote windowing package on the ED nodes, is a licensed product. When you are done using FastX, please log all the way out to ensure licenses are available for all users.