Datasets:
docs: dataset card with nuScenes attribution
Browse files
README.md
CHANGED
|
@@ -37,7 +37,7 @@ thumbs.tar -> repo root <- fetch this one
|
|
| 37 |
|---|---|---|
|
| 38 |
| `artifacts/vectors.npy` | 21 MB | 6858 × 768 float32, L2-normalised SigLIP2 image embeddings |
|
| 39 |
| `artifacts/caption_vectors.npy` | 10.5 MB | 6858 × 384 float32, MiniLM embeddings of generated captions |
|
| 40 |
-
| `thumbs.tar` |
|
| 41 |
| `*.jpg` | 261 MB | the same thumbnails loose, 640×360, downscaled from 1600×900 |
|
| 42 |
|
| 43 |
**640×360 as of 2026-08-06, regenerated from the nuScenes source.** Thumbnail width is one constant,
|
|
@@ -74,11 +74,16 @@ unauthenticated caller for. It returned 429 at roughly the 490th file on a CI ru
|
|
| 74 |
minutes in, leaving a half-populated directory. One request cannot half-arrive.
|
| 75 |
|
| 76 |
The tarball is uncompressed deliberately: measured over 200 of these thumbnails, gzip -6 saves 2.1%,
|
| 77 |
-
because JPEG is already DCT-compressed. It is larger than the sum of its contents
|
| 78 |
-
261
|
| 79 |
-
|
| 80 |
-
|
| 81 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 82 |
|
| 83 |
Row order in both matrices matches `frames.jsonl` in the application repo exactly, and the
|
| 84 |
application re-checks that on load — a misaligned row would mean confident answers about the wrong
|
|
|
|
| 37 |
|---|---|---|
|
| 38 |
| `artifacts/vectors.npy` | 21 MB | 6858 × 768 float32, L2-normalised SigLIP2 image embeddings |
|
| 39 |
| `artifacts/caption_vectors.npy` | 10.5 MB | 6858 × 384 float32, MiniLM embeddings of generated captions |
|
| 40 |
+
| `thumbs.tar` | 274 MB | all 6,858 thumbnails, flat and uncompressed, faces/plates redacted |
|
| 41 |
| `*.jpg` | 261 MB | the same thumbnails loose, 640×360, downscaled from 1600×900 |
|
| 42 |
|
| 43 |
**640×360 as of 2026-08-06, regenerated from the nuScenes source.** Thumbnail width is one constant,
|
|
|
|
| 74 |
minutes in, leaving a half-populated directory. One request cannot half-arrive.
|
| 75 |
|
| 76 |
The tarball is uncompressed deliberately: measured over 200 of these thumbnails, gzip -6 saves 2.1%,
|
| 77 |
+
because JPEG is already DCT-compressed. It is larger than the sum of its contents — **274 MB against
|
| 78 |
+
261, an overhead of 12.3 MB or 4.7%** — because every member carries header blocks and is padded to a
|
| 79 |
+
512-byte boundary. Measured over this archive that is **1,790 bytes per member**: Python's `tarfile`
|
| 80 |
+
writes PAX by default, so each file gets an extended-header pair on top of the ustar header, plus
|
| 81 |
+
alignment padding.
|
| 82 |
+
|
| 83 |
+
**That cost is fixed per member, so it matters in inverse proportion to file size** — which is why
|
| 84 |
+
this paragraph used to argue harder. The same ~12 MB was **17%** of the 320×180 set (members averaged
|
| 85 |
+
~10 KB) and is **4.7%** of this one (members average 37 KB). Nothing about the packing changed; the
|
| 86 |
+
files got bigger.
|
| 87 |
|
| 88 |
Row order in both matrices matches `frames.jsonl` in the application repo exactly, and the
|
| 89 |
application re-checks that on load — a misaligned row would mean confident answers about the wrong
|