KTIMPORTKRONA(1)
β¨ NAME β¨
ktImportKrona β bestie, this is the one that lets you explore hierarchical metagenomic data with zoomable pie charts π (section 1 of the manual, filed under User Commands, iykyk)
πΈ DESCRIPTION πΈ
Okay so here's the tea: ktImportKrona creates a Krona chart from the data in other Krona charts. Charts in, chart out. Iconic behavior honestly π
π how you actually call it
ktImportKrona \
[options] \
krona_chart_1[:magnitudes_1][,name_1] \
[krona_chart_2[:magnitudes_2][,name_2]] \
...
π¦ the arguments, explained with love
krona_chartβ a Krona HTML file that was created with KronaTools or the Krona Excel Template. By default, separate datasets will be created for each input (see[-c]). So yeah, one file in, one lil dataset out, unless you tell it otherwise πmagnitudesβ optional file listing query IDs with magnitudes, separated by tabs. This can be used to account for read length or contig depth to obtain a more accurate representation of abundance. By default, query sequences without specified magnitudes will be assigned a magnitude of1. Magnitude files for assemblies in ACE format can be created withktGetContigMagnitudes. Slay, accurate abundance β¨nameβ a name to show in the list of datasets in the Krona chart (this only matters if multiple input files are present and[-c]is not specified). By default, the basename of the file will be used. No name-picking stress required, it handles it π
π OPTIONS π
-o <string>β output file name. [Default:'krona.krona.html'] β yes, the default really is that gloriously redundant, we love her π-n <string>β name of the highest level. Give your chart's top tier a title, main character energy π-cβ combine data from each file, rather than creating separate datasets within the chart. One big beautiful dataset instead of a little collection π«Ά-d <integer>β maximum depth of wedges to include in the chart. Depth check, literally π-x <integer>β hue (0-360) for "bad" scores. Sad vibes get a color of your choosing π-y <integer>β hue (0-360) for "good" scores. Good vibes get a color too β-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.
π¨ bestie listen: it does shrink your charts and let you get updates, but if that URL isn't reachable, the chart is not working. No cap. Trade-off is real π
-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.
π okay this one is kinda the coolest: instead of dumping all the query IDs into the wedge, it POSTs them off somewhere."queries"gets the comma separated list,"dataset"gets the dataset index counting from0, and you can sneak extra GET variables into the url itself. iykyk πΈ
and that's the whole page, bestie!! π β¨
this gorgeous little manual is for ktImportKrona version 2.8, dated June 2021 β shoutout to the KronaTools crew for feeding us, and that's a wrap ππ¦ππ
π¦ 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