For sakana ai infrastructure and model engineering teams
Sakana EvoLLM evaluation: setup failure or model execution?
Match the released model, evaluation configuration and first exception. Keep missing evaluation assets distinct from a failed GPU operation.
Free 30-day Team evaluation. No card or automatic subscription. Work email verification required.
Replay a resolved Sakana AI workflow incident
Upload your log file. Review the selected evidence and masking, then run diagnosis. Keep the original log for any follow-up questions.
Before uploading, review cloud data handling and local options.
Upload your log file. Large files are processed in your browser. Only selected evidence is submitted when you run diagnosis.
Try Denpex for 30 days. FREE.
No credit card. No automatic subscription. See whether Denpex helps with an incident you already understand.
Start your free 30-day Team evaluation
Up to 50 diagnoses a day for 30 days. Verify your work email to activate an eligible company evaluation, then replay a resolved incident and compare the evidence and next steps with your team's confirmed cause.
What a useful evaluation should establish
Compare one incident your team has already resolved with the first failure, quoted evidence and remaining questions. Begin with this question: Is the evaluation environment the one being compared? Only assign a process, device or recovery state when the submitted evidence establishes it.
Is the evaluation environment the one being compared?
Evidence to compare: Python and CUDA versions, package revision and selected evaluation configuration.
A version mismatch can fail before inference begins. Record the actual environment rather than treating the published test setup as a universal requirement.
Were the required evaluation assets available?
Evidence to compare: Asset paths, loader exceptions and the selected model identity.
A missing language-detection asset or inaccessible model is not evidence of GPU exhaustion. Establish input and model loading before device diagnosis.
Did execution fail or did a valid score disappoint?
Evidence to compare: Process exit status, retained traceback and completed metric output.
Infrastructure failure and model quality are separate outcomes. Do not prescribe a reset or claim recovery merely because a benchmark score changed.
Use Denpex alongside your existing telemetry tools to investigate submitted incident evidence. With monitoring configured on a supported plan, detected failures can trigger alerts and an automatic diagnosis from the captured evidence.
Inside Denpex
See the evidence, not just the claim
Follow the causal chain, inspect the quoted evidence and prepare the next handoff. These actual product captures use founder-account examples and the VS Code extension, with the source identified under each image. Open a capture to inspect it at full size.
Follow the failure through the cascade
Prepare the hardware escalation
Ask for the evidence that is missing
Keep the investigation in the editor
