<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Modeling Notes on CoolSim | SaaS CFD for Data Center Airflow &amp; Thermal Optimization</title><link>https://coolsimsoftware.com/notes/</link><description>Recent content in Modeling Notes on CoolSim | SaaS CFD for Data Center Airflow &amp; Thermal Optimization</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 13 Aug 2026 09:00:00 -0400</lastBuildDate><atom:link href="https://coolsimsoftware.com/notes/index.xml" rel="self" type="application/rss+xml"/><item><title>The return path you never drew</title><link>https://coolsimsoftware.com/notes/the-return-path-you-never-drew/</link><pubDate>Thu, 13 Aug 2026 09:00:00 -0400</pubDate><guid>https://coolsimsoftware.com/notes/the-return-path-you-never-drew/</guid><description>&lt;p&gt;Welcome to the first issue of &lt;em&gt;Modeling Notes&lt;/em&gt;. The short version of why this exists: we watch a lot of thermal models run — and the same handful of patterns come up over and over. Each issue takes one apart: the symptom, the physics, the fix. Five minutes, no fluff, no pitch.&lt;/p&gt;
&lt;h2 id="the-symptom"&gt;The symptom&lt;/h2&gt;
&lt;p&gt;The model solves, but rack inlet temperatures come in a few degrees hotter than anything you&amp;rsquo;d measure on the floor — or the solution drifts instead of settling. Nothing errors. It just reads wrong.&lt;/p&gt;</description></item></channel></rss>