User contributions for Seide

21:2921:29, 5 March 2026 diff hist +348 VS Code →Search tuning
21:2421:24, 5 March 2026 diff hist +369 Nexus →Access: Link to "Nexus/Submission Node Policy" current
21:1921:19, 5 March 2026 diff hist +4,010 N Nexus/Submission Node Policy Created page with "Submission nodes are intended for users to submit jobs to the Nexus cluster. User interactivity is critical here, and while some of these submission nodes have a decent amount of cores and memory, highly-intensive computational jobs should not be run on these nodes. We have minimal resource restrictions in place at the moment, but we may explore further CPU/memory restrictions in the future. For the time being, be a good neighbor! In general, we expect that users on the..." current
20:5620:56, 5 March 2026 diff hist +12 VS Code →Keep data separate from code where possible
19:5019:50, 5 March 2026 diff hist +1,005 VS Code →Best Practices: Add information about searching

16:1416:14, 21 November 2025 diff hist +2,006 Nexus →Partition QoS: Update for scavenger/scavenger-aarch64 relative QoS configuration

15:5915:59, 10 May 2024 diff hist +129 Nexus →Partitions
15:5615:56, 10 May 2024 diff hist +48 SLURM →Documentation
15:5415:54, 10 May 2024 diff hist +2,811 N SLURM/Preemption Created page with "If you are submitting to a partition which is eligible for preemption (e.g. scavenger), you are responsible for making sure that your job can be interrupted/restarted gracefully. Here we are documenting some Slurm behaviors that you can use to determine if your job has been cancelled or preempted. You should be able to take different code paths during startup/shutdown of your jobs based on this information. =Flowchart for job cancellation/preemption= ==Cancellation==..."