<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>hpc on Gaia Lab · Blog</title><link>https://blog.defectiv.es/en/tags/hpc/</link><description>Recent content in hpc on Gaia Lab · Blog</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Wed, 23 Sep 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://blog.defectiv.es/en/tags/hpc/index.xml" rel="self" type="application/rss+xml"/><item><title>What really runs on our cluster, read from the scripts themselves</title><link>https://blog.defectiv.es/en/posts/que-corre-de-verdad-en-nuestro-cluster/</link><pubDate>Tue, 22 Sep 2026 10:00:00 +0200</pubDate><guid>https://blog.defectiv.es/en/posts/que-corre-de-verdad-en-nuestro-cluster/</guid><description>&lt;p&gt;A cluster&amp;rsquo;s job history is usually a wall of six-digit identifiers and cryptic names —&lt;code&gt;mcpfw_cc&lt;/code&gt;, &lt;code&gt;eval_dynamic_pid&lt;/code&gt;, &lt;code&gt;boltz2&lt;/code&gt;— that say everything to whoever launched them and nothing to anyone else. But if you keep the &lt;em&gt;scripts&lt;/em&gt;, the wall turns into a document: people write down &lt;strong&gt;why&lt;/strong&gt; they do things, especially when a batch costs money and a night of waiting.&lt;/p&gt;</description></item></channel></rss>