exege 0.6.0__tar.gz

exege-0.6.0/.gitignore

@@ -0,0 +1,26 @@
+# the site directory
+site
+
+# any cache
+.cache
+
+# python
+.venv/
+__pycache__/
+*.py[cod]
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+
+# throwaway output: toy archives, fitted bases, whatever is made while trying things
+scratch/
+
+# lock files and tool environments: nothing is pinned here, and CI resolves from
+# pyproject.toml, so a lock is one machine's answer and not the repo's
+uv.lock
+pixi.lock
+.pixi/
+poetry.lock
+pdm.lock
+Pipfile.lock
+conda-lock.yml

exege-0.6.0/PKG-INFO

@@ -0,0 +1,52 @@
+Metadata-Version: 2.5
+Name: exege
+Version: 0.6.0
+Summary: Tools for understanding and evaluating scientific machine-learning models: latent-space diagnostics, sparse autoencoders, figures, a local app
+Project-URL: Homepage, https://mahf708.github.io/exege
+Project-URL: Documentation, https://mahf708.github.io/exege/
+Project-URL: Source, https://github.com/mahf708/exege
+Project-URL: Issues, https://github.com/mahf708/exege/issues
+Author: E3SM AI Group
+License-Expression: BSD-3-Clause
+Keywords: climate,e3sm,emulator,interpretability,machine-learning
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Atmospheric Science
+Requires-Python: >=3.11
+Requires-Dist: exege-core[app,hf]==0.6.0
+Provides-Extra: nn
+Requires-Dist: exege-core[nn]==0.6.0; extra == 'nn'
+Description-Content-Type: text/markdown
+
+# exege
+
+Tools for understanding and evaluating scientific machine-learning models: what an
+emulator holds inside, sparse autoencoders trained on it, figures, and a local app over
+them. The name comes from the Greek stem *exēgē-*, associated with explanation and
+interpretation.
+
+> **Research tool.** `exege` is early. What is described here works; expect it to change.
+
+```console
+$ pip install exege            # everything but torch
+$ pip install 'exege[nn]'      # and torch, for training sparse autoencoders
+$ exege --help
+```
+
+This is the full install. It holds no code of its own: it installs
+[exege-core](https://pypi.org/project/exege-core/) with every extra but `nn`, and both
+provide the same `import exege` and the same `exege` command. For the light install,
+Click only, with each subpackage's dependencies added as you need them:
+
+```console
+$ pip install 'exege-core[latents]'
+```
+
+- Documentation: <https://mahf708.github.io/exege/>
+- Source and issues: <https://github.com/mahf708/exege>
+
+BSD-3-Clause.

exege-0.6.0/README.md

@@ -0,0 +1,28 @@
+# exege
+
+Tools for understanding and evaluating scientific machine-learning models: what an
+emulator holds inside, sparse autoencoders trained on it, figures, and a local app over
+them. The name comes from the Greek stem *exēgē-*, associated with explanation and
+interpretation.
+
+> **Research tool.** `exege` is early. What is described here works; expect it to change.
+
+```console
+$ pip install exege            # everything but torch
+$ pip install 'exege[nn]'      # and torch, for training sparse autoencoders
+$ exege --help
+```
+
+This is the full install. It holds no code of its own: it installs
+[exege-core](https://pypi.org/project/exege-core/) with every extra but `nn`, and both
+provide the same `import exege` and the same `exege` command. For the light install,
+Click only, with each subpackage's dependencies added as you need them:
+
+```console
+$ pip install 'exege-core[latents]'
+```
+
+- Documentation: <https://mahf708.github.io/exege/>
+- Source and issues: <https://github.com/mahf708/exege>
+
+BSD-3-Clause.

exege-0.6.0/pyproject.toml

@@ -0,0 +1,44 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+# The full install: no code of its own, only exege-core with every extra but nn.
+# `import exege` and the `exege` command come from exege-core either way. The version
+# and the pin below move together with `exege.__version__`; tests/test_packaging.py
+# and the release workflow refuse any disagreement.
+[project]
+name = "exege"
+version = "0.6.0"
+description = "Tools for understanding and evaluating scientific machine-learning models: latent-space diagnostics, sparse autoencoders, figures, a local app"
+readme = "README.md"
+requires-python = ">=3.11"
+license = "BSD-3-Clause"
+authors = [{ name = "E3SM AI Group" }]
+keywords = ["interpretability", "emulator", "climate", "e3sm", "machine-learning"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Science/Research",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Scientific/Engineering :: Atmospheric Science",
+]
+dependencies = ["exege-core[app,hf]==0.6.0"]
+
+[project.optional-dependencies]
+# torch is left out of the default: its build (CPU, CUDA) is the machine's business.
+nn = ["exege-core[nn]==0.6.0"]
+
+[project.urls]
+Homepage = "https://mahf708.github.io/exege"
+Documentation = "https://mahf708.github.io/exege/"
+Source = "https://github.com/mahf708/exege"
+Issues = "https://github.com/mahf708/exege/issues"
+
+[tool.uv.sources]
+exege-core = { workspace = true }
+
+# Nothing to package but the metadata.
+[tool.hatch.build.targets.wheel]
+bypass-selection = true