Datasets:
Move reproducibility files to a private repo for author review before public release
Browse files- reproducibility/vlm_prompts.md +0 -105
reproducibility/vlm_prompts.md
DELETED
|
@@ -1,105 +0,0 @@
|
|
| 1 |
-
# VLM prompts used in the DeepJEB++ quality filter
|
| 2 |
-
|
| 3 |
-
<!-- ============================================================================
|
| 4 |
-
PUBLIC FILE - this is what gets uploaded to Hugging Face as reproducibility/vlm_prompts.md
|
| 5 |
-
The annotated working copy, with provenance notes, is prompts_extracted.md in this same
|
| 6 |
-
folder and is NOT for release.
|
| 7 |
-
|
| 8 |
-
Cleared for upload: the scoring-criteria question was answered by Jinsu Ra on 2026-08-22.
|
| 9 |
-
============================================================================ -->
|
| 10 |
-
|
| 11 |
-
Stage 1 of the pipeline screens candidate images with a vision-language model. The model is
|
| 12 |
-
asked to describe a rendered bracket, and the description is scored against a fixed vocabulary
|
| 13 |
-
of defect words; images whose score falls in the most defect-like top-*p*% are removed. This
|
| 14 |
-
file gives the exact prompt strings behind every filter variant reported in the paper, so that
|
| 15 |
-
the numbers in Table 2 can be reproduced.
|
| 16 |
-
|
| 17 |
-
The strings are reproduced verbatim from the generation notebooks and from the scoring manifest
|
| 18 |
-
on our lab server. Nothing here is retyped.
|
| 19 |
-
|
| 20 |
-
## The adopted filter — LLaVA with negative-word negation (NWN)
|
| 21 |
-
|
| 22 |
-
```
|
| 23 |
-
Question: Do not use word "no". Describe the red object's surface roughness as details. Do not use "no". Answer:
|
| 24 |
-
```
|
| 25 |
-
|
| 26 |
-
This is the filter used to build the released dataset. It reaches **72.17%** accuracy on the
|
| 27 |
-
labeled benchmark at the default threshold and **76.10%** at the tuned operating point
|
| 28 |
-
*p* = 29% (false-positive rate 40.7%, false-negative rate 14.0%).
|
| 29 |
-
|
| 30 |
-
The doubled negation is deliberate. Asking the model not to use the word "no" suppresses the
|
| 31 |
-
negated descriptions ("no visible cracks", "not rough") that otherwise dominate the output and
|
| 32 |
-
collide with the defect vocabulary, since a negated defect word and a present defect word score
|
| 33 |
-
alike under embedding similarity.
|
| 34 |
-
|
| 35 |
-
## The no-correction baseline — same backbone, no negation instruction
|
| 36 |
-
|
| 37 |
-
```
|
| 38 |
-
Could you describe this red object's surface condition as detail as possible and some Geometry Complexity? Answer:
|
| 39 |
-
```
|
| 40 |
-
|
| 41 |
-
This is Table 2's "Vanilla prompt (no NWN)" row at **56.45%**. The gap between this and the
|
| 42 |
-
adopted prompt is the effect of the negation instruction alone: the backbone, the vocabulary and
|
| 43 |
-
the scoring are identical.
|
| 44 |
-
|
| 45 |
-
## The alternative backbone — BLIP with the same NWN prompt
|
| 46 |
-
|
| 47 |
-
```
|
| 48 |
-
Question: Do not use word "no". Describe the red object's surface roughness as details. Do not use "no". Answer:
|
| 49 |
-
```
|
| 50 |
-
|
| 51 |
-
Identical prompt text; only the vision-language backbone differs. This is Table 2's
|
| 52 |
-
"BLIP + NWN prompt" row at **62.67%**, where the filter degenerates to near keep-all.
|
| 53 |
-
|
| 54 |
-
## Which result file used which prompt
|
| 55 |
-
|
| 56 |
-
| Reported result | Backbone | Prompt above | Vocabulary |
|
| 57 |
-
|---|---|---|---|
|
| 58 |
-
| 76.10% / 72.17% (adopted) | LLaVA | adopted NWN | `llm_keywords.txt` |
|
| 59 |
-
| 56.45% | LLaVA | no-correction baseline | `llm_keywords.txt` |
|
| 60 |
-
| 62.67% | BLIP | adopted NWN | `llm_keywords.txt` |
|
| 61 |
-
|
| 62 |
-
All three scoring runs use the same 112-word vocabulary, released here as
|
| 63 |
-
`reproducibility/llm_keywords.txt`.
|
| 64 |
-
|
| 65 |
-
## Vocabulary
|
| 66 |
-
|
| 67 |
-
`llm_keywords.txt` holds the **112** defect and manufacturability terms, one per line, that form
|
| 68 |
-
the negative-word set. The description embedding is compared against each term and the *mean*
|
| 69 |
-
cosine similarity is the image's defect score, so the file's length is also the dimension of the
|
| 70 |
-
similarity vector referred to in the paper as the 112-dimensional negative-word similarities.
|
| 71 |
-
|
| 72 |
-
The file has no trailing newline, so `wc -l` reports 111; the count is 112.
|
| 73 |
-
|
| 74 |
-
## Scoring criteria
|
| 75 |
-
|
| 76 |
-
The 112 defect words were generated by prompting a language model with seven engineering
|
| 77 |
-
criteria. All three scoring runs use the same list:
|
| 78 |
-
|
| 79 |
-
```
|
| 80 |
-
Manufacturability
|
| 81 |
-
Surface Clearence
|
| 82 |
-
Surface Texture
|
| 83 |
-
mono-body
|
| 84 |
-
uni-body
|
| 85 |
-
Smooth Surface
|
| 86 |
-
Good Strength
|
| 87 |
-
```
|
| 88 |
-
|
| 89 |
-
These are reproduced exactly as the scoring configuration records them, including the spelling
|
| 90 |
-
of "Clearence". Section 3.2.4 of the paper and Figure 3 list the same seven; both write
|
| 91 |
-
"surface roughness" for the criterion the configuration labels "Surface Texture", which is the
|
| 92 |
-
same criterion under two names.
|
| 93 |
-
|
| 94 |
-
The criteria are the prompt given to the language model that produces the vocabulary. They are
|
| 95 |
-
not applied to images as separate tests: the only quantity computed per image is the mean
|
| 96 |
-
similarity to the 112 words.
|
| 97 |
-
|
| 98 |
-
## A limitation of this release
|
| 99 |
-
|
| 100 |
-
The prompts and the vocabulary are fully determined, and the diffusion sampler is deterministic.
|
| 101 |
-
The selection of *which* images condition a given 3D generation is not recoverable: each design
|
| 102 |
-
is conditioned on eight images drawn from its interpolation pair's retained pool, and that
|
| 103 |
-
sampler was seeded with Python's string hash, which is randomized per process and was not fixed.
|
| 104 |
-
The dataset itself is unaffected — the meshes and labels are what they are — but a bit-exact
|
| 105 |
-
replay of the image-to-mesh step is not possible.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|