An intuitive tool for structural engineers to design concrete elements efficiently.
This repository provides a comprehensive package for the design and structural analysis of concrete sections, beams and columns. The package adheres to multiple design codes, ensuring broad applicability in structural engineering projects.
Installation
pip install mento
Requires Python 3.12 or newer.
Features
- Check and design for flexure and shear of:
- Rectangular Concrete Beam
- Rectangular One way Slab
- Unit-sensitive design, allowing users to input variables with their respective units for accurate calculations.
- Interactive usage in Jupyter Notebooks, allowing users to create custom calculations using package modules.
- Results are presented in markdown format within the notebook and as pandas DataFrames for easy handling of multiple checks.
- Ability to generate detailed calculation reports in Word.
- Comprehensive testing for design code compliance, including ACI 318-19, EN 1992-2004, and CIRSOC 201-2025.
Where mento fits
mento designs and verifies structural members against a design code, and documents the result: given a section, its materials and a set of load combinations, it returns the required reinforcement, the demand-to-capacity ratios, and a calculation report you can hand to a reviewer.
mento is also, as far as we know, the only open source package that implements CIRSOC 201-2025, the Argentinian concrete design standard.
Using mento at your company?
mento is free and open-source under MIT. If your team wants help going further, we offer a few things on top:
- Team onboarding — short remote sessions to get your engineers productive with Python, Jupyter, VS Code and Git, using mento as the starting point.
- Custom tools — building specific workflows on top of mento (custom reports, integrations with Revit / ETABS / Robot, batch design tools, internal company libraries).
- Sponsored features — if your firm needs a specific element type, design code, or check that's on the roadmap (or not), we can scope it as paid work and contribute it back.
If any of that is useful for your team, fill out this form and we'll follow up.
Not looking for anything? A ⭐ on the repo or feedback in Discussions is also genuinely appreciated.
Roadmap
The development is structured around key milestones, with ongoing tasks that aim to enhance functionality and compliance with design standards:
- Rectangular concrete beam section check and design for ACI 318-19 and CIRSOC 201-25.
- Rectangular concrete beam section check and design for EN 1992-2004.
- One way concrete slab and footing check and design for ACI 318-19 and CIRSOC 201-25.
- One way concrete slab and footing check and design for EN 1992-2004.
- Shear wall shear check and design for ACI 318-19 and CIRSOC 201-25.
- Shear wall shear check and design for EN 1992-2004. (in progress)
- Slab shear punching check and design for ACI 318-19 and CIRSOC 201-25. (in progress)
- Slab shear punching check and design for EN 1992-2004. (in progress)
Each milestone incorporates rigorous testing and continuous integration to ensure code quality and reliability.
Documentation
You can read the official documentation in this link: Mento Docs
Contributing
We welcome contributions from the community to expand and enhance the package. Start with the contributing guide, then look through the open issues — those labelled good first issue are a good entry point. Every calculation contributed to mento is validated against a published worked example before it is merged; the guide explains how.
Participation in this project is governed by our Code of Conduct.
Disclaimer
mento is a tool to assist structural engineers, not a replacement for engineering judgement. Results must be reviewed and accepted by a qualified engineer who takes responsibility for the design. The software is provided "as is", without warranty of any kind, and the authors accept no liability for its use. Verify the output against the applicable design code before relying on it for any real structure.
Citing mento
If mento supports your research or professional work, cite it with the DOI 10.5281/zenodo.21956634, which always resolves to the latest release. Citation metadata is in CITATION.cff, and GitHub's "Cite this repository" button will format it for you. The citing guide explains which version to cite and gives a BibTeX entry.
License
This project is licensed under the MIT License. See LICENSE for the full text.
Release files for mento 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mento-1.1.0.tar.gz | 280.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mento-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 459.2 kB
Release files / mento-1.1.0.tar.gz
| Download URL | mento-1.1.0.tar.gz |
|---|---|
| Size | 280.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
babfe51ec5542742080c814ad733d5e7d935b0e5764d95f0fdafb8c54bef9418
|
|
BLAKE2b-256 checksum How to use checksums |
2ac9f955ff8a39c4d1181cb13de2864815d244a3b73ff4817ccbe69acd456a90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logRelease files / mento-1.1.0-py3-none-any.whl
| Download URL | mento-1.1.0-py3-none-any.whl |
|---|---|
| Size | 179.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c174f40b9532c68a3c1a8230a9a86136387533860120ca06a1f4b6aac52327d1
|
|
BLAKE2b-256 checksum How to use checksums |
a85bd1689b94f126ba37fec341798be3cfebc1ed64b469a4530c5ea9e636eceb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency log