OpenMOSS / OpenMOSS/Llamascopium

请问在cerebras/SlimPajama-627B 的Test子集上用llama-Scope得到的结果和图12有差异是怎么回事呢?

Open
#128 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
228
Forks
30
PR merge metrics
No merged PRs in 30d

Description

Hi, I’m trying to reproduce Figure 2 for the L15R-8x SAE on Llama-3.1-8B.

Setup

LM: meta-llama/Llama-3.1-8B

SAE release: llama_scope_lxr_8x, sae_id = l15r_8x

Script: run_llamascope_inference.py

Cmd (simplified):

python run_llamascope_inference.py --model-name meta-llama/Llama-3.1-8B --sae-release llama_scope_lxr_8x --layers 15 --dataset-cache-path slimpajama_test_cache.jsonl.gz --dataset-max-prompts 5120 --prompts-per-batch 96 --max-seq-len 512

Dataset: SlimPajama cached split, 5120 prompts, max seq len 512 (~1.84M tokens)

Observed metrics (summary JSON)

layer: L15R-8x

explained_variance ≈ 0.702

mean_l0 ≈ 32.3

tokens_evaluated ≈ 1.84M

activation_rate ≈ 9.9e-4, feature_coverage ≈ 0.983

(Δ LM loss is not implemented in my eval script yet.)

Comparison to paper

From Fig.2, my reading is that L15R-8x TopK/JumpReLU is around:

mean L0 ≈ 50

EV ≈ 0.72

So EV is in the right ballpark but a bit lower, while L0 is noticeably lower than the nominal top_k = 50.

Questions

What exact eval configuration (activation scaling, dataset, token count, gating) was used to produce Fig.2 for llama_scope_lxr_8x?

Should I be using a specific ActivationScaler config from the SAE release when calling encode/decode?

Is there a reference eval script to reproduce Fig.2, including Δ LM loss?

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with run_llamascope_inference.py and the supplied SlimPajama cached split configuration, then compare its llama_scope_lxr_8x L15R-8x evaluation with Figure 2. Check the SAE release's activation-scaling and gating settings and determine whether a reference evaluation path, including Δ LM loss, is available; done means the configuration and metric differences are explained.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ai, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.