alternate-backends
Routes leafmap users to optional backend choices such as kepler, plotly, bokeh, pydeck, deck.gl, HERE, and mapbox when the default notebook maps are not the best fit.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- alternate-backends
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Routes leafmap users to optional backend choices such as kepler, plotly, bokeh, pydeck, deck.gl, HERE, and mapbox when the default notebook maps are not the best fit.
- disable-model-invocation
- true
02 资源文件 2
- 参考文档references/backends.md1.7 KB
- 参考文档references/troubleshooting.md1.4 KB
03 SKILL.md 正文
Alternate Backends
Purpose
Use this sub-skill when the user is asking which non-default leafmap backend to use or how to handle a backend-specific import or capability question.
Read this when
- The user mentions kepler, plotly, bokeh, pydeck, deck.gl, HERE, or mapbox.
- The user wants a 3D or browser-hosted map and the default ipyleaflet/folium route is not ideal.
- The user needs to know whether an optional backend is installed, missing, or unsupported in the current environment.
What this sub-skill owns
- Backend selection guidance for
leafmap.kepler,leafmap.plotlymap,leafmap.bokehmap,leafmap.deck,leafmap.deckgl,leafmap.heremap, andleafmap.mapbox. - Dependency caveats, backend-specific limitations, and missing-backend troubleshooting.
What this sub-skill does not own
- Default ipyleaflet/folium map composition.
- STAC / OSM / Planetary Computer / fire / Terrascope data helpers.
- MapLibre viewer and CLI details.
First place to look
references/backends.mdfor the selection matrix.references/troubleshooting.mdfor missing-package, API-key, and compatibility failures.../../scripts/check_leafmap_smoke.py --mode optionalfor a quick import-sanity check.
How to route a request
- Use this sub-skill when the user is trying to choose a backend or recover from a backend-specific ImportError.
- If the user only needs the best default map workflow, route them to
interactive-mapsinstead. - If the user actually wants a standalone viewer or CLI command, route them to
maplibre-viewers.
Typical workflow
- Identify the requested visual style or backend name.
- Check whether the backend is installed and whether it needs a special key or widget stack.
- Prefer a verified backend over forcing an optional one into place.
- If the backend is missing, explain the shortest safe install or the best fallback.
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).