We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFEvaluating GPT-J, GPT-NeoX, or CodeGen models with multiple GPUs (torch.distributed.launch or deepspeed) triggers RuntimeError: Tensors must be contiguous during the evaluation loop.
THENEnsure tensors are contiguous before all-gather operations in distributed evaluation. Add `.contiguous()` calls after operations like transpose or view in the model's forward pass, particularly in attention layers. If you cannot modify the library code, monkey-patch the model's forward method in your script to call `.contiguous()` on relevant tensors before they are gathered.
IFWhen evaluating models like GPT-J, codegen-16B, or gpt-neox-20b on multiple GPUs using torch.distributed.launch or deepspeed, evaluation crashes with 'Tensors must be contiguous' error in the distributed gather step.
THENEnsure that tensors are contiguous before the distributed gather operation. This can be done by adding `.contiguous()` calls in the model's forward method for the relevant outputs, or by using `model.to(memory_format=torch.contiguous_format)` as a workaround. Additionally, consider using `torch.distributed.all_gather` with contiguous tensors. The root cause is likely missing contiguous calls in the model modeling code.
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site