Saul Crumpton

I'm noticing this even with only a single job on a node: Slurm Web 2.2.2  Slurm Web 2.2.5  There are 3 changes that are the potential culprits: 

The Major code changes between https://github.com/edf-hpc/slurm-web/commit/c233323e514fb41e9d2490a69212378130c0712b and https://github.com/edf-hpc/slurm-web/commit/c1d1ad2f41efc365ad3bfea6fd380c15c3033d8d Is when the error was introduced. reverting only the 2d-draw.js file back to https://github.com/edf-hpc/slurm-web/blob/86ac1c6d1b3873de80320ec06bc2fed6bdb26e0c/dashboard/js/draw/2d-draw.js has it working mostly like normal, but there...

I think I've tracked an issue down in 2.2.5 to the getCoreABSCoordinates function. I noticed that certain times, I'm having multiple cores map to the same X,Y pairs. Looking at...

so; 2 major issues I've found: 1. in the `/util/jobs.js` buildAllocatedCPUs function, you will only end up getting one layout returned for a node, regardless of how many jobs (and...

I ended up re-writing the functions to match old functionality, partially to add support for a GPUs page. https://github.com/BSCrumpton/slurm-web/tree/GPUBranch some of the relevant code can be seen here

honestly, maybe just dashboard/js/draw/2d-draw.js . Note that I haven't tested this in a while, so I'm not 100% sure. No other readme- but I should add it to the docket...

 basically- I added another tab to the main menu (top right) called GPUs that displays similar to JobsMap, but showing GPUs instead of cores. Additionally, in the main Jobs...