qpytorch 0.1__tar.gz

qpytorch-0.1/.conda/meta.yaml

@@ -0,0 +1,52 @@
+{% set _version_match = load_file_regex(
+  load_file="qpytorch/version.py",
+  regex_pattern="__version__ = version = '(.+)'"
+) %}
+{% set version = _version_match[1] %}
+
+package:
+  name: qpytorch
+  version: {{ version }}
+
+source:
+  path: ../
+
+build:
+  noarch: python
+  script: "$PYTHON ./setup.py install --single-version-externally-managed --record=record.txt"
+
+requirements:
+  host:
+    - python>=3.10
+
+  run:
+    - python>=3.10
+    - jaxtyping
+    - linear_operator>=0.6
+    - mpmath>=0.19,<=1.3
+    - pytorch>=2.2
+    - scikit-learn
+    - gpytorch>=1.13
+
+test:
+  imports:
+    - qpytorch
+    - qpytorch.distributions
+    - qpytorch.functions
+    - qpytorch.kernels
+    - qpytorch.lazy
+    - qpytorch.likelihoods
+    - qpytorch.means
+    - qpytorch.mlls
+    - qpytorch.models
+    - qpytorch.priors
+    - qpytorch.utils
+    - qpytorch.variational
+
+about:
+  home: https://lanzithinking.github.io/QePyTorch/
+  license: MIT
+  license_file: LICENSE
+  summary: An implementation of Q-Exponential Processes in Pytorch built from GPyTorch
+  doc_url: https://qepytorch.readthedocs.io/en/latest/
+  dev_url: https://github.com/lanzithinking/qepytorch

qpytorch-0.1/.github/workflows/deploy.yml

@@ -0,0 +1,59 @@
+# This workflow will upload a Python Package using Twine when a release is created
+# For more information see: https://help.github.com/en/actions/language-and-framework-guides/using-python-with-github-actions#publishing-to-package-registries
+
+name: Upload Python Package to PyPI and Anaconda
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  run_test_suite:
+    uses: ./.github/workflows/run_test_suite.yml
+
+  deploy_pypi:
+    runs-on: ubuntu-latest
+    needs: run_test_suite
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python
+      uses: actions/setup-python@v2
+      with:
+        python-version: "3.10"
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install setuptools_scm setuptools wheel twine
+    - name: Build and publish
+      env:
+        TWINE_USERNAME: ${{ secrets.PYPI_USERNAME }}
+        TWINE_PASSWORD: ${{ secrets.PYPI_PASSWORD }}
+      run: |
+        python -m setuptools_scm
+        python setup.py sdist bdist_wheel
+        twine upload dist/*
+
+  deploy_conda:
+    runs-on: ubuntu-latest
+    needs: run_test_suite
+    steps:
+    - uses: actions/checkout@v2
+    - uses: conda-incubator/setup-miniconda@v2
+      with:
+        auto-update-conda: false
+        python-version: "3.10"
+    - name: Install dependencies
+      run: |
+        conda install -y anaconda-client conda-build
+        conda install linear_operator gpytorch -c gpytorch
+        pip install setuptools_scm
+    - name: Build and publish
+      run: |
+        conda config --set anaconda_upload yes
+        conda config --append channels pytorch
+        conda config --append channels gpytorch
+        conda config --append channels conda-forge
+        /usr/share/miniconda/bin/anaconda login --username ${{ secrets.CONDA_USERNAME }} --password ${{ secrets.CONDA_PASSWORD }}
+        python -m setuptools_scm
+        conda build .conda
+        /usr/share/miniconda/bin/anaconda logout

qpytorch-0.1/.github/workflows/run_test_suite.yml

@@ -0,0 +1,85 @@
+# This workflow will install Python dependencies, run tests and lint with a variety of Python versions
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-python-with-github-actions
+
+name: Run Test Suite
+
+on:
+  push:
+    branches: [ main, develop ]
+  pull_request:
+    branches: [ main, develop ]
+  workflow_call:
+
+jobs:
+  # run_linter:
+  #   runs-on: ubuntu-latest
+  #   steps:
+  #   - uses: actions/checkout@v2
+  #   - name: Set up Python
+  #     uses: actions/setup-python@v2
+  #     with:
+  #       python-version: "3.10"
+  #   - name: Install dependencies
+  #     run: |
+  #       pip install flake8==4.0.1 flake8-print==4.0.0 pre-commit
+  #       pre-commit install
+  #   - name: Run linting
+  #     run: |
+  #       flake8
+  #   - name: Run pre-commit checks
+  #     # skipping flake8 here (run separatey above b/c pre-commit does not include flake8-print)
+  #     run: |
+  #       SKIP=flake8 pre-commit run --files test/**/*.py qpytorch/**/*.py
+  #   - name: Upload coverage reports to Codecov
+  #     uses: codecov/codecov-action@v3
+
+  run_unit_tests:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        pytorch-version: ["main", "stable"]
+        extras: ["with-extras", "no-extras"]
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python
+      uses: actions/setup-python@v2
+      with:
+        python-version: "3.10"
+    - name: Install dependencies
+      run: |
+        if [[ ${{ matrix.pytorch-version }} = "main" ]]; then
+          pip install --pre torch -f https://download.pytorch.org/whl/nightly/cpu/torch_nightly.html;
+        else
+          pip install "numpy<2"  # Numpy 2.0 is not fully supported until PyTorch 2.2
+          pip install torch==2.0+cpu -f https://download.pytorch.org/whl/torch_stable.html
+        fi
+        pip install -e .
+        if [[ ${{ matrix.extras }} == "with-extras" ]]; then
+          pip install "pyro-ppl>=1.8";
+          pip install pykeops;
+          pip install faiss-cpu;  # Unofficial pip release: https://pypi.org/project/faiss-cpu/#history
+        fi
+    - name: Run unit tests
+      run: |
+        python -m unittest discover
+
+  run_examples:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python
+      uses: actions/setup-python@v2
+      with:
+        python-version: "3.10"
+    - name: Install dependencies
+      run: |
+        pip install "numpy<2"  # Numpy 2.0 is not fully supported until PyTorch 2.2
+        pip install torch==2.0+cpu -f https://download.pytorch.org/whl/torch_stable.html
+        pip install pytest nbval jupyter tqdm matplotlib torchvision scipy
+        pip install -e .
+        pip install "pyro-ppl>=1.8";
+        pip install pykeops;
+        pip install faiss-cpu;  # Unofficial pip release: https://pypi.org/project/faiss-cpu/#history
+    - name: Run example notebooks
+      run: |
+        grep -l smoke_test examples/**/*.ipynb | xargs grep -L 'smoke_test = False' | CI=true xargs pytest --nbval-lax --current-env

qpytorch-0.1/.gitignore

@@ -0,0 +1,196 @@
+# 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/
+
+# 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 enitre vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+.DS_Store

qpytorch-0.1/.readthedocs.yaml

@@ -0,0 +1,35 @@
+# .readthedocs.yml
+# Read the Docs configuration file
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+# Required
+version: 2
+
+build:
+  os: "ubuntu-22.04"
+  tools:
+    python: "3.10"
+  jobs:
+    pre_install:  # Lock version of torch at 2.0
+      - pip install "numpy<2"  # Numpy 2.0 is not fully supported until PyTorch 2.2
+      - pip install torch==2.0+cpu -f https://download.pytorch.org/whl/torch_stable.html
+    pre_build:
+      - python -m setuptools_scm  # Get correct version number
+
+# Build documentation in the docs/ directory with Sphinx
+sphinx:
+  configuration: docs/source/conf.py
+#   fail_on_warning: true
+
+# Optionally build your docs in additional formats such as PDF
+#formats:
+  #- pdf
+
+# Optionally set the version of Python and requirements required to build your docs
+python:
+  install:
+    - method: pip
+      path: .
+      extra_requirements:
+        - docs
+        - pyro

qpytorch-0.1/CONTRIBUTING.md

@@ -0,0 +1,130 @@
+# Contributing to Q<sup style="font-size: 0.5em;">&#9428;</sup>PyTorch
+
+Thanks for contributing!
+
+## Development installation
+
+To get the development installation with all the necessary dependencies for
+linting, testing, and building the documentation, run the following:
+```bash
+git clone https://github.com/lanzithinking/qepytorch.git
+cd qpytorch
+pip install -e .[dev,docs,examples,keops,pyro,test]  # keops and pyro are optional
+pre-commit install
+```
+
+
+## Our Development Process
+
+### Formatting and Linting
+
+Q<sup style="font-size: 0.5em;">&#9428;</sup>PyTorch uses [pre-commit](https://pre-commit.com) for code formatting
+and [flake8](https://flake8.pycqa.org/en/latest/) for linting.
+This enforces a common code style across the repository.
+The [development installation instructions](#development-installation) should install both tools, and no additional configuration should be necessary.
+
+`flake8` and `pre-commit` are both run every time you make a local commit.
+To run both commands independent of making a commit:
+```bash
+SKIP=flake8 pre-commit run --files test/**/*.py qpytorch/**/*.py
+flake8
+```
+
+### Docstrings
+We use [standard sphinx docstrings](https://sphinx-rtd-tutorial.readthedocs.io/en/latest/docstrings.html) (not Google-style).
+
+
+### Type Hints
+
+Q<sup style="font-size: 0.5em;">&#9428;</sup>PyTorch aims to be fully typed using Python 3.8+
+[type hints](https://www.python.org/dev/peps/pep-0484/).
+
+We recognize that we have a long way to go towards fully typing the library,
+but we expect all contributions to also use proper type annotations.
+While we currently do not enforce full consistency of these in our continuous integration
+test, you should strive to type check your code locally.
+For this we recommend using [pyre](https://pyre-check.org/).
+
+
+### Unit Tests
+
+We use python's `unittest` to run unit tests:
+```bash
+python -m unittest
+```
+
+- To run tests within a specific directory, run (e.g.) `python -m unittest discover -s test/kernels`.
+- To run a specific unit test, run (e.g.) `python -m unittest test.operators.test_rbf_kernel.TestRBFKernel.test_active_dims_range`.
+
+
+### Documentation
+
+Q<sup style="font-size: 0.5em;">&#9428;</sup>PyTorch uses sphinx to generate documentation, and ReadTheDocs to host documentation.
+To build the documentation locally, ensure that sphinx and its plugins are properly installed (see the [development installation section](#development-installation) for instructions).
+Then run:
+
+```bash
+cd docs
+SKIP_EXAMPLES=true make html
+cd build/html
+python -m http.server 8000
+```
+
+If you are making an update to one of the example notebooks, drop the `SKIP_EXAMPLES=true` environment variable:
+(This takes longer to build.)
+
+```bash
+cd docs
+make html
+cd build/html
+python -m http.server 8000
+```
+
+The documentation will be available at http://localhost:8000.
+You will have to rerun the `make html` or `SKIP_EXAMPLES=true make html` command every time you wish to update the docs.
+
+**Important**: Our CI requires that the documentation compiles *WITHOUT WARNINGS*.
+Please ensure that you can build the documentation locally without producing any warnings.
+
+## Pull Requests
+We greatly appreciate PRs! To minimize back-and-forward communication, please ensure that your PR includes the following:
+
+1. **Code changes.** (the bug fix/new feature/updated documentation/etc.)
+1. **Unit tests.** If you are updating any code, you should add an appropraite unit test.
+   - If you are fixing a bug, make sure that there's a new unit test that catches the bug.
+     (I.e., there should be a new unit test that fails before your bug fix, but passes after your bug fix.
+     This ensures that we don't have any accidental regressions in the code base.)
+   - If you are adding a new feature, you should add unit tests for this new feature.
+1. **Documentation.** Any new objects/methods should have [appropriate docstrings](#docstrings).
+   - If you are adding a new object, **please ensure that it appears in the documentation.**
+     You may have to add the object to the appropriate file in [docs/source](https://github.com/lanzithinking/qepytorch/tree/main/docs/source).
+1. **Example notebooks.** Any major new functionality, tutorials, or examples should have an example jupyter notebook.
+   - If you are adding a new notebook, **please ensure that it appears in the documentation.**
+     You may have to add the object to the appropriate file in [docs/source](https://github.com/lanzithinking/qepytorch/tree/main/examples/).
+
+Before submitting a PR, ensure the following:
+1. **Code is proprerly formatted and linted.** Linting and formatting checking should happen automatically if you have followed the development installation instructions.
+   See [the formatting and linting](#formatting-and-linting) section for more info.
+1. **Unit tests pass.** See [the unit tests section](#unit-tests) for more info.
+1. **Documentation renders correctly without warnings.** [Build the documentation locally](#documentation) to ensure that your new class/docstrings are rendered correctly. Ensure that sphinx can build the documentation without warnings.
+
+
+## Issues
+
+We use GitHub issues to track public bugs. Please ensure your description is
+clear and has sufficient instructions to be able to reproduce the issue.
+
+We accept the following types of issues:
+- Bug reports
+- Requests for documentation/examples
+- Feature requests
+- Opportuntities to refactor code
+- Performance issues (speed, memory, etc.)
+
+Please refrain from using the issue tracker for questions or debugging personal code.
+Instead please use the [Q<sup style="font-size: 0.5em;">&#9428;</sup>PyTorch discussions forum](https://github.com/lanzithinking/qepytorch/discussions).
+
+## License
+
+By contributing to Q<sup style="font-size: 0.5em;">&#9428;</sup>PyTorch, you agree that your contributions will be licensed
+under the LICENSE file in the root directory of this source tree.

qpytorch-0.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Shiwei Lan
+
+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.