<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cluster Computing on Rachid Youven Zeghlache</title><link>https://youvenz.github.io/tags/cluster-computing/</link><description>Recent content in Cluster Computing on Rachid Youven Zeghlache</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 05 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://youvenz.github.io/tags/cluster-computing/index.xml" rel="self" type="application/rss+xml"/><item><title>Apptainer &amp; Conda: Reproducible HPC Python Environments</title><link>https://youvenz.github.io/blog/2026-03-05-apptainer-conda-reproducible-hpc-python-environments/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://youvenz.github.io/blog/2026-03-05-apptainer-conda-reproducible-hpc-python-environments/</guid><description>&lt;h1 id="build-reproducible-python-environments-with-apptainer--conda--for-hpc-researchers"&gt;Build Reproducible Python Environments with Apptainer &amp;amp; Conda — For HPC Researchers&lt;/h1&gt;
&lt;p&gt;Your Python script runs perfectly on your laptop. You transfer it to the cluster. Runtime fails. Missing dependencies. Version conflicts. Different Python builds. You spend hours debugging environment mismatches instead of running science.&lt;/p&gt;
&lt;p&gt;This is the researcher&amp;rsquo;s tax: &lt;strong&gt;environment reproduction across machines is broken by default.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id="what-this-solves"&gt;What This Solves&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Apptainer&lt;/strong&gt; (formerly Singularity) is a containerization tool built for HPC clusters. Unlike Docker, it doesn&amp;rsquo;t require root privileges and integrates seamlessly with cluster job schedulers like SLURM and PBS. Combined with &lt;strong&gt;Conda&lt;/strong&gt;, it lets you package a complete, reproducible Python environment—dependencies, versions, and all—into a single &lt;code&gt;.sif&lt;/code&gt; file that runs identically on your laptop, your colleague&amp;rsquo;s machine, and any HPC node.&lt;/p&gt;</description></item><item><title>SLURM Job Scheduling: Submit &amp; Monitor HPC Jobs</title><link>https://youvenz.github.io/blog/2026-03-05-slurm-job-scheduling-submit-monitor-hpc-jobs/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://youvenz.github.io/blog/2026-03-05-slurm-job-scheduling-submit-monitor-hpc-jobs/</guid><description>&lt;h1 id="submit--monitor-hpc-jobs-using-slurm--without-losing-your-data-to-path-errors"&gt;Submit &amp;amp; Monitor HPC Jobs Using SLURM — Without Losing Your Data to Path Errors&lt;/h1&gt;
&lt;p&gt;You&amp;rsquo;ve just logged into your university&amp;rsquo;s HPC cluster for the first time. You write what you think is a perfect job script, submit it with &lt;code&gt;sbatch&lt;/code&gt;, and 10 minutes later you find a cryptic error in the log file: &amp;ldquo;file does not exist.&amp;rdquo; Your absolute path was wrong. Or you forgot to specify GPU resources and your job waited in the queue for 3 hours doing nothing.&lt;/p&gt;</description></item></channel></rss>