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
Dual memory and sliding windows: observations, action chunks, window updates, and supervision.
Historical memory and token compression: sampling, pooling, GridToMe, GTC, and STC computations.
Map memory: explored masks, global/local views, and token budgets.
Input augmentation and UAV adaptation: initial views, pose FiLM, and Stage-A alignment objectives.
1. Installation and setup
Installation: create the training and evaluation environments.
Models and checkpoints: download Qwen base models and released SwiftVLN checkpoints.
SatNav training data: prepare episodes, GeoTIFF scenes, and offline trajectories.
Habitat training data: prepare R2R, RxR, and EnvDrop trajectories.
Evaluation data: prepare SatNav and Habitat resources for online evaluation.
2. Training
SwiftVLN training: shared training configuration, SatNav training, Habitat training, and resume.
Memory configuration: history-frame sampling, input augmentation, and long-term Memory compression.
Satellite-to-UAV Stage-A: SatDronePair manifests, adapter training, and retrieval evaluation.
SatDronePair generation: convert UAV–satellite datasets for Satellite-to-UAV Stage-A.
SatNav training data: generate and validate SatNav offline trajectories.
Habitat training data: generate and validate R2R, RxR, and EnvDrop trajectories.
3. Evaluation
Models and checkpoints: download the default SatNav model, ablation models, and backbone models.
Evaluation data: prepare SatNav episodes and GeoTIFF scenes or Habitat R2R and MP3D data.
SwiftVLN evaluation: configure and run single- or multi-GPU online 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 |
|
Download a base model or checkpoint |
|
Prepare SatNav training trajectories |
|
Prepare Habitat training trajectories |
|
Prepare SatNav or Habitat evaluation data |
|
Train SwiftVLN |
|
Configure a Memory experiment |
|
Generate SatDronePair data |
|
Train a Satellite-to-UAV adapter |
|
Evaluate a checkpoint |
|
Modify core modules |
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.