CNVKIT_BINTEST(1)

πŸ“¦
version 0.9.13 Β· 3 versions
, in debian trixie, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– CNVKIT_BINTEST(1) πŸ’–

okay bestie, welcome to cnvkit_bintest β€” it's a User Command, it lives in section 1 of the manual, and it is literally the "Test for single-bin copy number alterations." vibe. no cap. 🧚


✨ NAME ✨

cnvkit_bintest β€” Test for single-bin copy number alterations.


🌸 DESCRIPTION 🌸

so the way this works is, you run it like this:

usage: cnvkit.py bintest [-h] [-s FILENAME] [-a ALPHA] [-t] [-o OUTPUT]

       cnarray

that's the whole shape of it. <lavender>cnarray</lavender> is the main character here, everything else is optional garnish. πŸŽ€

🌈 positional arguments 🌈

  • cnarray β€” this is your bin-level log2 ratios file, a .cnr file, and it's gotta be the kind that comes out of the fix command. that's the whole point, that's what we're testing. πŸ’…

πŸ¦‹ options πŸ¦‹

  • -h, --help β€” shows you this help message and then dips. classic. shows help, exits, we love a clean exit. ✨
  • -s FILENAME, --segment FILENAME β€” your segmentation calls, a .cns file, aka the output of the segment command. that's where these calls came from, iykyk. πŸ“
  • -a ALPHA, --alpha ALPHA β€” the significance threshold. [Default: 0.005] β€” yeah, that's the default, she's strict. πŸ‘‘
  • -t, --target β€” test target bins only, and just straight up ignore the off-target bins. like, not even a glance. πŸ™ˆ
  • -o OUTPUT, --output OUTPUT β€” output filename. give your results a name, they deserve one. πŸ’œ

ngl bestie, -a is spelled "threhold" in the original and honestly? iconic of it. we keep it, we don't fix it, we simply respect the typo. πŸ’€

πŸ’« SEE YA πŸ’«

that's the whole page, fr fr. this gorgeous thing is cnvkit.py bintest 0.9.10, dated July 2023, and it signs off as CNVKIT_BINTEST(1). periodt. πŸ«ΆπŸ’–

πŸ“¦ where this page comes from