File size: 1,388 Bytes
d76b924 eb14f7a d76b924 eb14f7a 77427bb eb14f7a 77427bb d76b924 eb14f7a 7935452 d76b924 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 | # Asset Naming Specification
## Directory fields
```text
assets/<source>/raw/<asset_type>/<category>/<asset_id>/
```
Collection imports must still use the same four-level layout under `raw/`:
```text
assets/<source>/raw/<asset_type>/<category>/<asset_id>/
```
The upstream tree should be preserved inside that directory.
- `source`: lowercase snake_case.
- `asset_type`: lowercase snake_case plural for collections.
- `category`: lowercase snake_case.
- `asset_id`: preserve upstream IDs when stable.
Derived outputs use the same semantic fields, but live under:
```text
assets/<source>/derived/<asset_type>/<category>/<asset_id>/
```
Use a distinct `asset_id` suffix or additional `variant` field when storing generated variants such as convex decomposition.
Common derived `asset_type` values:
```text
convex_decompositions
primitive_collision_proxies
```
Example derived IDs:
```text
robocasa.convex_decompositions.dishwashers.Dishwasher031_coacd_v1
robocasa.primitive_collision_proxies.dishwashers.Dishwasher031_rack1_primitive_boxes_v1
```
## Global asset_id
Use:
```text
<source>.<asset_type>.<category>.<upstream_id>
```
Example:
```text
robocasa.fixtures.dishwashers.Dishwasher031
```
## Preservation rule
Do not rename upstream model files unless there is a compatibility reason. Prefer storing normalization metadata instead of mutating raw asset structure.
|