atomecon
🧪 Try it live in your browser - no install needed.
Lightweight green chemistry metrics - atom economy, theoretical yield, percent yield, E-factor, and automatic equation balancing - computed from plain chemical formulas. No RDKit, no SMILES, no dependencies.
Who this is for
- Chemistry students taking green chemistry coursework, tired of redoing molar-mass arithmetic by hand for every reaction
- Anyone comparing multiple synthesis routes for the same product, who wants to score them programmatically instead of recalculating each one manually
- Developers who want atom economy and equation balancing without installing RDKit or learning SMILES notation
Why this exists
Existing chemistry packages either don't cover green chemistry metrics at all, or require RDKit and SMILES notation to calculate even a single metric like atom economy. atomecon bundles the standard metrics together, balances equations automatically, takes formulas the way you'd write them in a chemistry class ("C2H5OH", not "CCO"), and has zero dependencies.
Install
pip install atomecon
Quick start
from atomecon import analyze
analyze(["CH4", "O2"], ["CO2", "H2O"], desired_product="CO2")
Balances the equation and prints a report. No coefficients, no separate method calls.
The three kinds of number
This is the distinction the whole library is built around, and the one students most often blur together.
Atom economy is about the reaction you chose. It asks what fraction of the reactant mass ends up in the product you wanted, according to the balanced equation. It needs no lab data, and it is identical for everyone who ever runs that reaction. Better technique cannot improve it. Only a different route can.
Percent yield is about how you ran it. It compares what you actually isolated against the most the equation allows, given the masses you started with. It varies run to run.
E-factor is about waste, in grams of waste per gram of product.
atomecon keeps this explicit in its API: atom_economy() takes no arguments, while percent_yield() and e_factor() require real measured masses.
The E-factor floor
E-factor and atom economy are not independent, and this trips people up. Even a flawless run discards every atom the equation sends into the other products. So the lowest E-factor a reaction can ever reach is fixed by its atom economy:
E-factor floor = 100 / atom economy - 1
A reaction at 100% atom economy has a floor of 0. One at 50% has a floor of 1.0: a gram of waste per gram of product, forever, no matter how carefully it is run. Methane combustion at 55% can never get below 0.82.
from atomecon import Reaction
rxn = Reaction.auto(["CH4", "O2"], ["CO2", "H2O"], desired_product="CO2")
print(rxn.e_factor_floor())
# 0.819... the best this equation can ever do
masses = {"CH4": 16.043, "O2": 63.996}
print(rxn.excess_e_factor(masses, actual_yield_g=44.0))
# 0.0 a flawless run: all remaining waste is forced by the equation
Green grade
A single A-F letter for comparing reactions at a glance.
print(rxn.green_grade(masses, actual_yield_g=44.0))
# B (Atom economy: 55% | E-factor: 0.8, best possible 0.8)
It scores two deliberately separate things:
- Atom economy scores the route you picked.
- Avoidable waste - E-factor above the floor - scores how you ran it.
Grading raw E-factor instead would punish a low-atom-economy reaction twice for the same fact, since its floor is set by its atom economy. Under that older approach a perfect run of methane combustion scored no better than a careless one, because the reaction could never reach the top E-factor band regardless. Grading the avoidable part fixes that: technique becomes visible, while a wasteful route still cannot reach an A.
This is a transparent scoring rule of our own devising, not a scientific standard. The bands live in green_grade() and you are welcome to disagree with them.
Full walkthrough
from atomecon import Reaction
# Aspirin synthesis: salicylic acid + acetic anhydride -> aspirin + acetic acid
rxn = Reaction(
reactants={"C7H6O3": 1, "C4H6O3": 1},
products={"C9H8O4": 1, "C2H4O2": 1},
desired_product="C9H8O4",
)
print(rxn.atom_economy())
# 75.0 (theoretical - no lab data needed)
masses = {"C7H6O3": 5.0, "C4H6O3": 5.0}
print(rxn.limiting_reactant(masses)) # C7H6O3 - runs out first
print(rxn.theoretical_yield_g(masses)) # 6.52 g
print(rxn.percent_yield(masses, actual_yield_g=4.2)) # 64.4
print(rxn.e_factor(masses, actual_yield_g=4.2)) # 1.38
print(rxn.e_factor_floor()) # 0.33
print(rxn.excess_e_factor(masses, actual_yield_g=4.2)) # 1.05
print(rxn.green_grade(masses, actual_yield_g=4.2)) # B (...)
print(rxn.summary_table(reactant_masses_g=masses, actual_yield_g=4.2))
Automatic equation balancing
rxn = Reaction.auto(["N2", "H2"], ["NH3"], desired_product="NH3")
print(rxn)
# <Reaction N2 + 3H2 -> 2NH3>
Gaussian elimination over exact fractions, solving for the smallest whole-number coefficients.
If you only want the coefficients and not a whole Reaction:
from atomecon import balance_equation
reactants, products = balance_equation(["CH4", "O2"], ["CO2", "H2O"])
print(reactants, products)
# {'CH4': 1, 'O2': 2} {'CO2': 1, 'H2O': 2}
Known limitation: a small number of equations have more than one valid balancing ratio. This is a genuine mathematical ambiguity, not a bug. Those raise a clear error asking you to supply coefficients yourself rather than guessing. The aspirin synthesis above is one of them, which is why that example is written out with explicit coefficients.
Impossible results are refused
A yield heavier than everything you put in violates conservation of mass. Left unchecked it produces negative waste, a negative E-factor, and a flattering grade for a reaction that cannot exist.
rxn = Reaction.auto(["CH4", "O2"], ["CO2", "H2O"], desired_product="CO2")
rxn.e_factor({"CH4": 1.0, "O2": 2.0}, actual_yield_g=40.0)
# ValueError: actual_yield_g (40.00 g) is greater than the total mass of
# reactants used (3.00 g). That breaks conservation of mass ...
Reaction also verifies the equation is atom-balanced on construction. Pass allow_unbalanced=True to override.
Learning mode: see the calculation
print(rxn.explain_atom_economy())
Prints the molar masses, the coefficients, the totals, and the final division as numbered steps.
For the same numbers as data rather than prose:
parts = rxn.atom_economy_breakdown()
print(parts["total_reactant_mass"]) # 80.039
print(parts["reactants"][0]) # {'formula': 'CH4', 'coefficient': 1, ...}
Comparing reactions
from atomecon import Reaction, ReactionLog
combustion = Reaction.auto(["CH4", "O2"], ["CO2", "H2O"], desired_product="CO2")
log = ReactionLog()
log.add(
"Methane combustion",
combustion,
reactant_masses_g={"CH4": 16.043, "O2": 63.996},
actual_yield_g=44.0,
)
log.add("Haber process", Reaction.auto(["N2", "H2"], ["NH3"], desired_product="NH3"))
print(log.comparison_table())
Prints a table sorted by atom economy, greenest first. For the same data as records you can feed into a spreadsheet or a web page:
for record in log.to_records():
print(record["name"], record["atom_economy"], record["grade_letter"])
ReactionLog is in-memory only. It resets each time your program runs.
Display helpers
equation() returns plain ASCII, which is what you want for terminals, monospace tables, and anything a machine reads back. For showing to people:
print(rxn.pretty_equation())
# CH₄ + 2O₂ → CO₂ + 2H₂O
from atomecon import to_subscripts
print(to_subscripts("Ca(OH)2"))
# Ca(OH)₂
Coefficients stay full size, because they multiply the molecule rather than counting atoms inside it.
Formula plausibility checking
from atomecon import is_formula_plausible
is_formula_plausible("C8H18") # True (real octane)
is_formula_plausible("C8H23") # False (impossible - odd total valence)
is_formula_plausible("Fe2O3") # True (iron has variable valence - not checked)
Important limitation: this can only rule formulas out as impossible. It cannot prove a formula is real, and it deliberately skips elements with variable valence (iron, sulfur, phosphorus, nitrogen, most transition metals) rather than risk a wrong answer. This is one mathematical shortcut, not a replacement for real molecular validity checking.
To see the reasoning rather than just the verdict:
from atomecon import explain_formula_plausibility
print(explain_formula_plausibility("C8H23"))
Formula syntax
from atomecon import parse_formula, molar_mass
parse_formula("Ca(OH)2") # {"Ca": 1, "O": 2, "H": 2}
parse_formula("Fe3(Fe(CN)6)2") # {"Fe": 5, "C": 12, "N": 12}
molar_mass("C6H12O6") # 180.156
What this library does NOT do
- Does not verify a formula represents a real molecule beyond the valence-parity check above. No bonding or structure model like RDKit.
- Does not verify a reaction is chemically real. It will happily compute metrics for an atom-balanced but chemically impossible reaction.
- No charge or ionic support. Formulas are tracked by atoms only, not electric charge.
- The green grade is not a standard. It is a scoring rule of our own.
Try the demo
demo.py ships with the source, not with the wheel, so grab the repository:
git clone https://github.com/JvenDeepak0203/atomecon
cd atomecon
python demo.py
A guided tour: balancing, the yield-versus-atom-economy distinction, the E-factor floor, route comparison, and the conservation-of-mass check.
Web app
Live at atomecon.streamlit.app, or run it yourself:
pip install streamlit
streamlit run app.py
Yield sliders are capped at the theoretical maximum, so impossible results cannot be entered. Reactions can be saved, compared side by side, and exported to CSV.
Running tests
pip install pytest
pytest
Changelog
0.1.2
- Yields exceeding the total reactant mass are now rejected. Previously these produced a negative E-factor and an undeservedly good grade.
green_grade()now scores avoidable waste (E-factor above the floor) rather than raw E-factor, so a low-atom-economy reaction is no longer penalised twice and good technique is visible.- New:
limiting_reactant(),e_factor_floor(),excess_e_factor(),atom_economy_breakdown(),pretty_equation(),to_subscripts(),ReactionLog.to_records(). comparison_table()now uses stable column widths and right-aligned numbers.- Added
demo.py, which earlier versions of this README referenced without shipping it. - Web app: example presets, saved-reaction comparison, CSV export, formatted working.
0.1.1 - initial public release.
License
MIT
Metadata
Release files for atomecon 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| atomecon-0.1.2.tar.gz | 34.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atomecon-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.5 kB
Release files / atomecon-0.1.2.tar.gz
| Download URL | atomecon-0.1.2.tar.gz |
|---|---|
| Size | 34.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3de4fdf57ff72ae6104659e2fc71d3befa33c4b5831739763e1717ffdc939d7
|
|
BLAKE2b-256 checksum How to use checksums |
5ef268e43e976478f40d94efedadcc795d9eee4625f25d01506516eea28b1d1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / atomecon-0.1.2-py3-none-any.whl
| Download URL | atomecon-0.1.2-py3-none-any.whl |
|---|---|
| Size | 20.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26abc78470947b1710f17417f049f367d610782597f440ae9688d6e9c77b8cef
|
|
BLAKE2b-256 checksum How to use checksums |
1c40a2f2357aa64edca2011c83425ab4a44a735ad273fbce2e84d15122dcc8ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for atomecon 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.