ff-new-model

name: ff-new-model description: "Complete workflow for adding a new model adapter. Covers analysis, sample dataclass, adapter implementation (4 abstract methods + per-modality encoder overrides), registry, example YAML, and verification. Trigger: 'add model', 'support new model', 'integrate model', 'new adapter'."

New Model Adapter Integration

Authoritative reference: guidance/new_model.md — read it first.

Prerequisites

Before starting, ensure you understand:

1. The target model's diffusers pipeline (or that you'll need a pseudo-pipeline)
2. The task type: Text-to-Image, Image-to-Image, Text-to-Video, Image-to-Video
3. Which Sample dataclass to extend

Phase 1: Analysis

1. Identify the diffusers pipeline for the target model
   • Check if it exists in diffusers: from diffusers import <Pipeline>
   • If not, you'll need a pseudo-pipeline (see guidance/new_model.md advanced section)
2. Study an existing adapter of the same task type:
   • T2I: models/flux/flux1.py or models/stable_diffusion/sd3_5.py
   • I2I: models/flux/flux1_kontext.py or models/qwen_image/qwen_image_edit_plus.py
   • T2V: models/wan/wan2_t2v.py
   • I2V: models/wan/wan2_i2v.py
3. Map pipeline components to adapter responsibilities:
   • Text encoders → encode_prompt(), preprocessing_modules
   • VAE → encode_image() / decode_latents(), preprocessing_modules
   • Audio encoder/VAE (if any) → encode_audio(), preprocessing_modules
   • Transformer/UNet → forward(), default_target_modules (LoRA target layer names), inference_modules
4. Also read: topics/adapter_conventions.md for upstream alignment rules; topics/dtype_precision.md for precision handling in cast_latents().

Phase 2: Implementation

Step 1 — Define Sample Dataclass

# src/flow_factory/models/<family>/<model>.py
@dataclass
class MyModelSample(T2ISample):  # or appropriate base
    _shared_fields: ClassVar[frozenset[str]] = frozenset({})
    # Add model-specific fields if needed

Step 2 — Create Adapter Class

class MyModelAdapter(BaseAdapter):

    @property
    def preprocessing_modules(self) -> List[str]:
        return ["text_encoder", "vae"]  # Components for Stage 1

    @property
    def inference_modules(self) -> List[str]:
        return ["vae"]  # Components needed at inference time

    @property
    def default_target_modules(self) -> List[str]:
        # LoRA target module names used when YAML sets `target_modules: default`.
        # Override only if your transformer uses non-standard attention layer names.
        return ["to_q", "to_k", "to_v", "to_out.0"]

Which components are trainable is config-driven: the YAML target_components / target_modules fields are resolved by BaseAdapter._parse_target_modules() into self.target_module_map (set in __init__). Adapters do not override target_module_map.

Step 3 — Implement Required Methods

Step 4 — Register

Add to _MODEL_ADAPTER_REGISTRY in src/flow_factory/models/registry.py:

'my-model': 'flow_factory.models.<family>.<model>.MyModelAdapter',

Phase 3: Configuration

Create example YAML config in examples/grpo/lora/<model>/default.yaml:

model:
  model_type: "my-model"
  model_name_or_path: "org/model-name"
  finetune_type: "lora"
  target_components: ["transformer"]

Phase 4: Verification

Also read: topics/parity_testing.md for the 4-layer verification protocol.

• load_pipeline() successfully loads the model
• preprocess_func() produces correct cached tensors
• inference() generates valid images/videos
• forward() computes loss without errors
• Training runs end-to-end with GRPO for ≥2 steps
• LoRA weights save and reload correctly
• Registry entry resolves correctly: get_model_adapter_class('my-model')
• Example YAML config is valid and complete

Common Pitfalls

1. Forgetting to set preprocessing_modules — causes text encoder to stay on GPU, OOM during training
2. Wrong target_components / target_modules (or default_target_modules) — LoRA applied to wrong components/layers, no training effect
3. Mismatched _shared_fields — data corruption during batch collation
4. Not handling enable_preprocess=False — encoding components not loaded at inference time
5. Inconsistent custom field types across samples — if a custom sample field is Tensor on some samples and List[Tensor] on others, gather_samples will fall back to slow pickle-based gather_object. Always canonicalize to a single type in __post_init__; prefer List[Tensor] for variable-length data.
6. Wrong images/condition_images/audios convention — preprocess_func(), encode_image(), encode_video(), encode_audio(), and inference() all operate at batch level: images is List[List[Image.Image]] (MultiImageBatch), condition_images is List[List[Tensor(C,H,W)]] (or List[List[PIL.Image]] for adapters that declare python_format_columns, e.g. Bagel), and audios is List[List[Tensor]] (MultiAudioBatch), where the outer list indexes samples in the batch and the inner list holds each sample's items. Empty samples contribute [] (never None); single-item samples contribute [item] (never a bare element). Never pass a flat List[Image] / List[Tensor] or unwrap single-element lists — that breaks Arrow's homogeneous-column requirement and forces every downstream consumer to handle three input shapes. For single-condition models, _standardize_image_input / _standardize_video_input must detect the nested format with is_multi_image_batch / is_multi_video_batch, extract the first element per sample ([batch[0] for batch in images]), and warn if extra conditions are discarded (e.g. Wan2_I2V._standardize_image_input, LTX2_I2AV._standardize_image_input). See topics/adapter_conventions.md Gotcha #5 and #6.