Training catalog
Entering the training wizard's framework, model and hyperparameter choices per framework key in the database, and keeping them in line with image labels
Required permission: SettingsADMIN
The choices in steps 2 (framework cards), 3 (models) and 7 (hyperparameters) of the new training wizard come from the training catalog. There is one catalog per framework key (the framework value of a training runtime variant, for example defect-clf). All variants with the same key share the same catalog.
Where the catalog is looked up
| Order | Location | Who enters it |
|---|---|---|
| 1 | Tenant DB: this tenant's catalog | Tenant admin (this screen) |
| 2 | Shared DB: applies to every tenant using the key | Global admin (Shared images) |
| 3 | Code: a definition built into the platform | Platform release |
The first match wins. Once saved in the tenant DB, it takes precedence over the shared DB and the code in that tenant.
Built-in frameworks (YOLO, RF-DETR, Pointcept) are defined by code, reviewed together with their Dockerfiles. These keys cannot be stored in the DB.
Catalog status
The Catalog (카탈로그) column of the Training runtime (학습 런타임) list shows a status per key.
| Badge | Meaning | Wizard |
|---|---|---|
DB · 수동 (DB, manual) | Stored in the DB, edited by a person | Selectable |
DB · 라벨 반입 (DB, from label) | Stored in the DB, imported automatically from the runtime image label | Selectable |
코드 정본 (code canonical) | Built-in framework | Selectable |
코드 기본값 (code defaults) | Not in the DB, running on the definition built into the code | Selectable, with a notice on the card |
카탈로그 없음 (no catalog) | Neither in the DB nor in the code | Not selectable, with the reason on the card |
코드 기본값 and 카탈로그 없음 need input. Until then a warning shows in the orange banner on the training runtime screen, in the Catalog (카탈로그) column and on the wizard step 2 card. Code defaults may be removed in a later release, so enter them into the DB ahead of time.
Entering and editing a catalog
- In the admin console Training runtime (학습 런타임) screen, press the key's input button in the banner or the catalog icon on the variant row. The editor opens.
- Pick where to start from in Start from (시작점) and press Load (불러오기): Fill from code defaults (코드 기본값으로 채우기), Copy shared catalog (공유 카탈로그 복사), Import from image label (이미지 라벨에서 가져오기), Copy another key's catalog (다른 키의 카탈로그 복사) or Blank manifest (빈 매니페스트). Merge an
hp_preset.yamldelivered by a partner into the current text with Import hp_preset.yaml (hp_preset.yaml 가져오기). As you edit the YAML on the left, the server validates it and marks lines with errors in red. The wizard preview on the right shows steps 2, 3 and 7. - When there are no errors, press Save to DB (DB 에 저장). The confirmation dialog shows how many variants change with it and how many experiments can no longer be re-run because a model key is removed.
For the format see Catalog registration.
Image labels
A runtime image can carry its own catalog as the OCI label io.geo-mlops.catalog.v1. Labels are read only from images in the platform registry (images in an external registry show 조회 불가, unreadable, in the Image label (이미지 라벨) column). The label is read when an import finishes, when the same tag is pushed to the registry, and when a variant is created or edited.
| Situation | Action | Image label (이미지 라벨) column |
|---|---|---|
| No tenant catalog for the key | Creates the catalog from the label (DB · 라벨 반입) | DB 와 같음 (same as DB) |
The catalog is DB · 라벨 반입 | Updates it with the new label | DB 와 같음 |
The catalog is DB · 수동 | No change | 라벨과 다름 (differs from label) |
| The label key differs from the variant's framework | Not applied | 라벨 키 불일치 (label key mismatch) |
| The label key is a built-in framework | Not applied | 라벨 오류 (label error) |
| The variant's framework is Unrestricted (제한 없음) | Not applied, the key is recorded | 키 지정 대기 (waiting for a key) |
Selecting a 라벨과 다름 variant in the list shows Re-import from label (라벨에서 다시 가져오기) in the detail below. It replaces the catalog with the label and changes the source to DB · 라벨 반입 (the previous text stays in history). View label (라벨 원문 보기) only shows the label in the registry without changing the DB.
External variants without a framework
A catalog attaches to a key, so an external variant whose framework is Unrestricted (제한 없음) gets no catalog. Such variants appear in the banner and in the variant detail, and Assign framework key (프레임워크 키 지정) in the variant detail (<tag> 키 지정 in the banner) sets a key once. If the image label names a key, it is filled in. After assigning, the label is read again and applied. A key cannot be changed once set.
A new external variant can get a key from the start with Enter own key (자체 키 입력) under Training framework in the Add variant (변형 추가) dialog (see Image variants).
History and deletion
- Show history (이력 보기) at the bottom of the editor lists the text kept for each save, label import and restore. Restore this version (이 본문으로 되돌리기) saves that text as a new version.
- Delete tenant catalog (테넌트 카탈로그 삭제) deletes this tenant's DB catalog and its history. The key then runs on the shared DB or code defaults, or becomes
카탈로그 없음if neither exists.