interpreto 0.2.2__tar.gz

interpreto-0.2.2/.editorconfig

@@ -0,0 +1,24 @@
+# Check http://editorconfig.org for more information
+# This is the main config file for this project:
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = true
+
+[*.{py, pyi}]
+indent_style = space
+indent_size = 4
+
+[Makefile]
+indent_style = tab
+
+[*.md]
+trim_trailing_whitespace = false
+
+[*.{diff,patch}]
+trim_trailing_whitespace = false

interpreto-0.2.2/.gitignore

@@ -0,0 +1,179 @@
+.DS_Store
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# PyPI configuration file
+.pypirc
+
+# VSCode
+.vscode/
+
+# Codex
+codex.patch

interpreto-0.2.2/.pre-commit-config.yaml

@@ -0,0 +1,74 @@
+default_language_version:
+  python: python3
+
+default_stages: [pre-commit, pre-push]
+
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: check-ast
+      - id: check-yaml
+        exclude: mkdocs.yml # Non-standard syntax for pymdownx not supported
+      - id: check-added-large-files
+        args: ['--maxkb=2500']
+      - id: check-docstring-first
+      - id: check-toml
+      - id: check-merge-conflict
+      - id: mixed-line-ending
+        args: ['--fix=lf']
+      - id: end-of-file-fixer
+        exclude: LICENSE
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.11.0
+    hooks:
+      - id: ruff-format
+      - id: ruff
+
+  - repo: local
+    hooks:
+      - id: fast-test
+        name: fast-test
+        entry: make
+        args: ["fast-test"]
+        language: system
+        pass_filenames: false
+      - id: clean
+        name: clean
+        entry: make
+        args: ["clean"]
+        language: system
+        pass_filenames: false
+
+  - repo: https://github.com/Lucas-C/pre-commit-hooks
+    rev: v1.5.5
+    hooks:
+      - id: insert-license
+        name: Add MIT license to docs
+        exclude: ^(docs/source)
+        files: \.py$
+        args:
+          - --license-filepath
+          - LICENSE
+
+  - repo: https://github.com/Lucas-C/pre-commit-hooks
+    rev: v1.5.5
+    hooks:
+      - id: insert-license
+        name: insert MIT license
+        exclude: ^(docs/source)
+        files: \.py$
+        args:
+          - --license-filepath
+          - LICENSE
+
+  - repo: local
+    hooks:
+      - id: docs
+        name: build docs
+        entry: make
+        args: ["build-docs"]
+        language: system
+        pass_filenames: false

interpreto-0.2.2/CHANGELOG.md

@@ -0,0 +1,3 @@
+# Changelog
+
+*This file contains a high-level description of changes that were merged into the main branch since the last release. Refer to the releases page for an exhaustive overview of changes introduced at each release.*

interpreto-0.2.2/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [fanny.jourdan@irt-saintexupery.com](mailto:fanny.jourdan@irt-saintexupery.com). All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+<https://www.contributor-covenant.org/faq>

interpreto-0.2.2/LICENSE

@@ -0,0 +1,23 @@
+MIT License
+
+Copyright (c) 2025 IRT Antoine de Saint Exupéry et Université Paul Sabatier Toulouse III - All
+rights reserved. DEEL and FOR are research programs operated by IVADO, IRT Saint Exupéry,
+CRIAQ and ANITI - https://www.deel.ai/.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

interpreto-0.2.2/MANIFEST.in

@@ -0,0 +1,13 @@
+include LICENSE
+include requirements.txt
+include *.md
+include *.py
+include *.yaml
+include *.yml
+recursive-include interpreto *.py
+
+exclude Makefile
+prune .github
+prune docs
+prune examples
+prune tests

interpreto-0.2.2/PKG-INFO

@@ -0,0 +1,283 @@
+Metadata-Version: 2.4
+Name: interpreto
+Version: 0.2.2
+Summary: Interpretability toolbox for LLMs
+Author: FOR Team
+Author-email: fanny.jourdan@irt-saintexupery.com
+Maintainer-email: Fanny Jourdan <fanny.jourdan@irt-saintexupery.com>, Antonin Poché <antonin.poche@irt-saintexupery.com>, Thomas Mullor <thomas.mullor@irt-saintexupery.com>, Gabriele Sarti <gabriele.sarti996@gmail.com>
+License: MIT License
+        
+        Copyright (c) 2025 IRT Antoine de Saint Exupéry et Université Paul Sabatier Toulouse III - All
+        rights reserved. DEEL and FOR are research programs operated by IVADO, IRT Saint Exupéry,
+        CRIAQ and ANITI - https://www.deel.ai/.
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+        
+Project-URL: homepage, https://github.com/FOR-sight-ai/interpreto
+Project-URL: documentation, https://github.com/FOR-sight-ai/interpreto
+Project-URL: repository, https://github.com/FOR-sight-ai/interpreto
+Project-URL: changelog, https://github.com/FOR-sight-ai/interpreto/blob/main/CHANGELOG.md
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Environment :: GPU
+Classifier: Environment :: GPU :: NVIDIA CUDA
+Classifier: Framework :: Jupyter
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Scientific/Engineering :: Visualization
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: transformers[sentencepiece,tokenizers]>=4.22.0
+Requires-Dist: torch>=2.0
+Requires-Dist: overcomplete>=0.2.3
+Requires-Dist: nnsight>=0.4.0
+Requires-Dist: jaxtyping<=0.2.36
+Requires-Dist: beartype
+Requires-Dist: nvidia-cublas-cu11>=11.10.3.66; sys_platform == "Linux"
+Requires-Dist: nvidia-cuda-cupti-cu11>=11.7.101; sys_platform == "Linux"
+Requires-Dist: nvidia-cuda-nvrtc-cu11>=11.7.99; sys_platform == "Linux"
+Requires-Dist: nvidia-cuda-runtime-cu11>=11.7.99; sys_platform == "Linux"
+Requires-Dist: nvidia-cudnn-cu11>=8.5.0.96; sys_platform == "Linux"
+Requires-Dist: nvidia-cufft-cu11>=10.9.0.58; sys_platform == "Linux"
+Requires-Dist: nvidia-curand-cu11>=10.2.10.91; sys_platform == "Linux"
+Requires-Dist: nvidia-cusolver-cu11>=11.4.0.1; sys_platform == "Linux"
+Requires-Dist: nvidia-cusparse-cu11>=11.7.4.91; sys_platform == "Linux"
+Requires-Dist: nvidia-nccl-cu11>=2.14.3; sys_platform == "Linux"
+Requires-Dist: nvidia-nvtx-cu11>=11.7.91; sys_platform == "Linux"
+Provides-Extra: docs
+Requires-Dist: mkdocs>=1.6.1; extra == "docs"
+Requires-Dist: mkdocs-material>=9.5.34; extra == "docs"
+Requires-Dist: mkdocs-autorefs>=1.1.0; extra == "docs"
+Requires-Dist: mkdocs-section-index>=0.3.9; extra == "docs"
+Requires-Dist: mkdocstrings>=0.25.2; extra == "docs"
+Requires-Dist: mkdocstrings-python>=1.10.9; extra == "docs"
+Requires-Dist: mknotebooks>=0.8.0; extra == "docs"
+Requires-Dist: docstr-coverage>=2.3.2; extra == "docs"
+Provides-Extra: lint
+Requires-Dist: setuptools; extra == "lint"
+Requires-Dist: pydoclint>=0.4.0; extra == "lint"
+Requires-Dist: pre-commit>=2.19.0; extra == "lint"
+Requires-Dist: pytest>=7.2.0; extra == "lint"
+Requires-Dist: pytest-cov>=4.0.0; extra == "lint"
+Requires-Dist: pytest-xdist>=3.5.0; extra == "lint"
+Requires-Dist: ruff>=0.2.0; extra == "lint"
+Requires-Dist: virtualenv>=20.26.6; extra == "lint"
+Requires-Dist: networkx>=3.0.0; extra == "lint"
+Requires-Dist: numpy>=2.2.0; extra == "lint"
+Provides-Extra: notebook
+Requires-Dist: ipykernel>=6.29.2; extra == "notebook"
+Requires-Dist: ipywidgets>=8.1.2; extra == "notebook"
+Dynamic: license-file
+
+<div align="center">
+  <img src="docs/assets/img/interpreto_banner.png" alt="Interpreto: Interpretability Toolkit for LLMs">
+<br/>
+
+[![Build status](https://img.shields.io/github/actions/workflow/status/FOR-sight-ai/interpreto/build.yml?branch=main)](https://github.com/FOR-sight-ai/interpreto/actions?query=workflow%3Abuild)
+[![Docs status](https://img.shields.io/readthedocs/interpreto)](TODO)
+[![Version](https://img.shields.io/pypi/v/interpreto?color=blue)](https://pypi.org/project/interpreto/)
+[![Python Version](https://img.shields.io/pypi/pyversions/interpreto.svg?color=blue)](https://pypi.org/project/interpreto/)
+[![Downloads](https://static.pepy.tech/badge/interpreto)](https://pepy.tech/project/interpreto)
+[![License](https://img.shields.io/github/license/FOR-sight-ai/interpreto)](https://github.com/FOR-sight-ai/interpreto/blob/main/LICENSE)
+
+  <!-- Link to the documentation -->
+  <a href="https://for-sight-ai.github.io/interpreto/"><strong>Explore Interpreto docs »</strong></a>
+  <br>
+
+</div>
+
+## ⚠️ Warning
+
+This library is currently in beta and many functions may not work. If you use it anyway, we welcome your comments; please open an issue!
+
+The API might change and the documentation is not up to date.
+
+In particular, it is not yet possible to obtain interpretable concept-based explanations.
+
+## 📚 Table of contents
+
+- [📚 Table of contents](#-table-of-contents)
+- [🚀 Quick Start](#-quick-start)
+- [📦 What's Included](#-whats-included)
+- [👍 Contributing](#-contributing)
+- [👀 See Also](#-see-also)
+- [🙏 Acknowledgments](#-acknowledgments)
+- [👨‍🎓 Creators](#-creators)
+- [🗞️ Citation](#️-citation)
+- [📝 License](#-license)
+
+## 🚀 Quick Start
+
+The library should be available on PyPI soon. Try `pip install interpreto` to install it.
+
+Otherwise, you can clone the repository and install it locally with `pip install -e .`.
+
+And any case, checkout the [attribution walkthrough](https://github.com/FOR-sight-ai/interpreto/tree/main/attribution_walkthrough.ipynb) to get started!
+
+## 📦 What's Included
+
+Interpreto 🪄 provides a modular framework encompassing Attribution Methods, Concept-Based Methods, and Evaluation Metrics.
+
+### Attribution Methods
+
+<details>
+<summary>Interpreto includes both inference-based and gradient-based attribution methods:</summary>
+
+*We currently have these methods available:*
+
+**Inference-based Methods:**
+
+- Occlusion: [Zeiler and Fergus, 2014. Visualizing and understanding convolutional networks](https://link.springer.com/chapter/10.1007/978-3-319-10590-1_53).
+- LIME: [Ribeiro et al. 2013, "Why should i trust you?" explaining the predictions of any classifier](https://dl.acm.org/doi/abs/10.1145/2939672.2939778).
+- Kernel SHAP: [Lundberg and Lee, 2017, A Unified Approach to Interpreting Model Predictions](https://arxiv.org/abs/1705.07874).
+- Sobol Attribution: [Fel et al. 2021, Look at the variance! efficient black-box explanations with sobol-based sensitivity analysis](https://proceedings.neurips.cc/paper/2021/hash/da94cbeff56cfda50785df477941308b-Abstract.html).
+
+**Gradient based methods:**
+
+- Saliency: [Simonyan et al. 2013, Deep Inside Convolutional Networks: Visualising Image Classification Models and Saliency Maps](https://arxiv.org/abs/1312.6034).
+- Integrated Gradient: [Sundararajan et al. 2017, Axiomatic Attribution for Deep Networks](http://proceedings.mlr.press/v70/sundararajan17a.html).
+- SmoothGrad: [Smilkov et al. 2017, SmoothGrad: removing noise by adding noise](https://arxiv.org/abs/1706.03825)
+
+*We will be adding these methods soon (Gradient based methods):*
+
+- InputxGradient: [Simonyan et al. 2013, Deep Inside Convolutional Networks: Visualising Image Classification Models and Saliency Maps](https://arxiv.org/abs/1312.6034).
+- DeepLift: [Shrikumar et al. 2017, Learning Important Features Through Propagating Activation Differences](http://proceedings.mlr.press/v70/shrikumar17a).
+- VarGrad: [Richter et al. 2020, VarGrad: A Low-Variance Gradient Estimator for Variational Inference](https://proceedings.neurips.cc/paper/2020/hash/9c22c0b51b3202246463e986c7e205df-Abstract.html)
+
+</details>
+
+### Concept-Based Methods
+
+<details>
+
+<summary> Concept-based explanations aim to provide high-level interpretations of latent model representations. </summary>
+
+Interpreto generalizes these methods through three core steps:
+
+1. Concept Discovery (e.g., from latent embeddings)
+2. Concept Interpretation (mapping discovered concepts to human-understandable elements)
+3. Concept-to-Output Attribution (assessing concept relevance to model outputs)
+
+**Concept Discovery Techniques** (via [Overcomplete](https://github.com/KempnerInstitute/overcomplete)):
+
+- NMF, Semi-NMF, ConvexNMF
+- ICA, SVD, PCA
+- SAE variants (Vanilla SAE, TopK SAE, JumpReLU SAE, BatchTopK SAE)
+
+**Available Concept Interpretation Techniques:**
+
+- Top-k tokens from tokenizer vocabulary
+
+*Concept Interpretation Techniques Added Soon:*
+
+- Top-k tokens/words/clauses/sentences from specific datasets
+- Input-to-concept attribution from dataset examples ([Jourdan et al. 2023](https://aclanthology.org/2023.findings-acl.317/))
+- Theme prediction via LLMs from top-k tokens/sentences
+
+*Concept Interpretation Techniques Added Later:*
+
+- OpenAI Interpretation ([Bills et al. 2023](https://openai.com/index/language-models-can-explain-neurons-in-language-models/))
+- Aligning concepts with human labels ([Sajjad et al. 2022](https://aclanthology.org/2022.naacl-main.225/))
+- Word cloud visualizations of concepts ([Dalvi et al. 2022](https://arxiv.org/abs/2205.07237))
+- VocabProj & TokenChange ([Gur-Arieh et al. 2025](https://arxiv.org/abs/2501.08319))
+
+**Concept-to-Output Attribution:**
+
+This part will be implemented later, but all the attribution methods presented above will be available here.
+
+*Note that only methods with a concept extraction that has an encoder (input to concept) AND a decoder (concept to output) can use this function.*
+
+**Specific methods:**
+
+**[Available later when all parts are implemented]** Thanks to this generalization encompassing all concept-based methods and our highly flexible architecture, we can easily obtain a large number of concept-based methods:
+
+- CAV and TCAV: [Kim et al. 2018, Interpretability Beyond Feature Attribution: Quantitative Testing with Concept Activation Vectors (TCAV)](http://proceedings.mlr.press/v80/kim18d.html)
+- ConceptSHAP: [Yeh et al. 2020, On Completeness-aware Concept-Based Explanations in Deep Neural Networks](https://proceedings.neurips.cc/paper/2020/hash/ecb287ff763c169694f682af52c1f309-Abstract.html)
+- COCKATIEL: [Jourdan et al. 2023, COCKATIEL: COntinuous Concept ranKed ATtribution with Interpretable ELements for explaining neural net classifiers on NLP](https://aclanthology.org/2023.findings-acl.317/)
+- Yun et al. 2021, [Transformer visualization via dictionary learning: contextualized embedding as a linear superposition of transformer factors](https://arxiv.org/abs/2103.15949)
+- FFN values interpretation: [Geva et al. 2022, Transformer Feed-Forward Layers Build Predictions by Promoting Concepts in the Vocabulary Space](https://aclanthology.org/2022.emnlp-main.3/)
+- SparseCoding: [Cunningham et al. 2023, Sparse Autoencoders Find Highly Interpretable Features in Language Models](https://arxiv.org/abs/2309.08600)
+- Parameter Interpretation: [Dar et al. 2023, Analyzing Transformers in Embedding Space](https://aclanthology.org/2023.acl-long.893/)
+
+</details>
+
+### Evaluation Metrics
+
+**Evaluation Metrics for Attribution**
+
+We don't yet have metrics implemented for attribution methods, but that's coming soon!
+
+**Evaluation Metrics for Concepts**
+
+<details>
+
+<summary> Several properties of the concept-space are desirable. The concept-space should (1) be faithful to the latent space data distribution; (2) have a low complexity to push toward interpretability; (3) be stable across different training regimes.
+ </summary>
+
+- *Concept-space faithfulness:* In Interpreto, you can use the ReconstructionError to define a custom metric by specifying a reconstruction_space and a distance_function. The MSE or FID metrics are also available.
+- *Concept-space complexity:* Sparsity and SparsityRatio metric are available.
+- *Concept-space stability:* You can use Stability metric to compare concept-model dictionaries.
+
+</details>
+
+## 👍 Contributing
+
+Feel free to propose your ideas or come and contribute with us on the Interpreto 🪄 toolbox! We have a specific document where we describe in a simple way how to make your [first pull request](docs/contributing.md).
+
+## 👀 See Also
+
+More from the DEEL project:
+
+- [Xplique](https://github.com/deel-ai/xplique) a Python library dedicated to explaining neural networks (Images, Time Series, Tabular data) on TensorFlow.
+- [Puncc](https://github.com/deel-ai/puncc) a Python library for predictive uncertainty quantification using conformal prediction.
+- [oodeel](https://github.com/deel-ai/oodeel) a Python library that performs post-hoc deep Out-of-Distribution (OOD) detection on already trained neural network image classifiers.
+- [deel-lip](https://github.com/deel-ai/deel-lip) a Python library for training k-Lipschitz neural networks on TensorFlow.
+- [deel-torchlip](https://github.com/deel-ai/deel-torchlip) a Python library for training k-Lipschitz neural networks on PyTorch.
+- [Influenciae](https://github.com/deel-ai/influenciae) a Python library dedicated to computing influence values for the discovery of potentially problematic samples in a dataset.
+- [DEEL White paper](https://arxiv.org/abs/2103.10529) a summary of the DEEL team on the challenges of certifiable AI and the role of data quality, representativity and explainability for this purpose.
+
+## 🙏 Acknowledgments
+
+This project received funding from the French ”Investing for the Future – PIA3” program within the Artificial and Natural Intelligence Toulouse Institute (ANITI). The authors gratefully acknowledge the support of the [DEEL](https://www.deel.ai) and the FOR projects.
+
+## 👨‍🎓 Creators
+
+Interpreto 🪄 is a project of the FOR and the [DEEL](https://www.deel.ai) teams at the [IRT Saint-Exupéry](https://www.irt-saintexupery.com/) in Toulouse, France.
+
+## 🗞️ Citation
+
+If you use Interpreto 🪄 as part of your workflow in a scientific publication, please consider citing 🗞️ our paper (coming soon):
+
+```bibtex
+BibTeX entry coming soon
+```
+
+## 📝 License
+
+The package is released under [MIT license](LICENSE).