cantera
Runs Cantera homogeneous chemical reactors and evaluates ignition delay with mechanism provenance, conservation checks, and numerical refinement. Use for combustion kinetics, closed adiabatic ideal-gas constant-volume or constant-pressure ignition, temperature histories, or mechanism-specific ignition-delay comparisons.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- cantera
- license
- MIT
- metadata
- { "version": "1.1", "skill-author": "K-Dense Inc.", "last-reviewed": "2026-09-30", "tested-package-version": "3.2.0" }
- description
- Runs Cantera homogeneous chemical reactors and evaluates ignition delay with mechanism provenance, conservation checks, and numerical refinement. Use for combustion kinetics, closed adiabatic ideal-gas constant-volume or constant-pressure ignition, temperature histories, or mechanism-specific ignition-delay comparisons.
- compatibility
- Requires Python 3.12-3.14, Cantera 3.2.0, and NumPy. Installation needs network access; simulations run locally without credentials. Custom mechanisms must be available as Cantera YAML files.
03 SKILL.md 正文
Cantera: homogeneous ignition calculations
When to use
Use for a closed, adiabatic, homogeneous ideal-gas reactor with a known kinetic mechanism, initial temperature, pressure, and mole composition. The bundled helper runs both constant volume and constant pressure cases and reports a precisely defined temperature-based delay. It is not a flame solver or a general reactor-network builder.
A calculation completing successfully establishes numerical execution, not mechanism validity for the fuel, pressure, temperature, diluent, or measured ignition observable. Read references/interpretation.md when choosing a mechanism, comparing experiments, or interpreting unresolved/two-stage ignition.
Workflow
- Identify the mechanism and its validated condition range. Preserve its source, version,
citation, and any modifications. Check that its phase is
ideal-gasand that every reactant, diluent, and tracked species exists. For custom YAML with imports, retain the original dependency files as well as the generated phase snapshot. Custom Python rate extensions additionally need their original code and environment for replay. - Choose constant volume or constant pressure from the physical experiment. Supply K,
Pa, seconds, and mole amounts explicitly.
mole_amountsis normalized to mole fractions; it is not a mass-fraction mapping. The report includes the normalized initial composition. - Copy assets/hydrogen-ignition.json and change its conditions.
The supplied H2/O2/Ar case uses Cantera's bundled
h2o2.yamlfor an executable numerical example; it is not a recommendation for every hydrogen experiment. - Set a time horizon long enough to observe the temperature rise and the decline of the heating-rate peak. Choose output spacing fine enough to locate that peak. Set a minimum temperature rise to distinguish ignition from negligible heating or numerical noise.
- Run the helper and inspect all four histories and the report. Refine again if the delay changes materially, if the maximum approaches a time boundary, or if conservation fails. Compare the temperature and tracked-species histories with the actual ignition definition.
- Report the condition set, mechanism hash, reactor constraint, delay definition, output spacing, numerical changes, and scientific limits together with the delay.
Execute the tested example
From the collection root:
uv run --no-project --python 3.12 --with cantera==3.2.0 --with numpy==2.5.3 \
python skills/cantera/scripts/ignition_delay.py \
skills/cantera/assets/hydrogen-ignition.json hydrogen-result
Tested on Python 3.12, Cantera 3.2.0, and NumPy 2.5.3. No external solver executable or credentials are needed. Local relative mechanism paths resolve against the configuration file directory before Cantera's built-in data search. Use a new output directory each run.
The 1000 K, 101325 Pa, H2:O2:Ar = 2:1:7 constant-volume example gives about 0.313 ms
using the stated max(dT/dt) definition. At 3 ms its temperature is approximately
2920.67 K and agrees with a separate UV equilibrium calculation. These are package
regression values, not experimental validation data.
Exact delay and refinement contract
Delay is the time of the global maximum of numpy.gradient(T, time, edge_order=2) on
a uniform output grid. It is reported only if the maximum temperature rise reaches
minimum_temperature_rise_k and the maximum is at least two sample indices from each
boundary. Otherwise delay_s is null and a status explains why. No delay beyond the
simulation horizon is extrapolated.
The helper explicitly uses Cantera 3.2's clone=True and reads evolving properties from
reactor.phase. The original Solution retains the initial state; do not read it as
the reactor's final state. ReactorNet.advance(t) requests an absolute time, and no
advance limits are configured, so the output grid remains uniform.
It runs four independent fresh reactors:
| Run | Change from configured conditions |
|---|---|
| baseline | Original settings |
| finer_output | Half output spacing, same horizon and solver controls |
| tighter_solver | Both solver tolerances divided by ten; maximum internal time step halved |
| longer_horizon | Twice the horizon with the original output spacing |
numerically_resolved requires all runs to yield delays, relative delay changes within
delay_relative_tolerance, and all conservation checks to pass. Agreement on a discrete
grid is not a statistical error bar: also report the output spacing. The baseline samples
must be between 11 and 50000, leaving room for refinement. Runtime grows with mechanism
size, stiffness, and the chosen horizon; integration failures retain Cantera's error text.
Outputs and checks
report.json: all input settings, package versions, configuration and mechanism hashes, normalized starting composition, four delay estimates, numerical changes, conservation, and mechanism thermodynamic temperature bounds.baseline.csv,finer_output.csv,tighter_solver.csv,longer_horizon.csv: time, temperature, pressure, volume, mass, total internal energy, total enthalpy, and requested species mole fractions.mechanism.yaml: a Cantera-written snapshot of the loaded phase, species, and reactions. The helper requestswrite_yaml(precision=17)and saves the exact UTF-8 bytes it hashes, without platform newline conversion. The report also hashes the located original mechanism file. Imported source dependencies are not separately hashed; the snapshot captures the loaded model. Its generated header includes a date, so the snapshot hash identifies the saved artifact and need not match between otherwise identical reruns.
Closed reactors conserve mass and elemental mass fractions. The constant-volume case
checks total internal energy; the constant-pressure case checks total enthalpy. Energy
error is divided by max(abs(initial_energy_J), 1 J). Diagnostic tolerances are mass
relative drift <1e-8, elemental absolute drift <1e-8, energy scaled drift <1e-6, species
mass-fraction sum error <1e-8, and species mass fractions >-1e-10. These checks expose
numerical issues and do not measure kinetic-model uncertainty.
Check within_thermo_temperature_range separately: it checks saved output states, not
every internal integration state. Numerical resolution does not mean species thermodynamic
fits stayed within their temperature bounds. The helper cannot assess pressure-dependent
kinetic validity from these bounds.
Scope and upstream references
The suite covers both reactor constraints, conservation, final-state agreement with independent Cantera equilibrium, nonigniting conditions, unresolved boundary maxima, refinement, snapshot replay, and invalid composition/conditions. It does not validate shock-tube heat loss, real-gas effects, surfaces, flow devices, flames, or multistage experimental ignition definitions. Build those models only with the necessary physics and their own checks; do not relabel this helper's result as one of them.
- Reactor model equations
- Python reactor API
- Thermodynamic properties and equilibrium
- Phase serialization API
- Custom extension registration
- Cantera 3.2 release notes
- Upstream ignition example uses a species mass-fraction peak; its delay definition differs from this helper's dT/dt peak.
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.