Skip to content
#small language model Open access

frb-vlm-benchmark: a zero-shot Vision-Language Model benchmark for Fast Radio Burst detection

Sep 2026 · arXiv (Cornell University)
Wireless Signal Modulation Classification

Abstract

Code and evaluation artifacts supporting the article "Generalist Vision-Language Models for Fast Radio Burst detection: a zero-shot benchmark against a specialized detector" (Santos, Queiroz, Duarte, de Farias & Batista), submitted to The Astrophysical Journal Supplement Series (manuscript AAS80842; preprint arXiv:2607.07382). The pipeline simulates PSRFITS dynamic spectra containing Fast Radio Bursts (FRB), structured Radio Frequency Interference (RFI) and system noise; renders them as anonymized PNG images; classifies those images with small, open-weight Vision-Language Models (Gemma 4 E2B/E4B) in a zero-shot, prompt-only regime; and evaluates the predictions, including a paired, sample-by-sample comparison against the specialized detector SwinYNet. The same models, prompts and decision threshold are then applied unchanged to the 1600 real FAST observations of the FAST-FREX data set (doi:10.57760/sciencedb.15070). Contents and file formats (169 files) Source code (56 .py files) — Python packages implementing each pipeline stage: simulate_dataset/ (synthetic PSRFITS generation and selection of the balanced binary subset), plot_dataset/ (PSRFITS to anonymized dynamic-spectrum PNG), vlm_classifier/ (zero-shot classification with Gemma 4 via Hugging Face Transformers), evaluation/ (discrete, probabilistic and paired metrics), benchmark_export/ and benchmark_predictions/ (anonymized FITS export and import/comparison of external detector output), prepare_real/ (preprocessing and rendering of real search-mode PSRFITS), plus tests/ (unit tests). Entry points: run_pipeline.py (CLI integrating all stages), fetch_fast_frex.py (selects and downloads the FAST-FREX files), prompt_timing_experiment.py (prompt-latency audit), and the read-only diagnostics check_burst_visibility.py, check_burst_visibility_sim.py, analyze_visibility.py, summarize_real_run.py. Configuration (2 .yaml, 1 .toml, 1 uv.lock) — config.yaml and config_binary.yaml are the exact configurations used for the published runs, pinning the instrumental setup, the global seed and the image-rendering protocol; pyproject.toml and uv.lock pin the Python environment. Data manifests (14 .jsonl files) — line-delimited JSON. dataset/metadata/labels.jsonl and image_manifest.jsonl record, per sample, the ground-truth class, the injected burst or RFI parameters, the source PSRFITS and the anonymized image identifier; dataset_binary/metadata/ holds the same for the balanced 2000-sample binary benchmark; dataset_real_full/metadata/image_manifest.jsonl documents the per-file preprocessing of all 1600 rendered FAST-FREX observations (time window, masked channels, decimation). The predictions.jsonl file in each results directory holds one raw model response per sample. Tabular data (21 .csv files) — the burst-visibility diagnostics that underlie Section 7 of the article (fast_frex/burst_visibility_full.csv and dataset/metadata/burst_visibility_sim.csv: dedispersed peak significance, recovered peak time and catalogued parameters per burst), the FAST-FREX input manifest and burst-parameter tables, and the paired_scores.csv files aligning the continuous scores of each VLM and of SwinYNet sample by sample. Metrics and reports (15 .json, 12 .txt) — the aggregate metrics computed by evaluation/ (accuracy, macro-F1, per-class precision and recall, ROC-AUC, average precision, Brier score, ECE, McNemar tests and bootstrap intervals) and their human-readable summaries, one set per run. Figures (27 .png, 16 .pdf) — the article figures and the diagnostic plots produced by each run; figures_src/ regenerates them from the tracked artifacts. Results directories and their relationship to the article results_vlm2b_0t_binary/, results_vlm_0t_binary/ — Gemma 4 E2B and E4B on the binary FRB vs NON_FRB task (2000 simulated samples): Tables 5-7 and Figures 3-4. results_external_binary/ — SwinYNet predictions imported into the pipeline format, used as the specialized baseline. results_comparison_2b_0t/, results_comparison_4b_0t/ — paired VLM vs SwinYNet comparison: Tables 8-9 (McNemar tests, false positives by contaminant type). results_vlm2b_0t/, results_vlm_0t/ — multiclass FRB/RFI/NOISE runs on 3000 samples: Table 11. results_prompt_timing_2b/, results_prompt_timing_4b/ — prompt-latency audit on a stratified 200-image subsample: Table 10. results_real_binary_full_2b/, results_real_binary_full_4b/ — both models on the 1600 real FAST-FREX observations: Tables 12-15 and Figures 6-7. Software needed to reuse this material Python >= 3.10 with the environment pinned in pyproject.toml/uv.lock (managed with uv). The manifests, diagnostics, predictions and metrics are plain text (JSON Lines, CSV, JSON) and can be read with any standard tool, without installing the pipeline. Reproducing the runs additionally requires: simulateSearch (ascl:2205.025) for the synthetic PSRFITS; the Gemma 4 checkpoints google/gemma-4-E2B-it and google/gemma-4-E4B-it through Hugging Face Transformers, with a CUDA GPU; and, for the baseline, SwinYNet v1.0.0 with the authors' pretrained weights. Astropy, NumPy, scikit-learn, Matplotlib and PyTorch are used throughout. Data not hosted here The simulated PSRFITS files and rendered images (about 60 GB) are regenerated exactly from the pinned configuration and global seed. The real observations (about 412 GB of PSRFITS) are the public FAST-FREX data set, downloaded from the Science Data Bank by fetch_fast_frex.py; the manifests tracked here pin exactly which files were used and how each was preprocessed. Released under the MIT license. See README.md for step-by-step reproduction instructions.

Read PDF

Similar papers

#computer vision Open access Jun 2016

Software Development in Startup Companies: The Greenfield Startup Model

The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.

Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al. · 178 citations · ⚡14
#computer vision Open access Oct 2016

Software Startups - A Research Agenda

Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.

M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al. · 157 citations · ⚡17
#machine learning Review Open access Oct 2016

“Failures” to be celebrated: an analysis of major pivots of software startups

This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.

Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al. · 127 citations · ⚡15
#computer vision Review Open access May 2015

A survey study on major technical barriers affecting the decision to adopt cloud services

The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.

Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al. · 111 citations · ⚡8
#computer vision Open access Feb 2018

Lean Internal Startups for Software Product Innovation in Large Companies: Enablers and Inhibitors

This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors, and shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context.

Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al. · 78 citations · ⚡6
#computer vision Conference Sep 2010

Exploring the Sources of Waste in Kanban Software Development Projects

The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.

Marko Ikonen, Petri Kettunen, Nilay V. Oza et al. · 67 citations · ⚡9

Related blog posts

MIT News · Artificial Intelligence Sep 14, 2026

New method enables AI for safety-critical situations

The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.

GPT-Lab Sep 10, 2026

Responsible AI Must Consider Its Afterlife

AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.