BEDMAP(1)

πŸ“¦
version 2.4.42 Β· 5 versions
, in ubuntu resolute, ubuntu stonking

🌸 bedmap(1) β€” the manual page for bedmap 🌸

okay bestie, sit down, hydrate, and let me tell you about bedmap β€” it's a User Command, it lives in section 1 of the manual, and this is the manual page for bedmap 2.4.42+dfsg. πŸ’–


✨ NAME ✨

bedmap β€” manual page for bedmap 2.4.42+dfsg. That's it, that's the name, short and iconic. πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

bedmap πŸ’…

citation:

version: 2.4.42 (typical)

authors: Shane Neph & Scott Kuehn 🫢 (yes, two whole authors, we love a collab)

USAGE: bedmap [process-flags] [overlap-option] <operation(s)...>
<ref-file> [map-file]

So here's the tea β˜• β€” any input file must be sorted per the sort-bed utility. The program accepts BED and Starch file formats. You may use '-' for a BED file to indicate the input comes from stdin. πŸŽ€

It traverses <ref-file>, while applying <operation(s)> on qualified, overlapping elements from <map-file>.

Output is one line for each line in <ref-file>, sent to standard output. There

is no limit on the number of operations you can specify to compute in one bedmap call. 🌈

If <map-file> is omitted, the given file is treated as both the <ref-file> and <map-file>. This usage is more efficient than specifying the same file twice. πŸ”₯

Arguments may be given in any order before the input file(s). Slay, flexible queen. πŸ’…


πŸŽ€ Process Flags πŸŽ€

bestie this is the whole list, no skipping, we're eating the whole plate πŸ“
  • --chrom <chromosome> β€” Jump to and process data for given <chromosome> only. One chromosome, main character energy. πŸ‘‘
  • --delim <delim> β€” Change output delimiter from '|' to <delim> between columns (e.g. '\t').
  • --ec β€” Error check all input files (slower). Thorough but it's giving... slow. 😭
  • --faster β€” (advanced) Strong input assumptions are made. Compatible with: --bp-ovr, --range, --fraction-both, and --exact overlap options only.
  • --header β€” Accept headers (VCF, GFF, SAM, BED, WIG) in any input file.
  • --help β€” Print this message and exit successfully. 🫢
  • --min-memory β€” Minimize memory usage (slower).
  • --multidelim <delim> β€” Change delimiter of multi-value output columns from ';' to <delim>.
  • --prec <int> β€” Change the post-decimal precision of scores to <int>. 0 <= <int>.
  • --sci β€” Use scientific notation for score outputs. nerd mode activated 🧚
  • --skip-unmapped β€” Print no output for a row with no mapped elements.
  • --sweep-all β€” Ensure <map-file> is read completely (helps to prevent broken pipes).
  • --unmapped-val <val> β€” Print <val> on unmapped --echo-map* and --min/max-element* operations. The default is to print nothing.
  • --version β€” Print program information.

πŸ’œ Overlap Options πŸ’œ

At most, one may be selected. By default, --bp-ovr 1 is used. One. Pick one. This is not a build-your-own-sundae situation. πŸ“
  • --bp-ovr <int> β€” Require <int> bp overlap between elements of input files.
  • --exact β€” First 3 fields from <map-file> must be identical to <ref-file>'s.
  • --fraction-both <val> β€” Both --fraction-ref <val> and --fraction-map <val> must be true to qualify as overlapping. Expect 0 < val <= 1.
  • --fraction-either <val> β€” Either --fraction-ref <val> or --fraction-map <val> must be true to qualify as overlapping. Expect 0 < val <= 1.
  • --fraction-map <val> β€” The fraction of the element's size from <map-file> that must overlap the element in <ref-file>. Expect 0 < val <= 1.
  • --fraction-ref <val> β€” The fraction of the element's size from <ref-file> that must overlap an element in <map-file>. Expect 0 < val <= 1.
  • --range <int> β€” Grab <map-file> elements within <int> bp of <ref-file>'s element, where 0 <= int. --range 0 is an alias for --bp-ovr 1.

⭐ Operations ⭐

(Any number of operations may be used any number of times.) Go off, bestie, stack 'em. πŸ’…

πŸ”₯ SCORE πŸ”₯

<ref-file> must have at least 3 columns and <map-file> 5 columns.
  • --cv β€” The result of --stdev divided by the result of --mean.
  • --kth <val> β€” Generalized median. Report the value, x, such that the fraction <val> of overlapping elements' scores from <map-file> is less than x, and the fraction 1-<val> of scores is greater than x. 0 < val <= 1.
  • --mad <mult=1> β€” The median absolute deviation of overlapping elements in <map-file>. Multiply mad score by <mult>. 0 < mult, and mult is 1 by default.
  • --max β€” The highest score from overlapping elements in <map-file>. πŸ‘‘
  • --max-element β€” A (non-random) highest-scoring and overlapping element in <map-file>.
  • --max-element-rand β€” A random highest-scoring and overlapping element in <map-file>.
  • --mean β€” The average score from overlapping elements in <map-file>.
  • --median β€” The median score from overlapping elements in <map-file>.
  • --min β€” The lowest score from overlapping elements in <map-file>.
  • --min-element β€” A (non-random) lowest-scoring and overlapping element in <map-file>.
  • --min-element-rand β€” A random lowest-scoring and overlapping element in <map-file>.
  • --stdev β€” The square root of the result of --variance.
  • --sum β€” Accumulated scores from overlapping elements in <map-file>.
  • --tmean <low> <hi> β€” The mean score from overlapping elements in <map-file>, after ignoring the bottom <low> and top <hi> fractions of those scores. 0 <= low <= 1. 0 <= hi <= 1. low+hi <= 1.
  • --variance β€” The variance of scores from overlapping elements in <map-file>.
  • --wmean β€” Weighted mean, scaled in proportion to the coverage of the <ref-file> element by each overlapping <map-file> element.

πŸ¦‹ NON-SCORE πŸ¦‹

Here's the column tea, bestie: <ref-file> must have at least 3 columns. For --echo-map-id/echo-map-id-uniq, <map-file> must have at least 4 columns. For --echo-map-score, <map-file> must have at least 5 columns. For all others, <map-file> requires at least 3 columns.
  • --bases β€” The total number of overlapping bases from <map-file>.
  • --bases-uniq β€” The number of distinct bases from <ref-file>'s element covered by overlapping elements in <map-file>.
  • --bases-uniq-f β€” The fraction of distinct bases from <ref-file>'s element covered by overlapping elements in <map-file>.
  • --count β€” The number of overlapping elements in <map-file>.
  • --echo β€” Print each line from <ref-file>.
  • --echo-map β€” List all overlapping elements from <map-file>.
  • --echo-map-id β€” List IDs from all overlapping <map-file> elements.
  • --echo-map-id-uniq β€” List unique IDs from overlapping <map-file> elements.
  • --echo-map-range β€” Print genomic range of overlapping elements from <map-file>.
  • --echo-map-score β€” List scores from overlapping <map-file> elements.
  • --echo-map-size β€” List the full length of every overlapping element.
  • --echo-overlap-size β€” List lengths of overlaps.
  • --echo-ref-name β€” Print the first 3 fields of <ref-file> using chrom:start-end format.
  • --echo-ref-row-id β€” Print 'id-' followed by the line number of <ref-file>.
  • --echo-ref-size β€” Print the length of each line from <ref-file>.
  • --indicator β€” Print 1 if there exists an overlapping element in <map-file>, 0 otherwise.

πŸ’– SEE ALSO πŸ’–

The full documentation for bedmap is maintained as a Texinfo manual. If the info and bedmap programs are properly installed at your site, the command

info bedmap

should give you access to the complete manual. πŸ“–βœ¨


okay that's the whole thing, you ate that, go forth and map your beds πŸ’…

sign-off: this was bedmap 2.4.42+dfsg, dated August 2025, section BEDMAP(1) β€” mwah, ily, bye 🫢🌸

πŸ“¦ where this page comes from