model-core
Build and run Mesa core models with agents, activation, time advancement, lifecycle, and event scheduling.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- model-core
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Build and run Mesa core models with agents, activation, time advancement, lifecycle, and event scheduling.
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/api-reference.md7.4 KB
- 参考文档references/troubleshooting.md2.4 KB
- 参考文档references/workflows.md5.3 KB
- 脚本scripts/mesa_model_smoke.py6.2 KB
03 SKILL.md 正文
Model Core
Use this sub-skill when the task is about Mesa's core modeling layer: Model, Agent, AgentSet, GroupBy, automatic registration, activation patterns, reproducible RNG, lifecycle/removal, and event scheduling.
Start here:
- API reference for verified signatures, object relationships, and gotchas.
- Workflows for copyable first-model, activation, event, lifecycle, and RNG recipes.
- Troubleshooting for common failure modes and quick fixes.
- Smoke script for a safe runtime check against an installed Mesa package.
Do:
- Build agents with
mesa.Agentand models withmesa.Model. - Create agents with
Agent.create_agentsorAgent.from_dataframe. - Activate agents with
model.agents.do(...),shuffle_do(...), ormodel.agents_by_type[...]. - Advance simulations with
run_for,run_until, orrun_model. - Schedule one-off and recurring work with
schedule_eventandschedule_recurring. - Remove agents with
agent.remove()and clear a model withremove_all_agents(). - Use
rng=or aScenarioinstance for reproducible randomness.
Route elsewhere when needed:
- Spatial placement and movement: ../spaces/SKILL.md
- Data collection and scenario experiments: ../analysis-experiments/SKILL.md
- Visualization dashboards: ../visualization/SKILL.md
Keep this sub-skill focused on core model mechanics; do not fold in space, analysis, or visualization workflows here.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).