SUMMARY(nged)

The summary command with no arguments lists the number of primitive shapes, regions, and nonregion combinations in the current database.

πŸ“… published 7.44.0, from nixpkgs unstable

πŸ’… SUMMARY(nged) β€” the glow-up

Okay bestie, welcome to the summary page from the BRL-CAD MGED Commands manual. This one's short and sweet, so grab your iced coffee and let's go ✨

🌸 NAME

summary β€” so like, when you run it with no arguments at all, it lists the number of primitive shapes, regions, and nonregion combinations in the current database. That's it. That's the vibe check. πŸ’–

πŸ¦‹ SYNOPSIS

summary
summary [prg]*
summary [-o | --obj] {object}

✨ DESCRIPTION

No arguments? Iconic. summary lists the number of primitive shapes, regions, and non-region combinations in the current database. Simple, clean, slay.

Now for the lore 🫢 β€” the historical single-token letters p, r, and g are still supported for reporting primitives, regions, and/or groups. You can concatenate them to request combined listing(s) of primitive names, region names, and combination names respectively. Old-school but still ate. πŸ’€

Modern usage can also summarize one specific database object β€” either by naming it directly as the lone argument, or by supplying -o or --obj. Main character energy fr fr. πŸ‘‘


πŸŽ€ OPTIONS

  • -h, -?, --help β€” print help and exit. Respectful, efficient, we love to see it. πŸ™ˆ
  • -o, --obj name β€” summarize the named database object. Just the one. Giving it all the attention. πŸ’…

🌈 EXAMPLES

The example shows the use of the summary command with an argument to list a summary of primitive shapes and regions for the current database.

Example 1. List a summary of primitive shapes and regions for the current database.

mged>summary pr

Lists a summary of primitive shapes and regions for the current database. (See? p and r concatenated β€” the historical letters said "hey" 😌)

Example 2. Summarize one object explicitly.

mged> summary --obj turret.r

Reports the summary information for turret.r. Obsessed with how specific this is. ⭐


πŸ‘‘ AUTHOR

BRL-CAD Team β€” legends, honestly.

πŸ“ BUG REPORTS

Reports of bugs or problems should be submitted via electronic mail to devs@brlcad.org. Don't be shy, they literally asked. πŸ’Œ


And that's the whole page, bestie β€” no cap, every flag and every name made it in intact 🧚

Brought to you by BRL-CAD, and yes the footer said SUMMARY(nged) β€” mwah, bye! πŸ’œ

πŸ“¦ where this page comes from