Operator-ready prompt for reuse, tuning, and workspace runs.
This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.
Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.
Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.
Swap domain facts, examples, and any hard-coded entities for your own context.
Tighten the evidence or verification requirement if this is headed toward production.
Decide which failure mode you want to evaluate first before you branch the prompt.
This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.
Open this prompt inside Workspace when you want a live iteration loop.
Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.
Structured source with 1 active lines to adapt.
Already linked to a challenge workflow.
Sign in to keep private prompt variations.
Prompt content
Original prompt text with formatting preserved for inspection and clean copy.
Leverage CodeLlama to assist in the initial exploration of memristor material parameters or device geometries. Use CodeLlama to suggest potential material compositions or structural modifications that could influence key memristor properties (e.g., resistance range, switching speed, retention) by simulating their behavior or summarizing relevant literature. Integrate the insights or generated parameters from CodeLlama into your `MemristorArraySimulator` setup or as an input to your optimization pipeline. Document how CodeLlama's output influenced your design choices.
Adaptation plan
Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.
Hold the task contract and output shape stable so generated implementations remain comparable.
Update libraries, interfaces, and environment assumptions to match the stack you actually run.
Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.
Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.
Prompt diagnostics
Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.
This prompt is mostly narrative and instruction-driven, so you can adapt examples and output constraints first without disturbing the structure.
Optimize Memristor Array for In-Memory Bayesian Inference with BoTorch
This challenge focuses on the practical design and optimization of a memristor-based hardware accelerator for Bayesian inference. Participants will develop a computational framework to simulate memristor behavior and iteratively tune array parameters to maximize inference accuracy while minimizing energy consumption. The goal is to bridge the gap between theoretical neuromorphic computing and real-world hardware design constraints. The solution requires implementing a simplified memristor array simulator that captures key device physics, then designing a specific Bayesian inference task (e.g., parameter estimation for a materials model). Advanced Bayesian optimization techniques using BoTorch, combined with the generative capabilities of CodeLlama for design space exploration, will be employed to find optimal memristor array configurations. This directly addresses the need for accelerated materials discovery and computational design of novel computing architectures.
Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.