core-data-and-geometry
Routes PhiFlow field, geometry, mesh, scene, and data-format workflows.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- core-data-and-geometry
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Routes PhiFlow field, geometry, mesh, scene, and data-format workflows.
- disable-model-invocation
- true
02 资源文件 3
- 参考文档references/troubleshooting.md2.2 KB
- 参考文档references/workflows.md3.5 KB
- 脚本scripts/scene_roundtrip.py2.1 KB
03 SKILL.md 正文
Core Data and Geometry
Use this sub-skill for the core PhiFlow objects that most other workflows build on: fields, grids, geometries, meshes, scenes, and field/scene I/O.
Route here for
CenteredGrid,StaggeredGrid,PointCloud,Noise, andAngularVelocityBox,Sphere,Cuboid,Cylinder,UniformGrid,Mesh,Graph,Heightmap,SDFGrid, andSDFScene.create(),Scene.at(),Scene.list(),Scene.write(),Scene.read(), and scene cleanup helpersfield.read(),field.write(),field.resample(),field.sample(), andfield.reduce_sample()Geometrytransformations and set operations such asshift,rotate,union, andintersection- scene / field file formats and legacy compatibility issues
Do not route here
- installation or backend setup ->
installation-and-backends - PDE stepping, fluids, waves, FLIP, or SPH ->
physics-and-simulation - gradients, Jacobians, or inverse design ->
optimization-and-learning - plotting, display, controls, or scalar logs ->
visualization-and-ui
Start with these imports
from phi.flow import *
from phi import field, geom, math
from phiml.math import batch, channel, instance, spatial, vec
Most common decisions
- Grid type: use
CenteredGridfor scalar quantities andStaggeredGridfor velocity-like vector fields. - Sampling vs resampling: use
field.sample()when you need values at aGeometry; usefield.resample()orField.at()when you need compatible field representations. - Scene I/O: use
Scene.create()for new scenes,Scene.write()to store fields, andScene.read()to recover them. The scene format storessim_folders with*.npzfield files. - Geometry syntax: prefer keyword constructors such as
Box(x=1, y=1)or the explicit slicing formBox['x,y', 0:1, 0:1]. - Mesh / implicit geometry: use
Meshfor unstructured surfaces or volumes, andSDFGrid/SDFwhen you want implicit shapes. - Legacy code: treat
Domainas compatibility-only. New workflows should construct grids directly with dictionaries andextrapolation=orboundary=values.
Verified signatures to rely on
Scene.create(parent_directory, shape=(), name='sim', copy_calling_script=True, **dimensions)Scene.write(self, data=dict=None, frame=0, **kw_data)Scene.read(self, *names, frame=0, convert_to_backend=True)field.read(file, convert_to_backend=True)/field.write(field, file)field.resample(value, to, keep_boundary=False, **kwargs)field.sample(field, geometry, at='center', boundary=None, **kwargs)field.reduce_sample(field, geometry, **kwargs)Box(*args, **kwargs)andBox['x,y', ...]geom.Box,geom.Sphere,geom.Cylinder,geom.Mesh,geom.Graph,geom.Heightmap,geom.SDFGrid, andgeom.SDF
Bundled references and helper
- Detailed workflows:
references/workflows.md - Failure handling:
references/troubleshooting.md - Scene round-trip smoke:
scripts/scene_roundtrip.py
From this sub-skill directory, run the smoke helper when you want to verify the field / scene I/O path:
python scripts/scene_roundtrip.py --resolution 16
The helper writes temporary scene data, reads it back through both the scene
API and field.read(), and cleans up afterwards.
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).