PATHSUM(nged)

shared path-evaluation command related to paths and listeval

πŸ“… published 7.44.0, from nixpkgs unstable

Hii bestie! Welcome to the PATHSUM(nged) page from the BRL-CAD User Commands set πŸ’– This is the shared path-evaluation moment, and we're gonna make it make sense.

✨ NAME ✨

pathsum β€” shared path-evaluation command related to paths and listeval 🫢

🌈 SYNOPSIS 🌈

pathsum {path}

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so the pathsum implementation is shared by three related commands, and they are a whole little trio: pathsum, paths, and listeval πŸ‘‘.

All three commands accept a model path specified either as slash-separated components or as space-separated components β€” but not both in the same invocation. Pick one separator style per invocation, bestie πŸ’….

Vibe check: slash-separated components or space-separated components, never both in the same invocation. No mixing, no chaos β€” periodt.

For interactive use, paths is usually the best choice when the goal is to enumerate all primitive paths below a starting point 🌈. And listeval is the best choice when the goal is to print the fully evaluated leaf primitive parameters for a path ✨.

The shared implementation also recognizes the -t option when invoked as listeval πŸ‘€. That option requests a terse primitive report for shapes with long parameter lists, such as BoTs 🫢.

  • -t β€” when the command is invoked as listeval, request a terse primitive report for shapes with long parameter lists, such as BoTs.

πŸŽ€ EXAMPLES πŸŽ€

Example 1. Use the shared path-evaluation logic through listeval for a terse report.

mged>listeval -t vehicle.r/turret.r/bolt.s

Evaluates the full transform stack along the specified path and prints a concise description of the resulting primitive πŸ’–.

Example 2. Enumerate all leaf paths below a subassembly.

mged>paths vehicle.r/turret.r

Lists every primitive path that begins at vehicle.r/turret.r, which is useful before selecting one specific path for listeval or copyeval ✨.

πŸ‘‘ AUTHOR πŸ‘‘

BRL-CAD Team 🫢

πŸ’€ BUG REPORTS πŸ’€

Reports of bugs or problems should be submitted via electronic mail to devs@brlcad.org πŸ“¬.


Catch you in the group chat, bestie β€” footer vibes: source/version BRL-CAD, manual PATHSUM(nged), mwah πŸ’‹πŸŽ€

πŸ“¦ where this page comes from