SwiftVLN Documentation

简体中文 | English

The SwiftVLN documentation is organized by research workflow. New users should begin with installation, model checkpoints, and data preparation. If your environment and data are already available, proceed directly to training or evaluation.

For SatNav scenes, request prepared GeoTIFFs or generate them with your own API credentials.

Implementation principles

1. Installation and setup

  1. Installation: create the training and evaluation environments.

  2. Models and checkpoints: download Qwen base models and released SwiftVLN checkpoints.

  3. SatNav training data: prepare episodes, GeoTIFF scenes, and offline trajectories.

  4. Habitat training data: prepare R2R, RxR, and EnvDrop trajectories.

  5. Evaluation data: prepare SatNav and Habitat resources for online evaluation.

2. Training

3. Evaluation

4. Development

  • Architecture: training and evaluation pipelines, module boundaries, and dependency direction.

  • Extending SwiftVLN: add an environment backend, history processor, embedding enhancement, or model family.

5. Find documentation by task

Task

Documentation

Install from source

Installation

Download a base model or checkpoint

Models and checkpoints

Prepare SatNav training trajectories

SatNav training data

Prepare Habitat training trajectories

Habitat training data

Prepare SatNav or Habitat evaluation data

Evaluation data

Train SwiftVLN

SwiftVLN training

Configure a Memory experiment

Memory configuration

Generate SatDronePair data

SatDronePair generation

Train a Satellite-to-UAV adapter

Satellite-to-UAV Stage-A

Evaluate a checkpoint

SwiftVLN evaluation

Modify core modules

Architecture

6. Conventions

  • Run commands from the SwiftVLN repository root unless stated otherwise.

  • Replace /path/to/... with the corresponding path on your machine.

  • Keep machine-specific paths, models, datasets, and credentials in local configuration.

  • Smoke tests validate execution paths and are not performance benchmarks.

  • Each procedure provides an expected output or a condition that can be checked after completion.