Troubleshooting

Use this page when the platform loads but a run will not start, a target fails to load, or account verification gets stuck.

WebGPU Not Available

What this means

LatticeZero scoring and docking run on WebGPU. If the browser cannot create a WebGPU adapter, the app can still load its docs and account pages, but GPU scoring features stay unavailable.

Common causes

• Unsupported browser build
• Hardware acceleration disabled
• Out-of-date GPU drivers
• Remote desktop or VM session without GPU passthrough
• Enterprise browser policies that disable WebGPU

What to check

1. Use a current Chromium browser such as Chrome or Edge.
2. Turn on hardware acceleration in browser settings.
3. Open chrome://gpu and confirm WebGPU is enabled on the active adapter.
4. Update NVIDIA, AMD, or Intel graphics drivers.
5. If you are on a laptop with integrated and discrete GPUs, force the browser onto the discrete GPU.
6. If you are in a VM or remote session, confirm GPU passthrough is actually available.

Expected fallback behavior

• The app should explain that WebGPU is unavailable.
• Documentation pages, account pages, and non-scoring surfaces should still work.
• There is no hidden server-side docking fallback for the web scoring path; a WebGPU-capable browser is required for live runs.

Scoring Errors

Run stalls or times out

Typical causes:

• Large ligand set with an aggressive accuracy preset
• Browser tab suspended in the background
• GPU resource exhaustion from other tabs or applications
• A demo bundle that loaded partially and never finished preparing the scoring path

What to do:

1. Refresh the page and rerun the target.
2. Drop to a smaller ligand subset before retrying a full run.
3. Close other GPU-heavy tabs and desktop apps.
4. Keep the tab in the foreground while the run initializes.

Receptor or target bundle fails to load

Typical symptoms:

• Empty target list
• "Target not found"
• Blank run panel after selecting a target
• Repeated fetch failures in the browser console

What to do:

1. Reload the page once to clear partial bundle state.
2. Try a second target; if multiple targets fail, the issue is probably global rather than target-specific.
3. Check the browser console for missing bundle files such as manifest.json, receptor.pdb, or ligand assets.
4. If the failure is isolated to one bundle, compare its static files with a known-good target in /static/wasm/demo_assets/v3/.

Scores are zero, NaN, or obviously wrong

Typical causes:

• The pose is outside the intended pocket
• The wrong scoring mode or profile is being used
• The target bundle loaded but the scoring metadata is stale
• WebGPU initialized, but the scoring path failed partway through setup

What to do:

1. Confirm the target bundle loaded completely before running.
2. Re-check the selected scoring profile and mode.
3. Compare the result against the published AUC for that target on Benchmark Results.
4. For lab work, compare dockAuc with the post-rescore metric to see whether the issue is the search stage or the scoring stage.

Email Verification Issues

Verification email never arrives

1. Check spam and promotions folders first.
2. Wait a few minutes before requesting another message.
3. Confirm the account was created with the same address you are checking.
4. If available, use the resend action instead of creating a second account.

Verification link opens but the account still looks unverified

1. Open the newest verification email only.
2. Complete the flow in the same browser session you plan to use for sign-in.
3. If you requested multiple emails, older links may have been superseded.
4. Sign out and back in after verification to refresh session state.

Magic-link or verification flow expires

• Request a fresh email and use the newest link.
• Avoid forwarding old verification links between devices.
• If the app loops back to sign-in, clear the stale tab and retry from the newest message.

Common Docking Questions

Why is my AUC low?

A low AUC usually means one of three things:

• the pose search is not landing actives in the right geometry
• the scoring profile is not separating actives from decoys for that target
• the current bundle is intentionally retained as an honest-but-weaker product path

Use these checks:

1. Compare dockAuc against the post-rescore AUC.
2. If both are low, the search setup or bundle quality is the likely issue.
3. If dockAuc is reasonable but post-rescore drops, the scoring profile or rescore configuration needs attention.

What does cascade rescore do?

Cascade rescore is the second-stage ranking pass applied after docking. The first stage finds poses and produces a raw dock ranking. The cascade stage then extracts physics features from those poses and applies the target-specific scoring profile. On some surfaces the post-docking metric is labeled rescoreAuc; in discussion it is often referred to as cascadeAuc.

In practice:

• dockAuc tells you how well the pose-search stage alone separates actives from decoys.
• cascadeAuc / rescoreAuc tells you how well the final ranking performs after profile-based rescoring.

When should I trust the dock ranking over the rescore ranking?

Use the raw dock ranking only when the bundle or validation notes explicitly say the dock ordering is the retained gold path. Otherwise, the post-rescore ranking is the number to compare against the published benchmark.

When To Escalate

Escalate a bundle issue when all of the following are true:

• WebGPU is working on the machine
• the target assets load cleanly
• rerunning does not change the failure
• the live result still disagrees materially with the published target AUC or expected behavior

When filing the issue, capture:

• browser name and version
• OS and GPU model
• target ID
• whether the failure happened in Demo, Run, or IsoPose Lab mode
• any console error text