Downloads · 30 days
0
jasonlingg/rlm-explorer-qwen3-8b-qasper-sft
rlm-explorer-qwen3-8b-qasper-sft is a text generation model from jasonlingg. Use it when you need the model to write or continue text. It is set up for peft. The card lists the license as apache-2.0.
This private repository preserves two experimental QLoRA checkpoints from the RLM Explorer scientific-paper research-agent project. The model was trained to write Python actions that call search(), read(), and extract…
Downloads · 30 days
0
Access
Public
Updated Sep 17, 2026
Repo size
143 MB
Likes
0
Public
Click a slice to open those files.
.pt88.2 MB · 54%
From the Hugging Face model README
This private repository preserves two experimental QLoRA checkpoints from the
RLM Explorer scientific-paper research-agent project. The model was trained to
write Python actions that call search(), read(), and extract() before
submitting an evidence-grounded answer.
Research status: these checkpoints are artifacts for evaluation and debugging. They do not currently demonstrate an improvement over base Qwen3-8B. Epoch 2 improved held-out next-token metrics but collapsed to immediate answer submission in behavioral evaluation.
| Path | Training point | Status |
|---|---|---|
epoch-1/ | step 48, epoch 1 | Behavioral smoke evaluation pending |
epoch-2/ | step 96, epoch 2 | Failed the agent-loop behavioral evaluation |
evaluation/ | base, epoch-2, and aligned smoke outputs | Full trajectories, logs, and manifests |
experiment_summary.json | experiment metadata | Machine-readable summary |
Each checkpoint contains the LoRA adapter, tokenizer, trainer state, optimizer,
scheduler, RNG state, and training arguments. The adapter in the original
final/ directory was byte-identical to checkpoint-96, so only one epoch-2
copy is stored here.
Qwen/Qwen3-8Bq_proj, k_proj, v_proj, o_proj, gate_proj, up_proj, and down_proj2e-4| Checkpoint | Eval loss | Eval mean-token accuracy |
|---|---|---|
| Epoch 1 | 0.5243 | 0.8528 |
| Epoch 2 | 0.4916 | 0.8617 |
These metrics show that the model learned to imitate held-out trajectories. They do not establish that it learned to operate the research-agent loop.
The frozen evaluation contained 40 QASPER test questions: 20 answerable from the paper corpus and 20 requiring abstention. There was no training/test question or paper overlap. Both policies used deterministic decoding, seed 42, a 10-step limit, and the same 416-paper corpus.
| Metric | Base Qwen3-8B | Epoch 2 |
|---|---|---|
| Average reward | 0.216 | 0.170 |
| Answer score | 0.091 | 0.044 |
| Citation precision | 0.475 | 0.425 |
| Citation recall | 0.950 | 0.925 |
| Average steps | 8.5 | 1.0 |
| Correct abstentions | 1/20 | 2/20 |
| False abstentions | 1/20 | 1/20 |
The preregistered abstention threshold required at least 7/20 correct
abstentions and no more than 4/20 false abstentions. Epoch 2 did not pass
(p = 1.0, two-sided Fisher exact test).
The first full comparison contained a train/serve mismatch: the initial observation repeated the tool preamble. A corrected five-question diagnostic removed that duplication. Epoch 2 still submitted immediately on 5/5 questions and used no tools, although it no longer copied placeholder text. This isolates the central failure: the adapter learned a direct-submit shortcut.
from transformers import AutoModelForCausalLM, AutoTokenizer
from peft import PeftModel
base_id = "Qwen/Qwen3-8B"
repo_id = "jasonlingg/rlm-explorer-qwen3-8b-qasper-sft"
tokenizer = AutoTokenizer.from_pretrained(repo_id, subfolder="epoch-1")
base = AutoModelForCausalLM.from_pretrained(base_id, device_map="auto")
model = PeftModel.from_pretrained(base, repo_id, subfolder="epoch-1")
Use epoch-1 or epoch-2 explicitly. Do not treat epoch-2 as a recommended
production model.
rlm-explorerd7e6efa2b9f90af32584f6973eff364389cbf8aeaf762ba0ab63e179f4c0ba9714e0c4a7d9985793b968826d9c46dd6066d109eabc6255188de912185720a5220ff9e47eb2465028d9592551d4575830ec476dfafc31a4470a11d4d0ee9e3b2986845194cf9a25dbd1ea1ab2cb8e44cd5e385e5cefcb8f7665335a9fThe files under evaluation/ contain the exact question IDs, policy settings,
hardware, software versions, run IDs, and full trajectories.