heat-exchanger-sizing
Skill7 starsChanged 6 months agoApache-2.0View on GitHub
LMTD-based duty and area estimate for counter- or co-current heat exchangers, with optional multi-pass F-factor correction (via `ht`). Use when sizing a new exchanger or sanity-checking an existing one with known U. Don't use for rigorous Bell-Delaware shell-side analysis, rate-based two-phase boiling/condensation design, or for an unknown U (compute h on each side first via convective-heat-transfer-correlations).
In this repository31 other files it gives its agents.
- absorption-stripping-designSkill
- bayesian-hierarchical-process-modelsSkill
- caustic-merox-extractionSkill
- censored-regressionSkill
- compositional-data-analysisSkill
- control-valve-sizing-isa75Skill
- convective-heat-transfer-correlationsSkill
- design-of-experimentsSkill
- dimensionless-numbersSkill
- distillation-shortcut-designSkill
- distributed-lag-modelsSkill
- engg-skills-commonSkill
- engineering-skill-creatorSkill
- engineering-statisticsSkill
- equation-of-state-selectionSkill
- literature-search-engineeringSkill
- material-energy-balancesSkill
- pipe-flow-pressure-dropSkill
- process-causal-inference-dagsSkill
- process-units-conversionSkill
- reactor-sizing-and-kineticsSkill
- relief-valve-sizing-api520Skill
- separator-vessel-sizingSkill
- sour-gas-amine-treatingSkill
- statistical-process-controlSkill
- steam-tables-iapwsSkill
- thermo-process-propertiesSkill
- time-series-process-data-analysisSkill
- two-phase-flowSkill
- uvSkill
- vle-flash-calculationsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 63
Run the script. Inspect area.
- Very specific: line 88
If ht.LMTD is unavailable, the script falls back to the direct LMTD formula and flags the substitution.
- Distinctive: line 90
If only one stream's enthalpy data is supplied, the script computes the matching cold/hot side from the energy balance, but only when …
- Very specific: line 96
Run the listed script with representative inputs and an --output file when a deterministic calculation is available.
- Distinctive: line 98
Check result magnitudes against the stated assumptions, references, and a hand calculation or known operating range before reporting them.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Heat Exchanger Sizing (LMTD)
Overview
LMTD-based duty and area calculation for a known overall heat transfer
coefficient U. Counter-current or co-current; multi-pass F-factor via the
ht library. Duty can be computed from terminal temperatures or supplied
explicitly.
Prerequisites
uvavailable.
When to Use
- Sizing a new exchanger when you have a defensible U value (vendor data, prior project) and terminal temperatures.
- Sanity-checking an existing exchanger for new conditions.
Don't use for
- Bell-Delaware shell-side design with detailed baffle / bundle configuration.
- Rate-based two-phase boiling or condensation (use a vendor or specialized tool).
- Calculating U from first principles when h on either side is unknown
(use
convective-heat-transfer-correlationsfirst).
Utility Scripts
uv run scripts/size_heat_exchanger.py --hot-in-c 150 --hot-out-c 90 --cold-in-c 25 --cold-out-c 90 --arrangement counterflow --u-w-m2-k 500 --duty-w 1e6 --output /tmp/hx.json
Procedure
- Define hot/cold inlet and outlet temperatures (°C for the bundled script).
- Decide arrangement: counterflow (preferred), co-current, or multi-pass with F-factor.
- Estimate U from either side's h (or vendor data); typical ranges: liquid-liquid 300-1000 W/m²K, liquid-gas 30-100, condensing steam 2000-5000, boiling 1000-4000.
- Provide duty from one stream's sensible heat (m × cp × ΔT) or pass the value if known.
- Run the script. Inspect area; round up to the nearest commercial bundle size.
- Cross-check by computing the other stream's duty and verifying the energy balance closes.
Pitfalls
- Using bare LMTD without the F-factor for multi-pass exchangers.
- Picking U from a textbook table without flagging the fouling factor (overstates U).
- Forgetting that LMTD blows up to ±infinity when terminal differences approach zero (temperature pinch).
- Using sensible-heat duty for a two-phase service (latent heat dominates).
- Reporting required area without acknowledging the fouling allowance.
- Choosing LMTD when one stream is isothermal (condensing / boiling) and using F = 1 by default. Even for single-phase the F-factor is < 1 for multi-pass.
- Picking shell-and-tube as default; for liquid-liquid services with low fouling, a plate-and-frame is often smaller and cheaper.
- Treating the calculated area as final without vendor-validated TEMA layout and pressure-drop check.
Fallback Strategies
- If
ht.LMTDis unavailable, the script falls back to the direct LMTD formula and flags the substitution. - If only one stream's enthalpy data is supplied, the script computes the matching cold/hot side from the energy balance, but only when arrangement allows it.
Verification
- Run the listed script with representative inputs and an
--outputfile when a deterministic calculation is available. - Confirm the JSON result contains
ok: true, expected units, and no unhandled warnings. - Check result magnitudes against the stated assumptions, references, and a hand calculation or known operating range before reporting them.
References
references/methods.md— assumptions, formulas, and U ranges.- TEMA standards (procure separately).
- Sinnott / Coulson & Richardson Vol 6 for U guidance.
Anti-Patterns
- Reporting required area without specifying U and fouling factors.
- Using LMTD with widely different specific heats across the exchanger (Cp varies strongly with T).
- Sizing without checking the temperature pinch.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

