USAGE:(1)

πŸ“¦
version 9.34.13 Β· 2 versions
, in fedora 43

πŸ’– NAME πŸ’–

usage: β€” osh_part (yes the name literally has a colon in it, we love a quirky queen πŸ‘‘)


✨ DESCRIPTION ✨

okay bestie so listen, osh_part is that girl. she takes your .osh files and does her thing, and she has a whole roster of flags to play with. here's the vibe:

usage: osh_part [options] options:

no cap, that's the actual line. moving on to the iconics πŸ’…

πŸŽ€ the options (aka her little accessories) πŸŽ€

  • --osh-memory β€” prints the amount and the stacktrace of max memory use. she's nosy about your RAM, respectfully 🫢
  • --osh-time β€” prints how much time got spent in certain functions. clocking the tea ⏱️
  • --osh-time-percent β€” same as above but as a percentage. math girl era πŸ”₯
  • --osh-time-chop 0.0 β€” only prints functions whose percent time is greater than the value you give. like, e.g. --osh-time-chop=2. filters out the low-key irrelevant ones, periodt ✨
  • --osh-time-with-filename β€” adds the file name to the function name in the profile output. receipts included, iykyk 🧾
  • --osh-signal β€” catches signals and prints a stacktrace. she catches everything πŸ’€
  • --osh-fpe β€” enables floating-point exceptions. drama on purpose, we support it πŸ’…
  • --osh-silent β€” suppresses all output. the silent treatment, but make it a feature πŸ™ˆ
  • --osh-pool β€” uses memory pooling. sharing is caring, babe 🌸
  • --osh-self-send value β€” controls the self send threshold. main character boundaries βœ‹
  • --osh-mpi-ranks-per-node value β€” mpi ranks per node (for CUDA+MPI). big parallel energy, no cap 🌈

and then, when you're done picking accessories, the actual run looks like:

usage: osh_part in.osh <nparts> out.osh
fr fr β€” that's the whole page. don't come for me, that's literally all the original gave us πŸ’–

~ cute sign-off ~ πŸ¦‹ this page's footer told us it was rockin' with usage: osh_part in.osh <nparts>..., stamped July 2025, and filed under the manual name USAGE:(1). slay, bye bestie πŸ’œβœ¨

πŸ“¦ where this page comes from