1. Physical consistency: your first line of defenseMartinsen outlined it beautifully: start with the basics.
✅
Liquid density vs molecular weight (or normal boiling point): should increase smoothly.
✅
Viscosity vs molecular weight: same deal, heavier fractions mean thicker fluids.
✅
Boiling point vs carbon number: monotonic, no random dips or spikes.
✅
Critical temperature and pressure vs boiling point: trends that make physical sense.
If you see the opposite, say, density goes up while viscosity goes down, you’re looking at an
inconsistent EOS. In reality, heavier fluids resist flow
more, not less.
Why it matters: small inconsistencies snowball. An unphysical viscosity trend might not crash your simulator today, but it will slowly corrupt every gas huff-n-puff forecast you make.
2. Thermodynamic consistency: where the real pros stand outOnce your physics check passes, dig deeper.
✅
K-values vs boiling point: single carbon numbers should trend cleanly, no weird crossings.
✅
K-values vs pressure: monotonic trends, crossing lines mean unphysical phase preferences.
✅
Binary interaction parameters (BIPs): check neighbors. Opposite-sign BIPs between similar components? Trouble ahead.
Martinsen emphasized this: if your model predicts oil and gas swapping roles halfway through a pressure range, it’s not predicting, it’s guessing.
3. Build a repeatable quality systemWant to separate yourself from 90 % of engineers? Automate the QA.
- Script it: Automate every plot and check. Humans skip steps, scripts don’t.
- Baseline it: Save your “golden EOS.” Compare new versions against it.
- Explain exceptions: If you keep a non-monotonic trend (e.g., due to real lab data), document it clearly.
- Enforce checks: Make quality validation part of your EOS deployment workflow.
That’s how you go from “decent modeler” to “trusted technical lead.”
4. Why positivity and precision matterPeople think QA slows you down. It doesn’t. It speeds you up by killing uncertainty.
When you
know your EOS behaves correctly:
- You stop chasing phantom errors.
- You trust your simulation results.
- You save days of debugging.
- You impress clients and management alike.
In Martinsen’s words: “Whether you receive an EOS or you yourself have developed an EOS, it is always a good idea to quality check the EOS.”
Couldn’t agree more.
5. TakeawayMost EOS models fail not because of bad math—but because no one bothered to
check them.
If you want to stop flying blind, use Martinsen’s checklist. Automate it. Baseline it. Bake it into your workflow until quality control becomes second nature.
Do that, and your EOS stops being a mysterious black box, it becomes a trustworthy engine for better decisions.
And if you want your EOS model properly QC’d, reach out to
markushays@whitson.com. Markus and the whitson team have turned EOS quality control into an art form.