Illumina BeadChip Type I vs II Probe Design Class Note Generator
Compare beadchip probe design architectures; does not correct chemistry-specific bias. Bounded exact-key educational reference only; observations and applicability must be established independently.
Description
Compare beadchip probe design architectures; does not correct chemistry-specific bias.
Methylation-array probe designs can use different combinations of probes and color channels. This lookup returns a compact distinction for the named design type.
When to use this tool
Compare beadchip probe design architectures; does not correct chemistry-specific bias.
- 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 "I", "II". 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. | "I", "II" |
| 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": "I"
},
"output": {
"result": {
"reference": "Infinium Type I uses two probes per CpG and a single color per locus."
}
}
}Limitations and assumptions
- The tool does not read array intensities, normalize channels or identify a probe's design from an ID. Only its exact supported type keys are accepted.
- 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
- BigWig Zoom-Level Pyramid Storage Note Generator
Explain BigWig multiresolution storage without reading a file.
- CUT&RUN Low-Read-Depth Suitability Advantage Note Generator
Explain conditional CUT&RUN low-background advantages without guaranteeing low-read sufficiency.