KTIMPORTPHYMMBL(1)
π KTIMPORTPHYMMBL π (that's ktImportPhymmBL, manual section 1, User Commands bestie)
β¨ NAME β¨
ktImportPhymmBL β explore hierarchical metagenomic data with zoomable pie charts π₯§π¦
π DESCRIPTION π
Okay so real talk: this little icon makes a Krona chart out of your Phymm or PhymmBL results. Slay.
π¨ Heads up bestie: confidence scores are not given for species/subspecies classifications, so they inherit their confidence scores from the genus classifications. Not me being the messenger, that's just how it is. π
Here's the whole vibe, literally verbatim:
ktImportPhymmBL \
[options] \
phymmbl_results_1[:magnitudes_1][,name_1] \
[phymmbl_results_2[:magnitudes_2][,name_2]] \
...
π the arguments, explained with love
phymmbl_resultsβ your PhymmBL results files (they look likeresults.03.*). They can also come from Phymm all by itself (results.01.*), but then you gotta pass[-p], no exceptions. And by default? Separate datasets get created for each input (peep[-c]if you wanna change that). πmagnitudesβ an optional file listing query IDs with magnitudes, separated by tabs. This is the glow-up for accuracy: use it to account for read length or contig depth so your abundance representation is actually giving what it's supposed to give. By default, query sequences with no specified magnitudes get assigned a magnitude of1. Also!! Magnitude files for assemblies in ACE format can be created withktGetContigMagnitudesπ«Άnameβ a name to show in the list of datasets in the Krona chart (only matters if multiple input files are present and[-c]is not specified). By default, the basename of the file is used. iconic behaviour honestly.
π OPTIONS π
-o <string>β output file name. [Default:'phymm(bl).krona.html'] β¨-n <string>β name of the highest level. [Default:'all'] π-m <number>β minimum confidence. Each query sequence will only be added to taxa that were predicted with a confidence score of at least this value. Gatekeeping, but make it science. π-cβ combine data from each file, rather than creating separate datasets within the chart. Friendship ended with separate datasets, now one dataset is my best friend. π«Ά-d <integer>β maximum depth of wedges to include in the chart. π-x <integer>β hue (0-360) for "bad" scores. [Default:'0'] π-y <integer>β hue (0-360) for "good" scores. [Default:'120'] π₯-pβ input is phymm only (no confidence scores). periodt. π-u <string>β URL of Krona resources to use instead of bundling them with the chart (e.g."http://krona.sourceforge.net"). Reduces size of charts and allows updates, though charts will not work without access to this URL. β οΈ Read that last part again bestie β no URL access, no chart.-qp <string>β url to send query IDs to (instead of listing them) for each wedge. The query IDs will be sent as a comma separated list in the POST variable"queries", with the current dataset index (from0) in the POST variable"dataset". The url can include additional variables encoded via GET. π§ lowkey a whole API moment.
and that's the whole page, no notes, ate and left no crumbs ππΈ
This was ktImportPhymmBL version 2.8, dated June 2021 β shoutout to the source and version for keeping it real, mwah, bye bestie! π¦β¨π
π¦ where this page comes from
- debian bookworm: radiant 2.8.1+dfsg-2 Β· BSD-3-Clause
- debian trixie: radiant 2.8.1+dfsg-2 Β· BSD-3-Clause
- ubuntu jammy: radiant 2.8.1+dfsg-1 Β· BSD-3-Clause
- ubuntu noble: radiant 2.8.1+dfsg-2 Β· BSD-3-Clause
- ubuntu questing: radiant 2.8.1+dfsg-2
- ubuntu resolute: radiant 2.8.1+dfsg-2build1 Β· BSD-3-Clause
- ubuntu stonking: radiant 2.8.1+dfsg-3 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms