neuron-explorer
Steering-first neuron explorer for Qwen3.5-4B: push every MLP neuron, keep every rollout, browse the results
Simulate a projected spherical display and calibrate projector alignment using camera images
AI summary · website and README
Developer toolsTypeScript · JavaScriptGitHub @zyra-projectOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
A physically-based simulator of a projected spherical display, and an alignment
solver that calibrates one from camera images.
The two are deliberately independent. They share no geometry code, no
projection math, and no distortion model — only a JSON document and the prose
describing what its numbers mean. If they shared implementation, the solver
would be inverting the simulator's own arithmetic, every recovery score would be
circular, and the project would be worthless. tools/boundary-lint.ts fails the
build on any import across that line.Read the full README ↗The full README is unavailable right now. Read it at the original link. The saved excerpt is shown below.
A physically-based simulator of a projected spherical display, and an alignment
solver that calibrates one from camera images.
The two are deliberately independent. They share no geometry code, no
projection math, and no distortion model — only a JSON document and the prose
describing what its numbers mean. If they shared implementation, the solver
would be inverting the simulator's own arithmetic, every recovery score would be
circular, and the project would be worthless. tools/boundary-lint.ts fails the
build on any import across that line.Read the full README ↗