Skip to content

Main content

BED Twelve Block Relative Start Term Tool

One BED12 block uses a zero-based offset relative to chromStart and a half-open absolute interval.

Loading tool…

Description

Return one BED block's absolute half-open bounds.

Genome annotations depend on coordinate origin, endpoint inclusion, strand and reading-phase conventions. A local offset or phase token can be handled precisely while a complete transcript, reference identity and biological reading frame remain separate validation questions.

Return one BED block's absolute half-open bounds.

When to use this tool

Use BED Twelve Block Relative Start Term when checking the stated genomic coordinate, annotation phase or attribute-value convention.

How to use the tool and how it works

  1. Enter chromStart, chromEnd, blockStart, blockSize. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read absoluteStart, absoluteEnd. Use the output convention below.

Return one BED block's absolute half-open bounds. Require nonnegative whole chromStart, blockStart, blockSize, chromEnd >= chromStart and block end <= chromEnd; add relative blockStart to chromStart.1

BED uses a zero-based start and an excluded end; block starts are relative to the enclosing chromosome start. The complete record has additional constraints.2

Input fieldMeaning and unitsAccepted input
chromStartChrom StartRequired. Safe integer; minimum 0.
chromEndChrom EndRequired. Safe integer.
blockStartZero-based start relative to chromStart, not an absolute chromosome position.Required. Safe integer; minimum 0.
blockSizeBlock SizeRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
absoluteStartAbsolute StartRequired. Safe integer.
absoluteEndAbsolute EndRequired. Safe integer.
json
{
  "input": {
    "chromStart": 100,
    "chromEnd": 200,
    "blockStart": 20,
    "blockSize": 30
  },
  "output": {
    "absoluteStart": 120,
    "absoluteEnd": 150
  }
}

Limitations and assumptions

  • Zero-size blocks are accepted; this does not validate all twelve BED fields, block ordering, overlap or reference identity.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use the intended complete BED/GFF/GTF format, reference assembly and transcript model to validate full annotations and biological meaning.

References

  1. Calculation and input contract: bioinformatics/bed-twelve-block-relative-start-term — tool.io

  2. Genome Browser data file formats: BED — UCSC Genome Browser

Similar or alternative tools