SMEFiT is a python program for Standard Model Effective Field Theory fits
Installation
To install the smefit release on PYPI you can do:
pip install smefit
Installation for developers
If you are interested in developing smefit or having the latest smefit code not yet released, you should clone the smefit repository and then install in editable mode:
cd smefit_release
pip install -e .
If one is interested in having smefit installed in a conda environment, this can be done by creating the environment (for example with python 3.12), activating it and then installing inside the environment.
conda create python=3.12 -n smefit-dev
conda activate smefit-dev
pip install -e .
Running
The fitting code provide two fitting strategies.
To run the code with Nested Sampling you can do:
smefit NS <path_to_runcard>
To run the code suing the analytic method (valid only for linear fits) you can do:
smefit A <path_to_runcard>
An runcard example is provided in runcards/test_runcard.yaml.
You can also do smefit -h for more help.
Running in parallel
To run smefit with Nested Sampling in parallel you can do:
mpiexec -n number_of_cores smefit NS <path_to_runcard>
Documentation
If you want to build the documentation do:
cd docs
make html
Unit tests
To run the unit test you need to install:
pip install pytest pytest-env pytest-cov
And then simply run:
pytest
Reports
To run reports and produce PDF and HTML output you need to have pandoc and pdflatex installed. The first one is available in conda the latter can be sourced in:
souce /cvmfs/sft.cern.ch/lcg/external/texlive/2020/bin/x86_64-linux/pdflatex
Citation policy
Please cite our paper when using the code:
@article{Giani:2023gfq,
author = "Giani, Tommaso and Magni, Giacomo and Rojo, Juan",
title = "{SMEFiT: a flexible toolbox for global interpretations of particle physics data with effective field theories}",
eprint = "2302.06660",
archivePrefix = "arXiv",
primaryClass = "hep-ph",
reportNumber = "Nikhef-2022-023",
month = "2",
year = "2023"
}
Metadata
Release files for smefit 4.0.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 | Provenance | Actions |
|---|---|---|---|---|
| smefit-4.0.0.tar.gz | 134.9 kB | With provenance | Details for smefit-4.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| smefit-4.0.0-py3-none-any.whl | Python 3 | none | any | Details for smefit-4.0.0-py3-none-any.whl |
Total release size: 286.0 kB
Release files / smefit-4.0.0.tar.gz
| Download URL | smefit-4.0.0.tar.gz |
|---|---|
| Size | 134.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5b839f5904c9d55cf7b8a083abc17fc3471c8e3f3355809d478d5a4a375fefc
|
|
BLAKE2b-256 checksum How to use checksums |
21259a673fd52910f44d911d436b846c0c6dfdcc26577d97f19c0d70baec313b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 22, 2026.
Transparency logRelease files / smefit-4.0.0-py3-none-any.whl
| Download URL | smefit-4.0.0-py3-none-any.whl |
|---|---|
| Size | 151.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
866fbc70276565c36114c7ce376603264ccf52ea5e2137548e3f680103c3427a
|
|
BLAKE2b-256 checksum How to use checksums |
d458eb93fc6d24b69349a837d983073748378a431a8791c74a82ffb3f7b0b0ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 22, 2026.
Transparency logSecurity for smefit 4.0.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for smefit-4.0.0.tar.gz
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 Apr 22, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.