aphex-ml 0.1.0a1__tar.gz

aphex_ml-0.1.0a1/.github/workflows/ci.yml

@@ -0,0 +1,86 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+    tags:
+      - "v*"
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          version: "latest"
+
+      - name: Set up Python
+        run: uv python install ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: uv sync --all-extras --dev
+
+      - name: Lint
+        run: uv run ruff check infermap/ tests/
+
+      - name: Type check
+        run: uv run mypy infermap/ --ignore-missing-imports
+
+      - name: Test
+        run: uv run pytest tests/ -v --cov=infermap --cov-report=term-missing
+
+  publish-test:
+    if: startsWith(github.ref, 'refs/tags/v')
+    needs: test
+    runs-on: ubuntu-latest
+    environment: testpypi
+    permissions:
+      id-token: write
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+
+      - name: Build
+        run: uv build
+
+      - name: Publish to TestPyPI
+        run: uv publish --publish-url https://test.pypi.org/legacy/
+
+      - name: Verify install from TestPyPI
+        run: |
+          pip install \
+            --index-url https://test.pypi.org/simple/ \
+            --extra-index-url https://pypi.org/simple/ \
+            aphex-ml
+          aphex --help
+
+  publish:
+    if: startsWith(github.ref, 'refs/tags/v')
+    needs: publish-test
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+
+      - name: Build
+        run: uv build
+
+      - name: Publish to PyPI
+        run: uv publish

aphex_ml-0.1.0a1/.gitignore

@@ -0,0 +1,236 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$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
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.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/
+idea.txt
+aphex.txt
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+.claude/*
+
+
+ALPHA_ROADMAP.md
+idea.txt
+note.txt
+
+# Model artifacts and test data
+model.pt
+calib_data.pt
+eval_data.pt
+infer.py
+*.engine
+*.onnx
+resnet18.pt
+*.pth
+deployment.yaml

aphex_ml-0.1.0a1/.python-version

@@ -0,0 +1 @@
+3.12

aphex_ml-0.1.0a1/CONTRIBUTING.md

@@ -0,0 +1,102 @@
+# Contributing to aphex
+
+## Setup
+
+aphex uses [uv](https://docs.astral.sh/uv/) for dependency management.
+
+```bash
+git clone https://github.com/<your-fork>/aphex
+cd aphex
+uv sync --all-extras --dev
+```
+
+This installs all optional extras (torch, sklearn, onnx, aws, gcp) plus the dev tools (pytest, ruff, mypy).
+
+## Running tests
+
+```bash
+# Fast suite — no network, no real models (~7 s)
+uv run pytest tests/
+
+# Include CUDA-specific tests (requires a GPU)
+uv run pytest tests/ -m requires_cuda
+
+# Integration tests — download real model weights
+uv run pytest tests/ -m integration
+```
+
+Integration tests are excluded by default because they pull weights from the internet. They are the right regression test to run before opening a PR that touches the benchmark or plugin layer.
+
+## Code style
+
+```bash
+uv run ruff check infermap/ tests/   # lint
+uv run ruff format infermap/ tests/  # auto-format
+uv run mypy infermap/                # type check
+```
+
+CI runs all three. A PR that fails lint or type-check won't be merged.
+
+Line length is 100. Target is Python 3.12+.
+
+## Project layout
+
+```
+infermap/
+  cli.py            # Typer CLI — entry point for all commands
+  benchmark.py      # timing loop, BenchmarkResult
+  candidates.py     # DeploymentCandidate generation
+  evaluator.py      # accuracy/F1/MAE/RMSE measurement, cloud eval data download
+  recommender.py    # Pareto filtering + objective ranking → Recommendation
+  pareto.py         # build_pareto_frontier(), rank_by_objective()
+  profiler.py       # HardwareProfile — CPU, CUDA, MPS, CoreML
+  preflight.py      # feasibility check before benchmarking
+  inspector.py      # ModelInfo — parameter count, memory, family
+  converter.py      # export to .pt / .onnx / .engine / .xml
+  selector.py       # candidate fingerprint-based pre-selection
+  cost_model.py     # prune candidates predicted >10× slower than best
+  checker.py        # regression check against a saved deployment.yaml
+  deployment.py     # deployment.yaml read/write
+  report.py         # HTML benchmark report
+  serving/          # serving config generators (Triton, TorchServe, BentoML, FastAPI)
+  cloud/
+    remote.py       # SSH-based remote execution
+    storage.py      # S3 + GCS backends
+    registry.py     # push/pull versioned model artifacts
+    instances.py    # cloud instance profiles for --target
+  plugins/          # per-framework ModelPlugin implementations
+    pytorch.py
+    sklearn.py
+    tensorflow.py
+    llm.py
+  registry.py       # plugin auto-detection from file extension / magic bytes
+tests/
+  integration/      # real-model tests; excluded from default run
+```
+
+## Adding a backend
+
+1. Add a `DeploymentCandidate` entry in `candidates.py` for the appropriate hardware path (`_cuda_candidates`, `_mps_candidates`, `_cpu_candidates`).
+2. Add a benchmark branch in `benchmark.py` (`_benchmark_candidate`) that runs the backend and returns latency/throughput numbers.
+3. Add the backend key to `ALL_CONVERTIBLE` in `converter.py` and implement the export branch if the backend produces a file artifact.
+4. Add accuracy evaluation support in `evaluator.py` (`_PYTORCH_EVAL_BACKENDS` or the sklearn equivalent) if the backend can degrade quality.
+5. Cover all four steps with tests.
+
+## Adding a model family (plugin)
+
+Implement the `ModelPlugin` abstract class in `infermap/plugin.py`:
+
+- `can_handle(path)` — return True if this plugin owns the file
+- `inspect(path)` → `ModelInfo`
+- `load(path)` → model object
+- `generate_candidates(info, hw)` → `list[DeploymentCandidate]`
+- `benchmark(candidate, model, info, shape, batch_size, ...)` → `BenchmarkResult`
+
+Register the plugin in `infermap/registry.py`.
+
+## Pull requests
+
+- Keep PRs focused - one feature or fix per PR.
+- New behaviour needs a test. Bug fixes should include a regression test.
+- Update `README.md` if you change the CLI interface or add a supported backend.
+- CI must pass (lint + type check + tests) before review.

aphex_ml-0.1.0a1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Rayansh Singh
+
+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.