Description
Count expected stack positions with at least one supplied slice within an explicit tolerance; no reconstruction.
An image grid has array indices as well as physical spacing, timing, and signal conventions. A calculation on supplied metadata describes one part of that grid or signal; it does not inspect an image, validate a complete file, or interpret anatomy.
Count expected stack positions with at least one supplied slice within an explicit tolerance; no reconstruction.
When to use this tool
Use it for scan stack support share when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter slicePositions, expectedPositions, tolerance. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read expectedSlices, matchedExpectedSlices, share, defined. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require nonnegative tolerance and unique expected positions. Count each expected position as supported when any supplied slice position differs by at most tolerance; divide supported positions by expected count.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| slicePositions | Slice Positions | Required. Array of Finite number.; maximum items 256. |
| expectedPositions | Expected Positions | Required. Array of Finite number.; maximum items 256. |
| tolerance | Nonnegative absolute tolerance in the quantity tested, unless the mechanics state a different convention. | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| expectedSlices | Expected Slices | Required. Safe integer. |
| matchedExpectedSlices | Matched Expected Slices | Required. Safe integer. |
| share | Dimensionless fraction using the denominator described above; not a percentage numeral. | Required. Finite number. |
| defined | Whether the associated denominator or quantity is defined; read this before interpreting a zero placeholder. | Required. Boolean. |
{
"input": {
"slicePositions": [
0,
2
],
"expectedPositions": [
0,
1,
2
],
"tolerance": 0
},
"output": {
"expectedSlices": 3,
"matchedExpectedSlices": 2,
"share": 0.6666666666666666,
"defined": true
}
}Limitations and assumptions
- One supplied slice may support multiple expected positions. An empty expected list returns share zero with defined false; this is not a one-to-one slice assignment or a reconstruction completeness certificate.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For scan stack support share, check the source records and the supplied rule before comparing the result with another method. Use a full image reader and geometry or signal analysis when the task requires interpreting image data.
References
Similar or alternative tools
- Acquisition Time Offset Precision Flag
Preserve a truncated timestamp quantum and offset-known flag; unknown UTC values use flagged zero placeholders.
- Ct Number Water Reference Gap
Subtract a supplied additive water-reference HU offset, without inferring tissue type or calibrating a full attenuation scale.