MASH-SCREEN(1)
β¨ MASH-SCREEN(1) β¨
okay bestie, welcome to mash-screen β the section of the mash manual (yes, that's mash(1), we'll get there) that answers the big question: π
is this lil query sequence actually IN this giant pool of sequences, or is it just cosplaying?
πΈ NAME πΈ
mash-screen β figure out whether your query sequences are hanging out inside a bigger pool of sequences. are they in the group chat or not, fr fr. π«Ά
π¦ SYNOPSIS π¦
mash screen [options] <queries>.msh <pool> [<pool>] ...
π DESCRIPTION π
So here's the tea. This command determines how well your query sequences are contained within a pool of sequences. β¨
Your queries must be formatted as a single Mash sketch file (.msh), and you gotta make it with the mash sketch command first. No shortcuts, bestie, it's giving "prerequisite." π
The <pool> files though? Those can be literally whatever:
- contigs or reads
- fasta or fastq
- gzipped or not
- and you can even pass
-for<pool>to read from standard input π
The <pool> sequences are assumed to be nucleotides, and they'll be 6-frame translated if your <queries> are amino acids. (yes, it just knows. iconic behavior.)
The output fields are:
[identity, shared-hashes, median-multiplicity, p-value, query-ID, query-comment]
and median-multiplicity is computed for shared hashes, based on how many times those hashes showed up within the pool. that's the whole vibe check. π
π OPTIONS π
-hβ Help. the classic. when in doubt, ask for help, no shame in it. π«Ά-p <int>β Parallelism. This many threads will be spawned for processing. it's giving main character energy, multiplied β more threads, more speed. π₯-wβ Winner-takes-all strategy for identity estimates. π So here's how it goes: after counting hashes for each query, hashes that appear in multiple queries get removed from all except the one with the best identity (and ties get broken by the larger query), and then the other identities get reduced. This removes output redundancy and gives you a rough compositional outline. survival of the fittest hash, periodt.
π Output π
-i <num>β Minimum identity to report. It's inclusive unless you set it to zero, in which case only identities greater than zero get reported (i.e. only ones with at least one shared hash). And if you set it to-1, it'll output everything. everything. all of it. no filter. π-v <num>β Maximum p-value to report. that's it, that's the setting. π
π SEE ALSO π
mash(1)β the parent manual, the source of all lore, go read it bestie π
π reminder, because it matters: the queries have to be a single.mshsketch file made withmash sketch. if you show up with anything else it's not gonna work, and that's not me being mean, that's just the rules. π
k byeeee, this was mash-screen(1) from the mash manual, dated 2019-12-13. go slay your containment analysis, bestie, you've got this πβ¨ππ¦πΈπ
π¦ where this page comes from
- debian bookworm: mash 2.3+dfsg-3+b1 Β· BSD-3-Clause
- debian trixie: mash 2.3+dfsg-6+b2 Β· BSD-3-Clause
- ubuntu jammy: mash 2.3+dfsg-1build2 Β· BSD-3-Clause
- ubuntu noble: mash 2.3+dfsg-6 Β· BSD-3-Clause
- ubuntu questing: mash 2.3+dfsg-6build2
- ubuntu resolute: mash 2.3+dfsg-6build3 Β· BSD-3-Clause
- ubuntu stonking: mash 2.3+dfsg-6build4 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms