agentleFS
hailo-aihailo-ai/hailo-apps/.cursor/rules/hl-model-management.mdc

hailo-apps / rules

Cursor rule506 starsChanged 7 months agoMITView on GitHub

Skill: Model Management & HEF Resolution

We split this hl-model-management.mdc into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always: use resolve_hef_path() — never hardcode model paths:

    line 21
  2. Very specific:

    User provided path: If --hef-path is given and file exists → use it

    line 35
  3. Very specific:

    Resource directory: Check /usr/local/hailo/resources/models/{arch}/

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
hl-model-management.mdc
---
description: "Skill: Model Management & HEF Resolution"
alwaysApply: false
---

# Skill: Model Management & HEF Resolution

> Manage HEF model files, resolve paths, and configure model resources.

## When to Use This Skill

- User needs to **resolve HEF model paths** for their application
- User wants to **add a new model** to the configuration
- User needs to understand the **model download and caching** system
- User wants to **list available models** for an app

## HEF Path Resolution

### The Golden Rule

**Always** use `resolve_hef_path()` — never hardcode model paths:

```python
from hailo_apps.python.core.common.core import resolve_hef_path

hef_path = resolve_hef_path(
    user_provided_path,   # From --hef-path CLI arg (may be None)
    app_name="my_app",    # Registered app name from defines.py
    arch="hailo10h",      # Target architecture
)
```

### Resolution Order

1. **User provided path**: If `--hef-path` is given and file exists → use it
2. **Default model lookup**: Query `resources_config.yaml` for default model
3. **Resource directory**: Check `/usr/local/hailo/resources/models/{arch}/`
4. **Auto-download**: Download from Model Zoo or S3 if not found locally

### Resource Paths

```
/usr/local/hailo/resources/
├── models/
│   ├── hailo8/         # Hailo-8 models
│   ├── hailo8l/        # Hailo-8L models
│   └── hailo10h/       # Hailo-10H models (including Gen AI)
├── videos/             # Test/demo videos
├── images/             # Test/demo images
├── json/               # Label files, configs
├── npy/                # Numpy data files
└── so/                 # Compiled postprocess libraries
```

## Listing Available Models

```python
from hailo_apps.python.core.common.core import list_models_for_app, handle_list_models_flag

# Programmatic listing
list_models_for_app(app_name="detection", arch="hailo8")

# CLI integration
parser = get_standalone_parser()
handle_list_models_flag(parser, "my_app")  # Handles --list-models flag
```

## Config Manager API

```python
from hailo_apps.config.config_manager import (
    get_available_apps,          # List all registered apps
    get_supported_architectures, # Architectures for an app
    get_default_models,          # Default models for app+arch
    get_extra_models,            # Additional models for app+arch
    get_default_model_name,      # Default model name string
    get_model_info,              # Full model metadata (source, url)
    get_model_names,             # All model names for app+arch
)

# Examples
apps = get_available_apps()  # ["detection", "pose_estimation", "vlm_chat", ...]
models = get_default_models("detection", "hailo8")  # [ModelEntry(...)]
name = get_default_model_name("vlm_chat", "hailo10h")  # "Qwen2-VL-2B-Instruct"
```

## Adding a New App to resources_config.yaml

```yaml
# In hailo_apps/config/resources_config.yaml
my_new_app:
  models:
    hailo10h:
      default:
        - name: "Qwen2-VL-2B-Instruct"
          source: "gen-ai-mz"
      extra:
        - name: "Qwen2-VL-7B-Instruct"
          source: "gen-ai-mz"
```

## Model Sources

| Source | Description | Example |
|---|---|---|
| `mz` | Hailo Model Zoo (standard models) | YOLOv8, ResNet, etc. |
| `gen-ai-mz` | Gen AI Model Zoo (LLM/VLM/Whisper) | Qwen2-VL, Whisper-Base |
| `s3` | Direct S3 URL download | Custom models |

## HEF File Utilities

```python
from hailo_apps.python.core.common.hef_utils import (
    get_hef_input_size,    # Returns (height, width)
    get_hef_input_shape,   # Returns full shape (H, W, C)
    get_hef_labels_json,   # Extract embedded labels
)

height, width = get_hef_input_size(hef_path)
shape = get_hef_input_shape(hef_path)  # e.g., (640, 640, 3)
```

## Architecture Constants

```python
from hailo_apps.python.core.common.defines import (
    HAILO8_ARCH,    # "hailo8"
    HAILO8L_ARCH,   # "hailo8l"
    HAILO10H_ARCH,  # "hailo10h"
)
from hailo_apps.python.core.common.installation_utils import detect_hailo_arch

arch = detect_hailo_arch()  # Auto-detect connected hardware
```

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.