HMMER result-table export
Export every HMMER3 protein-table hit with query and target accessions, original numeric tokens, free-text descriptions and exact source byte spans.
- 1Add input
- 2Adjust settings
- 3Get your result
Tool input and files are processed in this browser without being uploaded.
Before you start
Choose the producing program and table type, then inspect complete hits without rerunning HMMER or changing statistical tokens.
How to use this tool
- Choose tblout/domtblout and the actual producing program; paste or select one complete file.
- Check accessions, descriptions and domain coordinate roles; an empty hit table is distinct from a parse error.
- Download complete report.json, records.csv and original.txt.
Supported inputs and limits
One10MiB UTF-8 protein HMMER3 tblout or domtblout;100,000 hit records;300,000 physical lines;65,536 bytes per physical line. Complete original+JSON+CSV must fit48MiB. Budgets apply together.
Explicit hmmscan/hmmsearch/phmmer and18/22-field table profiles. Header program/version contradictions, HMMER2/nhmmer, fixed-field TAB, Unicode-space identifiers and ambiguous hash-prefixed target rows are Unsupported. ASCII spaces separate fixed fields; TAB and Unicode within descriptions remain intact.
All numerical lexical tokens, including tiny E-values, remain text. No float64 score/E-value recomputation. Raw domain coordinates stay1-based inclusive with program-specific query/target roles. Reported and included domain counts each must not exceed observed domains; they are not ordered against one another.
Complete JSON includes every hit/comment and UTF-8 line/description byte spans; original.txt preserves BOM and LF/CRLF. CSV protects formula-like text with a marked leading apostrophe; raw JSON/source values remain unchanged.
Preview and copy contain at most200 rows/2,000 UTF-16 units per long table cell; above20,000 units the copied report is a compact preview. Full JSON, CSV and original downloads remain complete. All output limits are combined and enforced atomically.
Worked example
Example input
# Program: hmmscan # Version: 3.1b2 t1 TA1 q1 QA1 1e-9 20.2 0.0 1e-8 18.1 0.0 1.0 1 1 0 1 1 1 1 long description, "quoted" 中文
Example options
{"params":{"format":"tblout","program":"hmmscan"}}Example output
{"schemaVersion":1,"program":"hmmscan","format":"tblout","columns":["targetName","targetAccession","queryName","queryAccession","evalue","score","bias","bestDomainEvalue","bestDomainScore","bestDomainBias","expectedDomains","regions","clusters","overlaps","envelopes","domains","reportedDomains","includedDomains"],"records":[{"line":3,"span":[36,130],"tokens":["t1","TA1","q1","QA1","1e-9","20.2","0.0","1e-8","18.1","0.0","1.0","1","1","0","1","1","1","1"],"description":"long description, \"quoted\" 中文","descriptionSpan":[96,130]}],"comments":[{"line":1,"span":[0,18]},{"line":2,"span":[19,35]}],"coordinateMeaning":null,"csvTextSafety":"Only textual identifiers/description prefix apostrophe for formula-sign starters; numeric tokens were strictly validated and preserved."}When something does not work
Check the selected profile and the original source, then correct the input or reduce complete input/output size. Cancellation and errors publish no partial files; rerun the same supported source.
Frequently asked questions
Are very small E-values rounded?
No. Their original lexical tokens remain intact; importing CSV into another program may reinterpret them.
Does this judge biological significance?
No. It reads the declared result table and does not run HMMER, recompute significance or certify biological conclusions.