Aspen Edr Shell Tube Verify

Aspen EDR Shell Tube Verify

Use this skill to validate Aspen Exchanger Design and Rating V11 quickly and repeatably on Windows.

Quick Start

1. Assume Aspen EDR is already installed.
2. Prefer the bundled script:

$skillRoot = if ($env:CODEX_HOME) {
    Join-Path $env:CODEX_HOME 'skills\aspen-edr-shell-tube-verify'
} else {
    Join-Path $env:USERPROFILE '.codex\skills\aspen-edr-shell-tube-verify'
}
python (Join-Path $skillRoot 'scripts\run_shell_tube_sample.py')

3. Review the printed artifact paths and the final sample window title.

Workflow

1. Check whether an Aspen EDR window for the target sample is already open.
2. If not, launch Aspen EDR with an official shell-and-tube sample from:

C:\Program Files\AspenTech\Aspen Exchanger Design and Rating V11.0\Examples\Shell&Tube

3. Prefer Liquid-Liquid_AEL.EDR for a fast liquid-liquid shell-and-tube verification.
4. Bring the sample window to the foreground and maximize it.
5. Capture an initial screenshot.
6. Trigger Run.
7. Wait for the run to finish, then capture:
   • the post-run window
   • the Errors & Warnings page
   • the Overall Summary page
8. Report whether the sample opened and whether the run completed without result errors.

Fallbacks

• If the user explicitly asks for a public online case, prove the installation first with the official sample, then optionally build a fresh case afterward.
• If the user explicitly refuses built-in samples, create a simple shell-and-tube water-water case manually.
• When creating a fresh case, prefer Aspen Properties plus databank lookup instead of fully manual property tables.
• Do not close the user's existing Aspen session unless asked.

Notes

• Assume Windows and PowerShell.
• Main executable:

C:\Program Files\AspenTech\Aspen Exchanger Design and Rating V11.0\XEQ\AspenEDR.exe

• If multiple Aspen EDR windows are open, work against the sample-specific title rather than the untitled session.
• Treat input warnings as informational unless the user asks for a warning-free file; focus on result errors and successful summary generation.

Script

• Main automation entrypoint: scripts/run_shell_tube_sample.py
• The script writes screenshots into the current working directory by default.