Casper and JupyterHub have been returned to service. All Casper nodes were updated to the OpenSUSE Version 15.4 for better compatibility with Derecho. Queued jobs were removed to prevent job conflicts running on the new operating system. The software stack has been entirely refreshed, and is consistent with the evaluation nodes provided over the past months for user checkout. Plan to recompile applications and you may need to reinstall some personal Conda environments, though this should be atypical.
JupyterHub is available on Casper and Cheyenne. Most existing language kernels should continue to work on Casper, though user-installed kernels featuring compiled code (e.g., pip source installs) may need to be recreated first. New curated kernels for Matlab, IDL, and Julia are provided, while some very old kernels have been removed to improve clarity of available options. Note that a few kernels are marked as intended for use on either Casper or Cheyenne only. Please do not load such kernels on an unsupported system - they will not work.
This is a big update on Casper - feel free to ask questions or report issues with JupyterHub kernels here, along with other usual channels.
Hi Brian,
I had some issues launching dask on the cluster this morning. There's an error after running "cluster = PBSCluster", saying "'ib0' is not a valid network interface. Valid network interfaces are: ['lo', 'mgt', 'ext', 'eno2']". I was wondering if it has something to do with the refresh. Do I need to update something?
Hi Hui,
Thank you for bringing this up! The ib0 interface which has been recommended for Dask is being deprecated for most workflows on Casper in favor of high-speed ethernet. Please use ext as the network inferface moving forward. We will make a point to share this in multiple places so everyone is aware.
Excellent. Thanks, Brian!
Hui, I'm having the same issue and wondering the same thing. Can we upvote this issue?
@Will Wieder does setting interface='ext'
in the PBSCluster()
command address your issue, or is there something else going on?
Yes, this fixed the issue. when I posted my question, I wasn't able to read Brian's response for some reason (I'm somewhat zulip challenged). Thanks for asking @Katie Dagon
Last updated: May 16 2025 at 17:14 UTC