caustic-merox-extraction
Skill7 starsChanged 6 months agoApache-2.0View on GitHub
Screening-level helpers for caustic mercaptan (Merox-style) extraction units: RS-Na loading in caustic, Kremser-style stage performance, and a disulfide carryback risk score. Use for plant troubleshooting, operator discussion, and order-of-magnitude estimation. Don't use for licensor design (use the licensor's package), for amine treating (use sour-gas-amine-treating), or to predict product disulfide concentration exactly — only the carryback risk direction is reliable.
In this repository31 other files it gives its agents.
- absorption-stripping-designSkill
- bayesian-hierarchical-process-modelsSkill
- 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
- heat-exchanger-sizingSkill
- 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
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 77
If loading is approaching available bound alkalinity, regeneration is not keeping pace — investigate the oxidizer / separator side.
- Distinctive: line 79
Use the Kremser estimate to bracket required stages for a given RSH removal.
- Distinctive: line 81
Use the carryback risk score to triage process data when product disulfide is rising.
- Distinctive: line 102
If the Kremser estimate predicts unachievable removal at any reasonable stage count, the dominant problem is likely K (poor distribution) …
- Very specific: line 105
If disulfide carryback score is "high" but product disulfide is low, there may be a strong DMS feed passthrough.
- Very specific: line 111
Run the listed script with representative inputs and an --output file when a deterministic calculation is available.
- Distinctive: line 113
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
Caustic / Merox Mercaptan Extraction Screening
Overview
Thin mass-balance helpers built around the chemistry of mercaptan extraction with aqueous NaOH:
RSH + NaOH → RS-Na + H2Oand the subsequent regeneration (oxidation):
2 RS-Na + 0.5 O2 + H2O → RSSR + 2 NaOHProvides:
- Stoichiometric RS-Na loading at steady extraction.
- Kremser-style stage performance with a user-supplied distribution
coefficient
K = C_LPG / C_caustic. - Risk-score heuristic for disulfide carryback to product LPG (caustic disulfide loading + caustic age + separator dP).
These are screening and troubleshooting tools, not licensor design calculations.
Prerequisites
uvavailable.- On first use, the script writes
LICENSE_NOTIFICATION.txt.
When to Use
- Troubleshooting a Merox unit (rising RSH slip, caustic age question, carryback suspicion).
- Sanity-checking caustic circulation rate vs RS-Na uptake.
- Order-of-magnitude operator discussion.
Don't use for
- Licensor design (UOP Merox package and successors are proprietary; use the licensor's calculations).
- Amine treating: use
sour-gas-amine-treating. - Exact prediction of product disulfide concentration — the carryback score is directional, not quantitative.
Utility Scripts
uv run scripts/merox.py loading --rsh-ppmw 500 --lpg-kg-s 10 --caustic-kg-s 0.5 --naoh-wt 0.12 --output /tmp/load.jsonuv run scripts/merox.py kremser --K 0.02 --lpg-vol 0.014 --caustic-vol 0.0006 --stages 3 --rsh-in 500 --output /tmp/k.jsonuv run scripts/merox.py carryback --caustic-disulfide-ppmw 300 --caustic-age-days 60 --separator-dp-kpa 8 --output /tmp/risk.json
Procedure
- Compute RS-Na loading from inlet RSH and current caustic circulation.
- Compare with the bound-alkalinity available in lean caustic (total alkalinity − free alkalinity).
- If loading is approaching available bound alkalinity, regeneration is not keeping pace — investigate the oxidizer / separator side.
- Use the Kremser estimate to bracket required stages for a given RSH removal.
- Use the carryback risk score to triage process data when product disulfide is rising.
Pitfalls
- Treating
Kas a constant when it depends on caustic concentration, T, and RSH chain length. - Confusing "free alkalinity" with "total alkalinity" — RS-Na consumption reduces free alkalinity.
- Ignoring water carryover between the LPG and caustic phases (and the reverse): the coalescer / sand filter is part of the design envelope.
- Treating the carryback heuristic score as quantitative.
- Treating disulfide rise in product solely as a Merox issue when it could be feed (DMS / DEDS / DMDS passthrough).
- Forgetting that caustic age increases mercaptide loading even at constant RSH inlet; bound alkalinity climbs over time.
- Sizing without considering the disulfide-separator (Stelter/Hsu-style) performance.
Fallback Strategies
- If the Kremser estimate predicts unachievable removal at any reasonable stage count, the dominant problem is likely K (poor distribution) rather than stages; revisit caustic strength and contactor design.
- If disulfide carryback score is "high" but product disulfide is low,
there may be a strong DMS feed passthrough; surface to
vle-flash-calculationsor product-sulfur speciation skill.
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/merox_chemistry.md— chemistry, regeneration, and the practical role of free alkalinity.- Kohl & Nielsen, Gas Purification.
- UOP Merox descriptive literature (public).
Anti-Patterns
- Reporting "Merox is the cause" without considering feed sulfur speciation.
- Treating the carryback score as a value to optimise on rather than a triage indicator.
- Using these helpers for licensor design or rerate.
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.

