pixelmap-multiview-python 0.1.1__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.
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/CHANGELOG.md +15 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/Cargo.lock +5 -5
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/Cargo.toml +2 -2
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/PKG-INFO +22 -11
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/README.md +21 -10
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/python/pixelmap_multiview/__init__.py +3 -2
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/python/pixelmap_multiview/_events.py +3 -3
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/python/pixelmap_multiview/_io.py +6 -4
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/.github/workflows/ci.yml +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/.github/workflows/release.yml +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/.gitignore +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/LICENSE +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/pyproject.toml +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/python/pixelmap_multiview/_errors.py +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/python/pixelmap_multiview/_model.py +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/python/pixelmap_multiview/_pixelmap_multiview.pyi +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/python/pixelmap_multiview/py.typed +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/src/convert.rs +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/src/errors.rs +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/src/events.rs +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/src/job.rs +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/src/lib.rs +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/src/model.rs +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/tests/conftest.py +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/tests/test_events.py +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/tests/test_export.py +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/tests/test_inputs.py +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/tests/test_job.py +0 -0
- {pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/tests/test_run.py +0 -0
|
@@ -4,6 +4,21 @@ All notable changes to this package are documented here. The format follows
|
|
|
4
4
|
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the package follows
|
|
5
5
|
[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
6
6
|
|
|
7
|
+
## 0.1.2 - 2026-11-17
|
|
8
|
+
|
|
9
|
+
### Changed
|
|
10
|
+
|
|
11
|
+
- Built against `pixelmap_multiview` 0.1.2 and pixelmap 0.3.1. Mapping each pair of
|
|
12
|
+
photos takes about 40% fewer region comparisons, so `reconstruct` is faster: on
|
|
13
|
+
4128x3096 photos one pair at `high` went from 5.9 s to 4.3 s.
|
|
14
|
+
- **The same photos, quality and `seed` no longer give the model 0.1.1 gave.** Runs are
|
|
15
|
+
still deterministic, but the solver reaches a different, equally good correspondence.
|
|
16
|
+
|
|
17
|
+
### Fixed
|
|
18
|
+
|
|
19
|
+
- Gaps in the depth maps and the mesh. Some pairs' correspondence had straight unmapped
|
|
20
|
+
bands, one grid cell wide, running through it; pixelmap 0.3.1 no longer leaves them.
|
|
21
|
+
|
|
7
22
|
## 0.1.1 - 2026-10-04
|
|
8
23
|
|
|
9
24
|
### Added
|
|
@@ -263,16 +263,16 @@ checksum = "57c0d7b74b563b49d38dae00a0c37d4d6de9b432382b2892f0574ddcae73fd0a"
|
|
|
263
263
|
|
|
264
264
|
[[package]]
|
|
265
265
|
name = "pixelmap"
|
|
266
|
-
version = "0.3.
|
|
266
|
+
version = "0.3.1"
|
|
267
267
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
268
|
-
checksum = "
|
|
268
|
+
checksum = "68c5a7639712187ae7cc9671dcb9b02247971d965c8bef954b2e0b4fc580967c"
|
|
269
269
|
dependencies = [
|
|
270
270
|
"rayon",
|
|
271
271
|
]
|
|
272
272
|
|
|
273
273
|
[[package]]
|
|
274
274
|
name = "pixelmap-multiview-py"
|
|
275
|
-
version = "0.1.
|
|
275
|
+
version = "0.1.2"
|
|
276
276
|
dependencies = [
|
|
277
277
|
"numpy",
|
|
278
278
|
"pixelmap_multiview",
|
|
@@ -282,9 +282,9 @@ dependencies = [
|
|
|
282
282
|
|
|
283
283
|
[[package]]
|
|
284
284
|
name = "pixelmap_multiview"
|
|
285
|
-
version = "0.1.
|
|
285
|
+
version = "0.1.2"
|
|
286
286
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
|
287
|
-
checksum = "
|
|
287
|
+
checksum = "32b6d01388114dc917063953f308c86e5652c5d27f2607125930c7205e5a7491"
|
|
288
288
|
dependencies = [
|
|
289
289
|
"nalgebra",
|
|
290
290
|
"pixelmap",
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
[package]
|
|
2
2
|
name = "pixelmap-multiview-py"
|
|
3
|
-
version = "0.1.
|
|
3
|
+
version = "0.1.2"
|
|
4
4
|
edition = "2021"
|
|
5
5
|
rust-version = "1.83"
|
|
6
6
|
description = "Python bindings for the pixelmap_multiview crate"
|
|
@@ -18,7 +18,7 @@ crate-type = ["cdylib"]
|
|
|
18
18
|
[dependencies]
|
|
19
19
|
# `pixelmap` and `nalgebra` are reached through this crate's re-exports, so they are
|
|
20
20
|
# always the versions it was built against.
|
|
21
|
-
pixelmap_multiview = "0.1.
|
|
21
|
+
pixelmap_multiview = "0.1.2"
|
|
22
22
|
pyo3 = { version = "0.29", features = ["abi3-py39", "extension-module"] }
|
|
23
23
|
numpy = "0.29"
|
|
24
24
|
# The crate does no I/O, so encoding the texture atlas is ours to do.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: pixelmap-multiview-python
|
|
3
|
-
Version: 0.1.
|
|
3
|
+
Version: 0.1.2
|
|
4
4
|
Classifier: Development Status :: 4 - Beta
|
|
5
5
|
Classifier: Intended Audience :: Science/Research
|
|
6
6
|
Classifier: License :: OSI Approved :: MIT License
|
|
@@ -173,20 +173,31 @@ For a good capture:
|
|
|
173
173
|
- Let neighbouring photos overlap generously.
|
|
174
174
|
- Keep one camera at one zoom setting throughout.
|
|
175
175
|
|
|
176
|
-
##
|
|
176
|
+
## Time complexity
|
|
177
177
|
|
|
178
|
-
Mapping the pairs dominates: N photos take N(N−1)/2 pixelmap runs
|
|
179
|
-
|
|
178
|
+
Mapping the pairs dominates: N photos take N(N−1)/2 pixelmap runs, one after another, so
|
|
179
|
+
the time grows with the square of the number of photos. Four photos make 6 pairs; the 23
|
|
180
|
+
photos of the statue make 253. One pair of 4:3 photos takes, by the long side of the
|
|
181
|
+
photos:
|
|
180
182
|
|
|
181
183
|
| Quality | 800 px | 1200 px | 1800 px |
|
|
182
184
|
|---------|--------|---------|---------|
|
|
183
|
-
| low | 0.
|
|
184
|
-
| medium |
|
|
185
|
-
| high |
|
|
186
|
-
|
|
187
|
-
|
|
188
|
-
|
|
189
|
-
|
|
185
|
+
| low | 0.22 s | 0.23 s | 0.22 s |
|
|
186
|
+
| medium | 0.98 s | 0.96 s | 0.97 s |
|
|
187
|
+
| high | 2.16 s | 2.90 s | 4.08 s |
|
|
188
|
+
|
|
189
|
+
So the statue at `medium` spends about four minutes mapping pairs. These are medians of
|
|
190
|
+
three runs of `pixelmap-multiview --time-pair` from `pixelmap_multiview` 0.1.2, on a
|
|
191
|
+
six-core Intel Core i7-9750H laptop. Expect other machines to be proportionally faster or
|
|
192
|
+
slower.
|
|
193
|
+
|
|
194
|
+
pixelmap scales both photos down to a fixed working width before matching them: 400 px
|
|
195
|
+
for `low`, 800 px for `medium` and 1600 px for `high`. It never scales them up, so at
|
|
196
|
+
`low` and `medium` the size of the input barely changes the time. `high` only works at its
|
|
197
|
+
full width with photos at least 1600 px across, which is why it slows down as they grow;
|
|
198
|
+
at the 1200 px `load_photos` gives by default it works at 1200 px. Larger photos also give
|
|
199
|
+
more precise geometry after matching. Runs are deterministic: the same photos, quality and
|
|
200
|
+
`seed` give the same model.
|
|
190
201
|
|
|
191
202
|
## Development
|
|
192
203
|
|
|
@@ -145,20 +145,31 @@ For a good capture:
|
|
|
145
145
|
- Let neighbouring photos overlap generously.
|
|
146
146
|
- Keep one camera at one zoom setting throughout.
|
|
147
147
|
|
|
148
|
-
##
|
|
148
|
+
## Time complexity
|
|
149
149
|
|
|
150
|
-
Mapping the pairs dominates: N photos take N(N−1)/2 pixelmap runs
|
|
151
|
-
|
|
150
|
+
Mapping the pairs dominates: N photos take N(N−1)/2 pixelmap runs, one after another, so
|
|
151
|
+
the time grows with the square of the number of photos. Four photos make 6 pairs; the 23
|
|
152
|
+
photos of the statue make 253. One pair of 4:3 photos takes, by the long side of the
|
|
153
|
+
photos:
|
|
152
154
|
|
|
153
155
|
| Quality | 800 px | 1200 px | 1800 px |
|
|
154
156
|
|---------|--------|---------|---------|
|
|
155
|
-
| low | 0.
|
|
156
|
-
| medium |
|
|
157
|
-
| high |
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
157
|
+
| low | 0.22 s | 0.23 s | 0.22 s |
|
|
158
|
+
| medium | 0.98 s | 0.96 s | 0.97 s |
|
|
159
|
+
| high | 2.16 s | 2.90 s | 4.08 s |
|
|
160
|
+
|
|
161
|
+
So the statue at `medium` spends about four minutes mapping pairs. These are medians of
|
|
162
|
+
three runs of `pixelmap-multiview --time-pair` from `pixelmap_multiview` 0.1.2, on a
|
|
163
|
+
six-core Intel Core i7-9750H laptop. Expect other machines to be proportionally faster or
|
|
164
|
+
slower.
|
|
165
|
+
|
|
166
|
+
pixelmap scales both photos down to a fixed working width before matching them: 400 px
|
|
167
|
+
for `low`, 800 px for `medium` and 1600 px for `high`. It never scales them up, so at
|
|
168
|
+
`low` and `medium` the size of the input barely changes the time. `high` only works at its
|
|
169
|
+
full width with photos at least 1600 px across, which is why it slows down as they grow;
|
|
170
|
+
at the 1200 px `load_photos` gives by default it works at 1200 px. Larger photos also give
|
|
171
|
+
more precise geometry after matching. Runs are deterministic: the same photos, quality and
|
|
172
|
+
`seed` give the same model.
|
|
162
173
|
|
|
163
174
|
## Development
|
|
164
175
|
|
|
@@ -105,8 +105,9 @@ STAGES: list[tuple[str, str]] = _pixelmap_multiview.STAGES
|
|
|
105
105
|
class Quality(str, enum.Enum):
|
|
106
106
|
"""How much work pixelmap puts into each pair of photos.
|
|
107
107
|
|
|
108
|
-
|
|
109
|
-
0.
|
|
108
|
+
Mapping the pairs takes most of a run's time, since there are N(N-1)/2 of them. One
|
|
109
|
+
pair of 1200 px photos takes roughly 0.2 s at ``LOW``, 1 s at ``MEDIUM`` and 2.9 s at
|
|
110
|
+
``HIGH`` on a six-core laptop.
|
|
110
111
|
"""
|
|
111
112
|
|
|
112
113
|
LOW = "low"
|
|
@@ -32,9 +32,9 @@ class Event:
|
|
|
32
32
|
Attributes:
|
|
33
33
|
stage: The stage it came from, one of the names in :data:`STAGES`.
|
|
34
34
|
progress: How far through the whole run this is, ``0.0``-``1.0``, with each stage
|
|
35
|
-
weighted by
|
|
36
|
-
progress — a log line or a dropped view — which a progress bar should
|
|
37
|
-
rather than move backwards for.
|
|
35
|
+
weighted by how long it typically takes. ``None`` for events that say nothing
|
|
36
|
+
about progress — a log line or a dropped view — which a progress bar should
|
|
37
|
+
ignore rather than move backwards for.
|
|
38
38
|
message: The event as one line for a log.
|
|
39
39
|
"""
|
|
40
40
|
|
{pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/python/pixelmap_multiview/_io.py
RENAMED
|
@@ -22,10 +22,12 @@ def load_photos(
|
|
|
22
22
|
"""Reads photos for :func:`reconstruct`, with the focal length EXIF records.
|
|
23
23
|
|
|
24
24
|
Each photo is turned upright as its EXIF orientation says, converted to RGB, and
|
|
25
|
-
scaled down so that its longer side is at most ``max_size`` pixels.
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
25
|
+
scaled down so that its longer side is at most ``max_size`` pixels. Smaller photos
|
|
26
|
+
take less memory, but the geometry that follows is less precise, so ``max_size``
|
|
27
|
+
trades memory against detail. Matching time stays about the same at ``"low"`` and
|
|
28
|
+
``"medium"``, because pixelmap scales photos down to a fixed working width. ``"high"``
|
|
29
|
+
works at up to 1600 px and never scales up, so below that, smaller photos make it
|
|
30
|
+
faster. 1200 is what the crate's measurements were taken at.
|
|
29
31
|
|
|
30
32
|
Requires Pillow: ``pip install pixelmap-multiview-python[images]``.
|
|
31
33
|
|
{pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/.github/workflows/ci.yml
RENAMED
|
File without changes
|
{pixelmap_multiview_python-0.1.1 → pixelmap_multiview_python-0.1.2}/.github/workflows/release.yml
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|