-
Notifications
You must be signed in to change notification settings - Fork 63
Open
Description
[this issue is migrated from a previous version of the repo]
@elephantmipt and @zdaiot ask:
Hi, thank you for releasing great tool! It would be great if you provide more details on which files SAE viewer uses for rendering particular feature. When I run published code locally, I get an error Failed to load resource: net::ERR_CONNECTION_REFUSED because here
sparse_autoencoder/sae-viewer/src/interpAPI.ts
Lines 4 to 20 in 0296e02
| export const load_file_no_cache = async(path: string) => { | |
| const data = { | |
| path: path | |
| } | |
| const url = new URL("/load_az", window.location.href) | |
| url.port = '8000'; | |
| return await ( | |
| await fetch(url, { | |
| method: "POST", // or 'PUT' | |
| headers: { | |
| "Content-Type": "application/json", | |
| }, | |
| body: JSON.stringify(data), | |
| }) | |
| ).json() | |
| } |
we try to connect to localhost:8000
load_az method.
I need an example of a file with activations that I can pass as JSON here
| const result = await load_fn(`${prefix}/${ae.subject}/${ae.path}/atoms/${feature.atom}${ablated ? '-ablated': ''}.json`) |
, in case I want to view features from my custom SAE. However, I am unsure of the format to use. Could you please provide example files with activations so that anyone can run the demo locally and/or modify the activations and models?
Metadata
Metadata
Assignees
Labels
No labels