vibeflow-postprocess

Extract metrics, plots, and tables from OpenFOAM C-run and caseDict results.

12|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/sunrise-hjx/vibeFlow-skills --skill vibeflow-postprocess
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibeflow-postprocess
Source: https://github.com/sunrise-hjx/vibeFlow-skills/tree/main/vibeflow-postprocess
Command: npx skills add https://github.com/sunrise-hjx/vibeFlow-skills --skill vibeflow-postprocess

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns solver results into evidence that can answer the user's question by extracting metrics, field images, tables, and traceable conclusions around OpenFOAM outputs from C-run and 0-caseDict/caseDict, including postProcessing data, probes, forces, forceCoeffs, samples, field files, solver logs, Python metrics, ParaView/pvpython scenes, and report-ready artifacts.

Core Features & Use Cases

  • Post-processing metrics extraction (drag, pressure drop, flow rate, etc.) from C-run and caseDict data for decision support.
  • Visualization with Python metrics and ParaView pvpython scenes, producing figures, tables, and animations for reporting.
  • Use cases include validation of solver convergence, preparation of report-ready summaries, case comparisons, and stakeholder-ready evidence artifacts.

Quick Start

Run the post-processing workflow to extract metrics and generate report-ready artifacts from the latest C-run and caseDict outputs.

Frequently Asked Questions about vibeflow-postprocess

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract metrics from OpenFOAM postProcessing data?

OpenFOAM post-processing extracts metrics by reading C-run outputs and 0-caseDict/caseDict structures to pull values like drag, pressure drop, and flow rate from solver logs, probes, and forceCoeffs artifacts for decision support.

Can I generate report-ready figures from OpenFOAM results using ParaView pvpython?

Yes, generating report-ready figures from OpenFOAM results uses Python metrics and ParaView pvpython scenes to produce visualizations, tables, and summaries for stakeholder reporting.

What is the best way to validate OpenFOAM solver convergence during post-processing?

Validating OpenFOAM solver convergence involves extracting metrics from solver logs and postProcessing artifacts to compare against expected values, ensuring simulation stability and accuracy before reporting.

Do I need caseDict files to perform OpenFOAM post-processing and visualization?

Yes, caseDict files are required for OpenFOAM post-processing and visualization, as they define the extraction rules and configurations needed to generate metrics, figures, and tables from C-run directories.

How do I compare multiple OpenFOAM cases using post-processing metrics?

Comparing multiple OpenFOAM cases uses post-processing metrics extracted from C-run and caseDict data to generate side-by-side tables and figures, enabling evidence-based conclusions for case selection.

What limitations exist when extracting Python metrics from OpenFOAM outputs?

Extracting Python metrics from OpenFOAM outputs requires access to structured C-run directories and postProcessing artifacts; without proper caseDict configurations, the extraction of field files and solver log data may fail.