<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Scientific-Computing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/scientific-computing/</link>
    <description>Recent content in Scientific-Computing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 04 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/scientific-computing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Genomics Workflow Pipelines: Nextflow vs Snakemake vs Cromwell</title>
      <link>https://www.pistack.xyz/posts/2026-06-04-genomics-workflow-pipelines-nextflow-snakemake-cromwell-guide/</link>
      <pubDate>Thu, 04 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-04-genomics-workflow-pipelines-nextflow-snakemake-cromwell-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Modern genomics research generates terabytes of data per experiment. A single whole-genome sequencing run can produce hundreds of gigabytes of raw reads that must be aligned, called, filtered, annotated, and visualized — all before a researcher can draw biological conclusions. Managing these multi-step computational workflows at scale requires specialized pipeline orchestration tools purpose-built for scientific computing.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosted HPC Container Runtimes: Apptainer vs Charliecloud vs Podman-HPC Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-self-hosted-hpc-container-runtimes-apptainer-charliecloud-podman-hpc-guide/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-self-hosted-hpc-container-runtimes-apptainer-charliecloud-podman-hpc-guide/</guid>
      <description>&lt;h2 id=&#34;why-self-host-hpc-container-runtimes&#34;&gt;Why Self-Host HPC Container Runtimes?&lt;/h2&gt;&#xA;&lt;p&gt;High-Performance Computing (HPC) centers face a unique containerization challenge: traditional container runtimes like Docker assume root privileges, daemon-based architectures, and layered filesystem overlays that conflict with shared, multi-tenant HPC clusters. HPC-specific container runtimes solve these problems by supporting unprivileged execution, parallel filesystem compatibility, and MPI integration out of the box.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosted HPC MPI Implementations: OpenMPI vs MPICH vs MVAPICH Performance Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-06-01-self-hosted-hpc-mpi-implementations-openmpi-mpich-mvapich-guide/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-01-self-hosted-hpc-mpi-implementations-openmpi-mpich-mvapich-guide/</guid>
      <description>&lt;h2 id=&#34;why-self-host-an-mpi-implementation&#34;&gt;Why Self-Host an MPI Implementation?&lt;/h2&gt;&#xA;&lt;p&gt;Message Passing Interface (MPI) is the foundational communication layer for virtually all parallel scientific computing. Every weather simulation, molecular dynamics calculation, and computational fluid dynamics model depends on efficient inter-process communication across potentially thousands of compute nodes. The choice of MPI implementation directly impacts application performance — different implementations optimize for different hardware (InfiniBand, Omni-Path, Slingshot), different communication patterns (point-to-point vs collective), and different levels of thread safety.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
