Skip to content

Main content

FASTA Header Accession Split

Split one FASTA definition line into the first whitespace-delimited identifier and remaining literal description without resolving an accession registry.

Loading tool…

Description

Split a supplied FASTA header into accession and description text.

Sequence formats distinguish coordinate origins, included endpoints, allele separators and identifier grammars. A genomic interbase position differs from a base number, and a parsed optional-field value may still violate its declared type. Local token checks preserve representation without validating a complete file, sequence, reference assembly or biological interpretation.

Split a supplied FASTA header into accession and description text.

When to use this tool

Use FASTA Header Accession Split when you already have header and need to split a supplied FASTA header into accession and description text.

How to use the tool and how it works

  1. Enter header. 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 accession, description. Use the output convention below.

Require a leading >, a nonwhitespace accession and no CR/LF. Accept optional space/tab-delimited description and return an empty description if absent.1

Input fieldMeaning and unitsAccepted input
headerHeaderRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
accessionAccessionRequired. Text; maximum UTF-16 length 8192.
descriptionDescriptionRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "header": ">SEQ17 sample description"
  },
  "output": {
    "accession": "SEQ17",
    "description": "sample description"
  }
}

Limitations and assumptions

  • Whitespace is not a universal FASTA database grammar. Description text is retained rather than parsed; no accession resolution, sequence or complete file validation occurs.
  • 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.

Alternative or Complementary methods

Use the complete applicable file specification and a full format validator for conformance. Verify reference assembly, sequence bounds, annotation and database context before interpreting local fields or coordinate transformations.

References

  1. Calculation and input contract: bioinformatics/fasta-header-accession-split — tool.io

Similar or alternative tools