Detecting Outliers in Premise Operations (dopo)
About dopo
The Premise Validation Project introduces the Python package dopo
(Detecting Outliers in Premise Operations), a toolkit
for evaluating the consistency of background life cycle inventories and
identifying anomalies that could affect LCA results.
It is essentially a wrapper around the Brightway2 bw2analyzer library,
combined with a Dash web application for interactive exploration of datasets and results.
🧪 Features
- Detect structural and numerical outliers in ecoinvent-based inventories.
- Interface with Brightway2 and Premise-modified databases.
- Filter or classify activities based on CPC, ISIC, or custom sector definitions.
- Assess differences in environmental impacts from method-to-method or database-to-database.
📊 Dash Web Application
dopo includes a Dash-based interactive app for exploring datasets and visualizing environmental impact scores across projects.
App Features
- ✅ Load and switch between multiple Brightway projects
- ✅ Select one or more background databases
- ✅ Choose a dataset grouping: Sectors, CPC, or ISIC
- ✅ Filter datasets with a search bar
- ✅ (Optional) Exclude market activities using a checkbox
- ✅ Select one or more impact assessment methods
- ✅ View either total impact scores or contribution plots
- ✅ Interactive dropdowns to explore results by sector and method
- ✅ Run calculations and visualize scores in seconds
Installation
You can install dopo via from Anaconda:
$ conda install romainsacchi::dopo
Or via [pip] from [PyPI]:
$ pip install dopo
How to run the app
You can launch the app directly from the terminal using the following command:
dopo-dash
Documentation
https://dopo.readthedocs.io/en/latest/
Contributing
Contributions are very welcome. To learn more, see the Contributor Guide.
License
Distributed under the terms of the MIT license, dopo is free and open source software.
Issues
If you encounter any problems, please file an issue along with a detailed description.
Maintainers
- Romain Sacchi, PSI
- Caroline Friedberger, NTNU
Support
Feel free to contact Romain Sacchi if you have any questions or need help.
Metadata
Release files for dopo 0.0.3
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 |
|---|---|---|---|---|
| dopo-0.0.3.tar.gz | 38.3 kB | Without provenance | Details for dopo-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dopo-0.0.3-py3-none-any.whl | Python 3 | none | any | Details for dopo-0.0.3-py3-none-any.whl |
Total release size: 82.1 kB
Release files / dopo-0.0.3.tar.gz
| Download URL | dopo-0.0.3.tar.gz |
|---|---|
| Size | 38.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
714c77d153017b646922b64f7f3b13cff65552c3c0d2e32755327c611707ae5e
|
|
BLAKE2b-256 checksum How to use checksums |
825db7bd7c615bd86ef41ef00c97b4d3407507da503a8204cc849388224d16df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / dopo-0.0.3-py3-none-any.whl
| Download URL | dopo-0.0.3-py3-none-any.whl |
|---|---|
| Size | 43.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
03d26fb882fcc2e5a1186e1ddcf8fd93b14618d6c3d7916d513760a2faffd17b
|
|
BLAKE2b-256 checksum How to use checksums |
19f93c44989554ed195104ac5ca889a1cf93b9f446d00f0b3df76895a1fe778b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for dopo 0.0.3
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.