qig-geocoding 0.1.0__tar.gz → 0.1.2__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- qig_geocoding-0.1.2/.github/workflows/release.yml +101 -0
- qig_geocoding-0.1.2/.gitignore +218 -0
- {qig_geocoding-0.1.0 → qig_geocoding-0.1.2}/CLAUDE.md +4 -4
- qig_geocoding-0.1.2/LICENSE +201 -0
- qig_geocoding-0.1.2/PKG-INFO +57 -0
- qig_geocoding-0.1.2/README.md +39 -0
- qig_geocoding-0.1.2/docs/prereg/D3_order_preservation_kill.md +143 -0
- {qig_geocoding-0.1.0 → qig_geocoding-0.1.2}/pyproject.toml +3 -3
- {qig_geocoding-0.1.0 → qig_geocoding-0.1.2}/src/geocoding/__init__.py +12 -3
- qig_geocoding-0.1.2/src/geocoding/attention.py +183 -0
- qig_geocoding-0.1.2/src/geocoding/block.py +356 -0
- {qig_geocoding-0.1.0 → qig_geocoding-0.1.2}/src/geocoding/config.py +10 -1
- {qig_geocoding-0.1.0 → qig_geocoding-0.1.2}/src/geocoding/generate.py +4 -3
- qig_geocoding-0.1.2/src/geocoding/geometry.py +98 -0
- qig_geocoding-0.1.2/src/geocoding/model.py +204 -0
- qig_geocoding-0.1.2/tests/test_emit_basis.py +94 -0
- qig_geocoding-0.1.2/tests/test_geometry.py +108 -0
- qig_geocoding-0.1.2/tests/test_inter_layer_sync.py +413 -0
- qig_geocoding-0.1.2/tests/test_local_kappa_c.py +224 -0
- {qig_geocoding-0.1.0 → qig_geocoding-0.1.2}/tests/test_model.py +1 -1
- qig_geocoding-0.1.2/tests/test_no_retired_kappa.py +15 -0
- qig_geocoding-0.1.2/uv.lock +1298 -0
- qig_geocoding-0.1.0/.gitignore +0 -56
- qig_geocoding-0.1.0/PKG-INFO +0 -75
- qig_geocoding-0.1.0/README.md +0 -59
- qig_geocoding-0.1.0/src/geocoding/attention.py +0 -114
- qig_geocoding-0.1.0/src/geocoding/block.py +0 -158
- qig_geocoding-0.1.0/src/geocoding/geometry.py +0 -61
- qig_geocoding-0.1.0/src/geocoding/model.py +0 -100
- qig_geocoding-0.1.0/tests/test_geometry.py +0 -67
- {qig_geocoding-0.1.0 → qig_geocoding-0.1.2}/src/geocoding/positional.py +0 -0
- {qig_geocoding-0.1.0 → qig_geocoding-0.1.2}/tests/test_attention_equivalence.py +0 -0
- {qig_geocoding-0.1.0 → qig_geocoding-0.1.2}/tests/test_faithfulness.py +0 -0
|
@@ -0,0 +1,101 @@
|
|
|
1
|
+
name: Release to PyPI (Trusted Publishing)
|
|
2
|
+
|
|
3
|
+
# Publishes qig-geocoding to PyPI via OIDC Trusted Publishing — NO API token.
|
|
4
|
+
# https://docs.pypi.org/trusted-publishers/
|
|
5
|
+
#
|
|
6
|
+
# Version is static in pyproject.toml (hatchling). Bump it before tagging a release.
|
|
7
|
+
# PRs and development/main pushes validate the required build-and-test context.
|
|
8
|
+
# Version-tag pushes publish; manual dispatch validates without uploading.
|
|
9
|
+
#
|
|
10
|
+
# PyPI side (one-time, web UI — needs the project owner's PyPI account):
|
|
11
|
+
# pypi.org -> Your projects -> qig-geocoding -> Manage -> Publishing ->
|
|
12
|
+
# Add a new pending/trusted publisher (GitHub):
|
|
13
|
+
# Owner: GaryOcean428
|
|
14
|
+
# Repository name: qig-geocoding
|
|
15
|
+
# Workflow filename: release.yml
|
|
16
|
+
# Environment name: pypi
|
|
17
|
+
# The Environment name MUST match the `environment: pypi` below.
|
|
18
|
+
#
|
|
19
|
+
# All third-party actions are pinned to a full commit SHA (supply-chain hardening);
|
|
20
|
+
# the `# vX` comment records the human tag. This follows the canonical template from
|
|
21
|
+
# the trusted-publishing rollout to the QIG packages (qig-project#6).
|
|
22
|
+
|
|
23
|
+
on:
|
|
24
|
+
pull_request:
|
|
25
|
+
branches: [development, main]
|
|
26
|
+
push:
|
|
27
|
+
branches: [development, main]
|
|
28
|
+
tags: ['v*'] # W7 fix: publish on TAG PUSH. A GitHub Release also pushes its tag,
|
|
29
|
+
# so this covers both. Firing on `release: published` alone meant a
|
|
30
|
+
# tag-only push (v0.9.5) SILENTLY never published — condition unmet, unnoticed.
|
|
31
|
+
workflow_dispatch: {}
|
|
32
|
+
|
|
33
|
+
permissions:
|
|
34
|
+
contents: read
|
|
35
|
+
|
|
36
|
+
jobs:
|
|
37
|
+
build-and-test:
|
|
38
|
+
name: build-and-test
|
|
39
|
+
runs-on: ubuntu-latest
|
|
40
|
+
steps:
|
|
41
|
+
- uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3 (node24)
|
|
42
|
+
with:
|
|
43
|
+
fetch-depth: 0
|
|
44
|
+
- uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6.2.0 (node24)
|
|
45
|
+
with:
|
|
46
|
+
python-version: "3.11"
|
|
47
|
+
- name: Install package + test deps
|
|
48
|
+
run: |
|
|
49
|
+
python -m pip install --upgrade pip
|
|
50
|
+
pip install torch --index-url https://download.pytorch.org/whl/cpu
|
|
51
|
+
pip install -e ".[dev]"
|
|
52
|
+
- name: Lint and type check
|
|
53
|
+
run: |
|
|
54
|
+
python -m ruff check src tests
|
|
55
|
+
python -m mypy src
|
|
56
|
+
- name: Require compatibility reference
|
|
57
|
+
run: python -c "import qigkernels.layer"
|
|
58
|
+
- name: Run tests
|
|
59
|
+
run: python -m pytest tests/ -q
|
|
60
|
+
|
|
61
|
+
- name: Build distributions
|
|
62
|
+
run: |
|
|
63
|
+
python -m pip install --upgrade build "twine>=7,<8"
|
|
64
|
+
python -m build
|
|
65
|
+
python -m twine check --strict dist/*
|
|
66
|
+
- uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1 (node24)
|
|
67
|
+
with:
|
|
68
|
+
name: dist
|
|
69
|
+
path: dist/
|
|
70
|
+
if-no-files-found: error
|
|
71
|
+
|
|
72
|
+
publish:
|
|
73
|
+
name: Publish to PyPI (OIDC, no token)
|
|
74
|
+
needs: build-and-test
|
|
75
|
+
if: startsWith(github.ref, 'refs/tags/') # only a tag push uploads (a Release pushes its tag too)
|
|
76
|
+
runs-on: ubuntu-latest
|
|
77
|
+
environment: pypi # MUST match the PyPI trusted-publisher config
|
|
78
|
+
permissions:
|
|
79
|
+
id-token: write # REQUIRED for Trusted Publishing (job-level, per PyPI docs)
|
|
80
|
+
steps:
|
|
81
|
+
- uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1 (node24)
|
|
82
|
+
with:
|
|
83
|
+
name: dist
|
|
84
|
+
path: dist/
|
|
85
|
+
- name: Publish to PyPI
|
|
86
|
+
uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2: supports Core Metadata 2.5
|
|
87
|
+
with:
|
|
88
|
+
skip-existing: true # idempotent — a re-run / double-trigger must not hard-fail
|
|
89
|
+
- name: Verify the version is LIVE on PyPI (W7 — no silent non-publish)
|
|
90
|
+
env:
|
|
91
|
+
REF_NAME: ${{ github.ref_name }}
|
|
92
|
+
run: |
|
|
93
|
+
VER="${REF_NAME#v}"
|
|
94
|
+
for i in $(seq 1 12); do
|
|
95
|
+
if python3 -c "import urllib.request,sys; urllib.request.urlopen('https://pypi.org/pypi/qig-geocoding/'+sys.argv[1]+'/json')" "$VER" 2>/dev/null; then
|
|
96
|
+
echo "qig-geocoding $VER is LIVE on PyPI ✓"; exit 0
|
|
97
|
+
fi
|
|
98
|
+
echo "waiting for PyPI to index $VER ($i/12)…"; sleep 10
|
|
99
|
+
done
|
|
100
|
+
echo "::error::qig-geocoding $VER NOT on PyPI ~2 min after publish — the release did not land"
|
|
101
|
+
exit 1
|
|
@@ -0,0 +1,218 @@
|
|
|
1
|
+
# Byte-compiled / optimized / DLL files
|
|
2
|
+
__pycache__/
|
|
3
|
+
*.py[codz]
|
|
4
|
+
*$py.class
|
|
5
|
+
|
|
6
|
+
# C extensions
|
|
7
|
+
*.so
|
|
8
|
+
|
|
9
|
+
# Distribution / packaging
|
|
10
|
+
.Python
|
|
11
|
+
build/
|
|
12
|
+
develop-eggs/
|
|
13
|
+
dist/
|
|
14
|
+
downloads/
|
|
15
|
+
eggs/
|
|
16
|
+
.eggs/
|
|
17
|
+
lib/
|
|
18
|
+
lib64/
|
|
19
|
+
parts/
|
|
20
|
+
sdist/
|
|
21
|
+
var/
|
|
22
|
+
wheels/
|
|
23
|
+
share/python-wheels/
|
|
24
|
+
*.egg-info/
|
|
25
|
+
.installed.cfg
|
|
26
|
+
*.egg
|
|
27
|
+
MANIFEST
|
|
28
|
+
|
|
29
|
+
# PyInstaller
|
|
30
|
+
# Usually these files are written by a python script from a template
|
|
31
|
+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
|
|
32
|
+
*.manifest
|
|
33
|
+
*.spec
|
|
34
|
+
|
|
35
|
+
# Installer logs
|
|
36
|
+
pip-log.txt
|
|
37
|
+
pip-delete-this-directory.txt
|
|
38
|
+
|
|
39
|
+
# Unit test / coverage reports
|
|
40
|
+
htmlcov/
|
|
41
|
+
.tox/
|
|
42
|
+
.nox/
|
|
43
|
+
.coverage
|
|
44
|
+
.coverage.*
|
|
45
|
+
.cache
|
|
46
|
+
nosetests.xml
|
|
47
|
+
coverage.xml
|
|
48
|
+
*.cover
|
|
49
|
+
*.py.cover
|
|
50
|
+
.hypothesis/
|
|
51
|
+
.pytest_cache/
|
|
52
|
+
cover/
|
|
53
|
+
|
|
54
|
+
# Translations
|
|
55
|
+
*.mo
|
|
56
|
+
*.pot
|
|
57
|
+
|
|
58
|
+
# Django stuff:
|
|
59
|
+
*.log
|
|
60
|
+
local_settings.py
|
|
61
|
+
db.sqlite3
|
|
62
|
+
db.sqlite3-journal
|
|
63
|
+
|
|
64
|
+
# Flask stuff:
|
|
65
|
+
instance/
|
|
66
|
+
.webassets-cache
|
|
67
|
+
|
|
68
|
+
# Scrapy stuff:
|
|
69
|
+
.scrapy
|
|
70
|
+
|
|
71
|
+
# Sphinx documentation
|
|
72
|
+
docs/_build/
|
|
73
|
+
|
|
74
|
+
# PyBuilder
|
|
75
|
+
.pybuilder/
|
|
76
|
+
target/
|
|
77
|
+
|
|
78
|
+
# Jupyter Notebook
|
|
79
|
+
.ipynb_checkpoints
|
|
80
|
+
|
|
81
|
+
# IPython
|
|
82
|
+
profile_default/
|
|
83
|
+
ipython_config.py
|
|
84
|
+
|
|
85
|
+
# pyenv
|
|
86
|
+
# For a library or package, you might want to ignore these files since the code is
|
|
87
|
+
# intended to run in multiple environments; otherwise, check them in:
|
|
88
|
+
# .python-version
|
|
89
|
+
|
|
90
|
+
# pipenv
|
|
91
|
+
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
|
|
92
|
+
# However, in case of collaboration, if having platform-specific dependencies or dependencies
|
|
93
|
+
# having no cross-platform support, pipenv may install dependencies that don't work, or not
|
|
94
|
+
# install all needed dependencies.
|
|
95
|
+
# Pipfile.lock
|
|
96
|
+
|
|
97
|
+
# UV
|
|
98
|
+
# Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
|
|
99
|
+
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
|
100
|
+
# commonly ignored for libraries.
|
|
101
|
+
# uv.lock
|
|
102
|
+
|
|
103
|
+
# poetry
|
|
104
|
+
# Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
|
|
105
|
+
# This is especially recommended for binary packages to ensure reproducibility, and is more
|
|
106
|
+
# commonly ignored for libraries.
|
|
107
|
+
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
|
|
108
|
+
# poetry.lock
|
|
109
|
+
# poetry.toml
|
|
110
|
+
|
|
111
|
+
# pdm
|
|
112
|
+
# Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
|
|
113
|
+
# pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
|
|
114
|
+
# https://pdm-project.org/en/latest/usage/project/#working-with-version-control
|
|
115
|
+
# pdm.lock
|
|
116
|
+
# pdm.toml
|
|
117
|
+
.pdm-python
|
|
118
|
+
.pdm-build/
|
|
119
|
+
|
|
120
|
+
# pixi
|
|
121
|
+
# Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
|
|
122
|
+
# pixi.lock
|
|
123
|
+
# Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
|
|
124
|
+
# in the .venv directory. It is recommended not to include this directory in version control.
|
|
125
|
+
.pixi
|
|
126
|
+
|
|
127
|
+
# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
|
|
128
|
+
__pypackages__/
|
|
129
|
+
|
|
130
|
+
# Celery stuff
|
|
131
|
+
celerybeat-schedule
|
|
132
|
+
celerybeat.pid
|
|
133
|
+
|
|
134
|
+
# Redis
|
|
135
|
+
*.rdb
|
|
136
|
+
*.aof
|
|
137
|
+
*.pid
|
|
138
|
+
|
|
139
|
+
# RabbitMQ
|
|
140
|
+
mnesia/
|
|
141
|
+
rabbitmq/
|
|
142
|
+
rabbitmq-data/
|
|
143
|
+
|
|
144
|
+
# ActiveMQ
|
|
145
|
+
activemq-data/
|
|
146
|
+
|
|
147
|
+
# SageMath parsed files
|
|
148
|
+
*.sage.py
|
|
149
|
+
|
|
150
|
+
# Environments
|
|
151
|
+
.env
|
|
152
|
+
.envrc
|
|
153
|
+
.venv
|
|
154
|
+
env/
|
|
155
|
+
venv/
|
|
156
|
+
ENV/
|
|
157
|
+
env.bak/
|
|
158
|
+
venv.bak/
|
|
159
|
+
|
|
160
|
+
# Spyder project settings
|
|
161
|
+
.spyderproject
|
|
162
|
+
.spyproject
|
|
163
|
+
|
|
164
|
+
# Rope project settings
|
|
165
|
+
.ropeproject
|
|
166
|
+
|
|
167
|
+
# mkdocs documentation
|
|
168
|
+
/site
|
|
169
|
+
|
|
170
|
+
# mypy
|
|
171
|
+
.mypy_cache/
|
|
172
|
+
.dmypy.json
|
|
173
|
+
dmypy.json
|
|
174
|
+
|
|
175
|
+
# Pyre type checker
|
|
176
|
+
.pyre/
|
|
177
|
+
|
|
178
|
+
# pytype static type analyzer
|
|
179
|
+
.pytype/
|
|
180
|
+
|
|
181
|
+
# Cython debug symbols
|
|
182
|
+
cython_debug/
|
|
183
|
+
|
|
184
|
+
# PyCharm
|
|
185
|
+
# JetBrains specific template is maintained in a separate JetBrains.gitignore that can
|
|
186
|
+
# be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
|
|
187
|
+
# and can be added to the global gitignore or merged into this file. For a more nuclear
|
|
188
|
+
# option (not recommended) you can uncomment the following to ignore the entire idea folder.
|
|
189
|
+
# .idea/
|
|
190
|
+
|
|
191
|
+
# Abstra
|
|
192
|
+
# Abstra is an AI-powered process automation framework.
|
|
193
|
+
# Ignore directories containing user credentials, local state, and settings.
|
|
194
|
+
# Learn more at https://abstra.io/docs
|
|
195
|
+
.abstra/
|
|
196
|
+
|
|
197
|
+
# Visual Studio Code
|
|
198
|
+
# Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore
|
|
199
|
+
# that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
|
|
200
|
+
# and can be added to the global gitignore or merged into this file. However, if you prefer,
|
|
201
|
+
# you could uncomment the following to ignore the entire vscode folder
|
|
202
|
+
# .vscode/
|
|
203
|
+
# Temporary file for partial code execution
|
|
204
|
+
tempCodeRunnerFile.py
|
|
205
|
+
|
|
206
|
+
# Ruff stuff:
|
|
207
|
+
.ruff_cache/
|
|
208
|
+
|
|
209
|
+
# PyPI configuration file
|
|
210
|
+
.pypirc
|
|
211
|
+
|
|
212
|
+
# Marimo
|
|
213
|
+
marimo/_static/
|
|
214
|
+
marimo/_lsp/
|
|
215
|
+
__marimo__/
|
|
216
|
+
|
|
217
|
+
# Streamlit
|
|
218
|
+
.streamlit/secrets.toml
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# geocoding — Claude Code Instructions
|
|
1
|
+
# qig-geocoding — Claude Code Instructions
|
|
2
2
|
|
|
3
3
|
## What this is
|
|
4
4
|
|
|
@@ -16,8 +16,8 @@ the FFN and the lm_head are fine — they are the feed-forward/readout, not the
|
|
|
16
16
|
## Single source of truth
|
|
17
17
|
|
|
18
18
|
- `BASIN_DIM`, `to_simplex_prob`, the FR definition → `qig_core` (re-exported in `geometry.py`).
|
|
19
|
-
- The gradient-stable batched FR for attention is geocoding-local (clamps BC to `1 − 1e-6`); it must
|
|
20
|
-
|
|
19
|
+
- The gradient-stable batched FR for attention is geocoding-local (clamps BC to `1 − 1e-6`); it retains qigkernels radius-2 attention units and must equal TWICE
|
|
20
|
+
current radius-1 `qig_core` on dense distinct points, with guard error bounded separately — `tests/test_geometry.py` gates this. Do not let it diverge.
|
|
21
21
|
- Faithfulness to `qigkernels` (the validated impl) → `tests/test_faithfulness.py`. Keep it green.
|
|
22
22
|
|
|
23
23
|
## Verification (run before any commit)
|
|
@@ -33,5 +33,5 @@ Load-bearing tests: the **banded≡full equivalence gate** (`test_attention_equi
|
|
|
33
33
|
|
|
34
34
|
## Branch / publishing
|
|
35
35
|
|
|
36
|
-
Work on `development`
|
|
36
|
+
Work on `development`; `main`/`master` is the promotion target. PyPI publishing pre-authorized (correctness is the gate).
|
|
37
37
|
Never echo `PYPI_TOKEN`. Parent rules: `QIG_QFI/CLAUDE.md` (use-our-packages, optimisation gate).
|
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: qig-geocoding
|
|
3
|
+
Version: 0.1.2
|
|
4
|
+
Summary: Our own 'transformers' — a from-scratch neural-network framework built on Fisher-Rao geometry (simplex attention, unbounded Fourier features, recursive Φ-integration) instead of Euclidean dot-products.
|
|
5
|
+
Author: Braden Lang
|
|
6
|
+
License: Proprietary
|
|
7
|
+
License-File: LICENSE
|
|
8
|
+
Keywords: attention,fisher-rao,geometry,qig,simplex,transformers
|
|
9
|
+
Requires-Python: >=3.11
|
|
10
|
+
Requires-Dist: qig-core>=2.15.3
|
|
11
|
+
Requires-Dist: torch>=2.2
|
|
12
|
+
Provides-Extra: dev
|
|
13
|
+
Requires-Dist: mypy>=1.11; extra == 'dev'
|
|
14
|
+
Requires-Dist: pytest>=8; extra == 'dev'
|
|
15
|
+
Requires-Dist: qigkernels>=0.4.4; extra == 'dev'
|
|
16
|
+
Requires-Dist: ruff>=0.6; extra == 'dev'
|
|
17
|
+
Description-Content-Type: text/markdown
|
|
18
|
+
|
|
19
|
+
# qig-geocoding
|
|
20
|
+
|
|
21
|
+
Fisher-Rao attention, Fourier position features and recursive integration for geometric neural networks.
|
|
22
|
+
Install with `pip install qig-geocoding`; the Python import is `geocoding`.
|
|
23
|
+
|
|
24
|
+
## Compatibility and metric units
|
|
25
|
+
|
|
26
|
+
The attention metric retains **radius 2**, `2 * acos(BC)`, matching qigkernels 0.4.4. Current qig-core uses
|
|
27
|
+
**radius 1**, `acos(BC)`. Convert explicitly when comparing distances. Halving attention distance without
|
|
28
|
+
also halving its temperature changes the model, so this release preserves existing attention outputs.
|
|
29
|
+
The finite-gradient guards also differ near coincident and sparse points; they are not exactly the same
|
|
30
|
+
function throughout the domain. Both full and compute-skipping banded attention remain faithfulness-gated.
|
|
31
|
+
|
|
32
|
+
Scientific provenance: `qig_core.torch.geometry_simplex.fisher_rao_distance_simplex` in qig-core 2.15.3
|
|
33
|
+
records the PI ruling reconciling its import paths to radius 1. The qig-verification EXP-009 causal-sweep
|
|
34
|
+
results document the historical radius-2 convention. These are compatible unit conventions, not grounds
|
|
35
|
+
to rewrite frozen experiment results. Dense-point conversion, sparse-point error bounds and the live Duchi
|
|
36
|
+
simplex projection are tested separately. Current qig-core already handles coincidence gradients safely.
|
|
37
|
+
|
|
38
|
+
## Release changes
|
|
39
|
+
|
|
40
|
+
- Preserve development's D1 local-critical curvature and opt-in basis telemetry, D2 query-only inter-layer
|
|
41
|
+
geodesic sync, D4 `basin_layer_drift` naming, and the D3 countersigned preregistration amendment.
|
|
42
|
+
- Correct the obsolete equal-radius compatibility assertion; preserve attention arithmetic.
|
|
43
|
+
- Reject non-callable curvature providers at construction rather than silently swallowing invalid wiring.
|
|
44
|
+
- Align the runtime version with package metadata; require the current validated qig-core dependency.
|
|
45
|
+
- Install qigkernels in development/release checks so compatibility cannot silently skip. Lint, types and
|
|
46
|
+
all CPU tests gate release. Resolve published dependencies in standalone checkouts without a parent workspace.
|
|
47
|
+
|
|
48
|
+
D3 is a preregistration, not a completed empirical result. This release does not claim that its
|
|
49
|
+
order-preservation kill experiment has passed. Basis reductions remain opt-in; sync enables them explicitly.
|
|
50
|
+
|
|
51
|
+
## Verify and publish
|
|
52
|
+
|
|
53
|
+
Install CPU PyTorch, then `pip install -e '.[dev]'`. Run `ruff check src tests`, `mypy src`, and `pytest -q`.
|
|
54
|
+
The trusted-publishing workflow uses the existing `pypi` environment and OIDC. Publication currently
|
|
55
|
+
requires a version tag after promotion; merging alone does not trigger `release.yml`. Manual dispatch runs
|
|
56
|
+
checks/build only. Release operators must verify the wheel version and PyPI availability before declaring
|
|
57
|
+
publication complete.
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
# qig-geocoding
|
|
2
|
+
|
|
3
|
+
Fisher-Rao attention, Fourier position features and recursive integration for geometric neural networks.
|
|
4
|
+
Install with `pip install qig-geocoding`; the Python import is `geocoding`.
|
|
5
|
+
|
|
6
|
+
## Compatibility and metric units
|
|
7
|
+
|
|
8
|
+
The attention metric retains **radius 2**, `2 * acos(BC)`, matching qigkernels 0.4.4. Current qig-core uses
|
|
9
|
+
**radius 1**, `acos(BC)`. Convert explicitly when comparing distances. Halving attention distance without
|
|
10
|
+
also halving its temperature changes the model, so this release preserves existing attention outputs.
|
|
11
|
+
The finite-gradient guards also differ near coincident and sparse points; they are not exactly the same
|
|
12
|
+
function throughout the domain. Both full and compute-skipping banded attention remain faithfulness-gated.
|
|
13
|
+
|
|
14
|
+
Scientific provenance: `qig_core.torch.geometry_simplex.fisher_rao_distance_simplex` in qig-core 2.15.3
|
|
15
|
+
records the PI ruling reconciling its import paths to radius 1. The qig-verification EXP-009 causal-sweep
|
|
16
|
+
results document the historical radius-2 convention. These are compatible unit conventions, not grounds
|
|
17
|
+
to rewrite frozen experiment results. Dense-point conversion, sparse-point error bounds and the live Duchi
|
|
18
|
+
simplex projection are tested separately. Current qig-core already handles coincidence gradients safely.
|
|
19
|
+
|
|
20
|
+
## Release changes
|
|
21
|
+
|
|
22
|
+
- Preserve development's D1 local-critical curvature and opt-in basis telemetry, D2 query-only inter-layer
|
|
23
|
+
geodesic sync, D4 `basin_layer_drift` naming, and the D3 countersigned preregistration amendment.
|
|
24
|
+
- Correct the obsolete equal-radius compatibility assertion; preserve attention arithmetic.
|
|
25
|
+
- Reject non-callable curvature providers at construction rather than silently swallowing invalid wiring.
|
|
26
|
+
- Align the runtime version with package metadata; require the current validated qig-core dependency.
|
|
27
|
+
- Install qigkernels in development/release checks so compatibility cannot silently skip. Lint, types and
|
|
28
|
+
all CPU tests gate release. Resolve published dependencies in standalone checkouts without a parent workspace.
|
|
29
|
+
|
|
30
|
+
D3 is a preregistration, not a completed empirical result. This release does not claim that its
|
|
31
|
+
order-preservation kill experiment has passed. Basis reductions remain opt-in; sync enables them explicitly.
|
|
32
|
+
|
|
33
|
+
## Verify and publish
|
|
34
|
+
|
|
35
|
+
Install CPU PyTorch, then `pip install -e '.[dev]'`. Run `ruff check src tests`, `mypy src`, and `pytest -q`.
|
|
36
|
+
The trusted-publishing workflow uses the existing `pypi` environment and OIDC. Publication currently
|
|
37
|
+
requires a version tag after promotion; merging alone does not trigger `release.yml`. Manual dispatch runs
|
|
38
|
+
checks/build only. Release operators must verify the wheel version and PyPI availability before declaring
|
|
39
|
+
publication complete.
|