executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
runtime-and-custom-opsSet up and diagnose the legacy TensorFlow runtime and PointNet++ custom operators used by Frustum PointNets.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this route for installation, version compatibility, TensorFlow graph-mode imports, CUDA/toolkit decisions, and the custom operators used by the v2 model. It is deliberately conservative: the repository is a Python-2/early-TensorFlow release, not a modern pip package.
python scripts/check_legacy_runtime.py --json.Read compatibility for version choices and custom operators for build and load checks. Read troubleshooting whenever an import or loader fails.
models/pointnet_util.py imports sampling, grouping, and 3D-interpolation
wrappers. Their Python modules call tf.load_op_library on local shared
objects, so v2 cannot be treated as a pure-Python CPU workflow. Build and test
operators in an isolated copy, discover TensorFlow's include/library paths
from the selected environment, and never paste machine-specific paths from an
old shell script into a reusable setup.
Verify in this order: Python/TensorFlow import, graph-mode placeholder/session
smoke, framework device listing, compiler/toolkit visibility, one operator
load smoke, then the native op tests. Stop at the first failed gate. The
current generated skill has verified only the CPU graph smoke; CUDA and the
old custom-op ABI remain explicitly unverified. Route data preparation to
../kitti-data-preparation/SKILL.md, training to ../training/SKILL.md, and
KITTI scoring to ../inference-and-evaluation/SKILL.md.