Narrow versus Broad Peak Caller Selection Guide by Mark Lookup
Retrieve a restricted peak-geometry caller-selection guide without processing reads. Bounded exact-key educational reference only; observations and applicability must be established independently.
Description
Retrieve a restricted peak-geometry caller-selection guide without processing reads.
Peak-calling choices depend partly on whether enrichment is localized or extended. A short reference can distinguish the intended signal shape before a caller is chosen.
When to use this tool
Retrieve a restricted peak-geometry caller-selection guide without processing reads.
- Prepare the supplied key fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter key. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.reference. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Supply key exactly as one of "sharp", "diffuse". Check for that own key in the fixed local table and return its stored reference text unchanged. An unsupported key is an input error, rather than a null result; there is no network request, fuzzy matching or dynamic text generation.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| key | Exact stored-entry key; spelling and case must match. | "sharp", "diffuse" |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.reference | The unchanged stored text for the supported exact key; unsupported keys cause an input error. |
{
"input": {
"key": "sharp"
},
"output": {
"result": {
"reference": "Narrow-peak calling is commonly appropriate for localized enrichment such as many transcription factors or H3K4me3, subject to assay context."
}
}
}Limitations and assumptions
- The lookup does not run a peak caller, choose parameters or assess control data. The stored broad/narrow guidance remains conditional on assay and target context.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Interpret computational summaries alongside assay controls and the original experimental evidence. A mark association, charge model or threshold flag does not independently establish a chromatin state, causal mechanism or transcriptional effect.
References
Similar or alternative tools
- Bromodomain Acetyl-Lys Reader Domain Specificity Table Lookup
Look up caller-supplied reference text by an exact reader protein and acetyl mark key, retaining source, context and date without independently verifying the evidence.
- Chromodomain Methyl-Lys Reader Specificity Table Lookup
Look up caller-supplied reference text by an exact reader protein and methyl mark key, retaining source, context and date without independently verifying the evidence.