xiaohaox commited on
Commit
49831e0
·
verified ·
1 Parent(s): 391ca29

Upload README.md with huggingface_hub

Browse files
Files changed (1) hide show
  1. README.md +234 -0
README.md ADDED
@@ -0,0 +1,234 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ pretty_name: "MD-3K: MultiDepth-3K Benchmark"
3
+ language:
4
+ - en
5
+ license: other
6
+ size_categories:
7
+ - 1K<n<10K
8
+ task_categories:
9
+ - depth-estimation
10
+ tags:
11
+ - depth-estimation
12
+ - monocular-depth-estimation
13
+ - ordinal-depth
14
+ - spatial-reasoning
15
+ - transparent-scenes
16
+ - glass
17
+ - multi-layer-depth
18
+ - geometric-ambiguity
19
+ - eccv-2026
20
+ ---
21
+
22
+ # MD-3K: MultiDepth-3K Benchmark
23
+
24
+ MD-3K is a real-world diagnostic benchmark for probing **geometric ambiguity** in monocular depth estimation. It focuses on transparent scenes where a single camera ray can contain two visually present and geometrically valid surfaces: a transparent foreground surface and the visible background behind it. Since a standard monocular depth model returns one scalar depth per pixel, MD-3K evaluates which valid depth layer a model reports and whether paired hypotheses can jointly satisfy both layer-specific ordinal relations.
25
+
26
+ This dataset accompanies the ECCV 2026 paper:
27
+
28
+ > **One Scene, Two Depths: Probing Geometric Ambiguity in Monocular Foundation Models**
29
+ > Xiaohao Xu, Feng Xue, Xiang Li, Haowei Li, Shusheng Yang, Tianyi Zhang, Matthew Johnson-Roberson, Xiaonan Huang.
30
+
31
+ Code repository: `https://github.com/Xiaohao-Xu/Ambiguity-in-Space`
32
+
33
+ ## Release files
34
+
35
+ The canonical archive in this release is:
36
+
37
+ ```text
38
+ MD-3K.zip
39
+ ```
40
+
41
+ The expected SHA256 checksum is:
42
+
43
+ ```text
44
+ 3e9627d3aca6886a4449fd149b7ec791d13943d423fc5ee14f611c986bdecd29 MD-3K.zip
45
+ ```
46
+
47
+ After extraction, the dataset should follow this layout:
48
+
49
+ ```text
50
+ MD-3K/
51
+ ├── images/ # RGB images
52
+ ├── masks/ # ambiguous/transparent-region masks
53
+ └── annotations.json # sparse point-pair ordinal annotations
54
+ ```
55
+
56
+ ## Dataset summary
57
+
58
+ MD-3K contains:
59
+
60
+ - 3,161 RGB images curated for transparent-scene ambiguity analysis.
61
+ - Ambiguous-region masks.
62
+ - Sparse point-pair annotations in ambiguous regions.
63
+ - Two layer-specific ordinal targets:
64
+ - **Layer 1:** transparent foreground surface.
65
+ - **Layer 2:** visible background behind the transparent surface.
66
+ - Same/Reverse subset structure:
67
+ - **Same:** the two valid layers induce the same ordinal relation.
68
+ - **Reverse:** the two valid layers induce conflicting ordinal relations.
69
+
70
+ The **Reverse** subset is the key diagnostic setting: a duplicated single-depth hypothesis cannot satisfy both valid layer relations.
71
+
72
+ ## Download
73
+
74
+ Download the archive with `huggingface_hub`:
75
+
76
+ ```python
77
+ from huggingface_hub import hf_hub_download
78
+
79
+ zip_path = hf_hub_download(
80
+ repo_id="Xiaohao-Xu/MD-3K", # change this if the dataset is released under another HF namespace
81
+ filename="MD-3K.zip",
82
+ repo_type="dataset",
83
+ )
84
+ print(zip_path)
85
+ ```
86
+
87
+ Extract locally:
88
+
89
+ ```python
90
+ from pathlib import Path
91
+ from zipfile import ZipFile
92
+
93
+ zip_path = Path(zip_path)
94
+ out_dir = Path("data")
95
+ out_dir.mkdir(parents=True, exist_ok=True)
96
+
97
+ with ZipFile(zip_path, "r") as zf:
98
+ zf.extractall(out_dir)
99
+
100
+ print(f"Extracted to: {out_dir.resolve()}")
101
+ ```
102
+
103
+ Expected local path for the GitHub evaluation scripts:
104
+
105
+ ```text
106
+ data/MD-3K/
107
+ ```
108
+
109
+ ## Integrity check
110
+
111
+ After downloading, verify the archive.
112
+
113
+ Linux:
114
+
115
+ ```bash
116
+ sha256sum -c checksums.txt
117
+ ```
118
+
119
+ macOS:
120
+
121
+ ```bash
122
+ shasum -a 256 MD-3K.zip
123
+ ```
124
+
125
+ Windows PowerShell:
126
+
127
+ ```powershell
128
+ Get-FileHash -Algorithm SHA256 MD-3K.zip
129
+ ```
130
+
131
+ The expected SHA256 hash is:
132
+
133
+ ```text
134
+ 3E9627D3ACA6886A4449FD149B7EC791D13943D423FC5EE14F611C986BDECD29
135
+ ```
136
+
137
+ ## Annotation schema
138
+
139
+ The canonical annotation file is `annotations.json`. It maps an image path to a list of sparse point-pair annotations. A typical record is:
140
+
141
+ ```json
142
+ {
143
+ "images/example.jpg": [
144
+ {
145
+ "point1": [x1, y1],
146
+ "point2": [x2, y2],
147
+ "foreground_label": "near_or_far",
148
+ "background_label": "near_or_far",
149
+ "subset": "same_or_reverse"
150
+ }
151
+ ]
152
+ }
153
+ ```
154
+
155
+ If a compact legacy schema is used, it may contain a single `label` field. In that case, follow the repository evaluation protocol and document the mapping explicitly. Do **not** describe `label = 1` as SRA(1) or `label = 2` as SRA(2): SRA(1) and SRA(2) are evaluation targets for the foreground and background layers, not merely dataset label values.
156
+
157
+ Coordinate convention: point coordinates are stored as `[x, y]`. When indexing an image or depth array with NumPy/OpenCV, use `[y, x]`.
158
+
159
+ ## Depth convention
160
+
161
+ Before comparing a predicted depth map to MD-3K ordinal labels, verify the saved prediction convention.
162
+
163
+ Some models save depth-like outputs, where larger values indicate farther points. Other models save inverse-depth or disparity-like outputs, where larger values indicate nearer points. MD-3K evaluation requires a consistent near/far convention. If a prediction is inverse depth or disparity, convert it to depth, or equivalently flip the ordinal comparison before computing SRA(1), SRA(2), depth-layer preference, or ML-SRA.
164
+
165
+ ## Metrics
166
+
167
+ ### SRA(1)
168
+
169
+ Spatial Relationship Accuracy with respect to the transparent foreground layer.
170
+
171
+ ### SRA(2)
172
+
173
+ Spatial Relationship Accuracy with respect to the visible background layer.
174
+
175
+ ### Depth-layer preference
176
+
177
+ ```text
178
+ alpha = SRA(2) - SRA(1)
179
+ ```
180
+
181
+ Positive `alpha` indicates stronger background-layer preference. Negative `alpha` indicates stronger foreground-layer preference.
182
+
183
+ ### ML-SRA
184
+
185
+ Multi-Layer Spatial Relationship Accuracy evaluates whether a paired output, such as RGB and LVP predictions, jointly satisfies both layer-specific ordinal relations.
186
+
187
+ In the paper protocol, RGB and LVP are assigned according to the model's **RGB depth-layer preference at the benchmark level**:
188
+
189
+ - If RGB prefers layer 1, assign RGB to layer 1 and LVP to layer 2.
190
+ - If RGB prefers layer 2, assign RGB to layer 2 and LVP to layer 1.
191
+
192
+ This is not a per-image oracle and should not be described as automatic test-time layer selection. Alternative pairing strategies may be useful future improvements, but they should be reported separately.
193
+
194
+ ## Associated code and LVP
195
+
196
+ The evaluation and analysis code is maintained in the GitHub repository:
197
+
198
+ ```text
199
+ https://github.com/Xiaohao-Xu/Ambiguity-in-Space
200
+ ```
201
+
202
+ Laplacian Visual Prompting (LVP) is a deterministic, training-free input transformation. It has no learned parameters and no checkpoint, so it is not released here as a Hugging Face model. The intended use is to apply the transform to the input image, map the result back to a standard RGB image representation, and pass it through the same depth-model processor used for the original RGB input.
203
+
204
+ ## Recommended use
205
+
206
+ Use MD-3K to:
207
+
208
+ - characterize depth-layer preference in monocular depth models,
209
+ - compare RGB and LVP behavior,
210
+ - evaluate paired-hypothesis complementarity with ML-SRA,
211
+ - analyze Same and Reverse subsets separately.
212
+
213
+ Do not use MD-3K to claim dense metric multi-layer depth recovery unless additional dense ground truth and evaluation are provided.
214
+
215
+ ## Limitations
216
+
217
+ MD-3K is a focused diagnostic benchmark. It is not intended to exhaustively cover all transparency, reflection, refraction, material, or open-world 3D ambiguity cases. Its annotations are sparse ordinal point-pair labels rather than dense metric multi-layer depth maps. It should be used for controlled analysis of model behavior under layered transparent-scene ambiguity, not as a standalone guarantee of robotic safety or deployable open-world depth robustness.
218
+
219
+ ## License and data terms
220
+
221
+ This dataset card uses `license: other` because the release contains dataset annotations/masks and RGB imagery curated from upstream transparent/glass-scene data. Please follow the terms of this MD-3K release and the applicable upstream data terms. If you decide to publish the complete archive under a specific standard license, update both the YAML metadata and this section consistently.
222
+
223
+ ## Citation
224
+
225
+ If you use MD-3K, please cite:
226
+
227
+ ```bibtex
228
+ @inproceedings{xu2026onescenetwodepths,
229
+ title={One Scene, Two Depths: Probing Geometric Ambiguity in Monocular Foundation Models},
230
+ author={Xu, Xiaohao and Xue, Feng and Li, Xiang and Li, Haowei and Yang, Shusheng and Zhang, Tianyi and Johnson-Roberson, Matthew and Huang, Xiaonan},
231
+ booktitle={European Conference on Computer Vision (ECCV)},
232
+ year={2026}
233
+ }
234
+ ```