Multi-Cycle vs Single-Step MOI Regime Classifier
Compare MOI with an independently chosen design boundary; replication-cycle regime also depends on timing and host conditions.
Description
Compare MOI with an independently chosen design boundary; replication-cycle regime also depends on timing and host conditions.
An MOI-based regime screen compares a supplied inoculation ratio with a chosen threshold. It is only one condition in establishing whether an experiment behaves as a single-step or multicycle system.
When to use this tool
Compare MOI with an independently chosen design boundary; replication-cycle regime also depends on timing and host conditions.
- Prepare the supplied moi, callerSingleStepMinimum 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 moi, callerSingleStepMinimum. 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.regimeScreen, result.experimentDesignConfirmed. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require nonnegative moi and positive callerSingleStepMinimum. At or above the minimum, return high-moi-single-step-candidate; below it return low-moi-multicycle-candidate. Always set experimentDesignConfirmed false.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| moi | moi. | Finite number; zero or greater |
| callerSingleStepMinimum | caller single step minimum. | Finite number; greater than zero |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.regimeScreen | The regime screen value under the stated formula or text convention. |
| result.experimentDesignConfirmed | Flag for experiment design confirmed under the exact condition described above. |
{
"input": {
"moi": 5,
"callerSingleStepMinimum": 3
},
"output": {
"result": {
"regimeScreen": "high-moi-single-step-candidate",
"experimentDesignConfirmed": false
}
}
}Limitations and assumptions
- No universal threshold is supplied. Adsorption, cell susceptibility, timing and secondary spread are not assessed, and the screen does not validate an experiment or predict its growth curve.
- 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
Keep physical-particle counts, infectious assay units and observed sample proportions distinct. Use the original calibration, product instructions or validated assay method for the specific context; simple conversions and reference notes do not establish infectivity or clinical interpretation.
References
Similar or alternative tools
- Capsid Symmetry Type Classifier (icosahedral/helical/complex)
Decode independently established capsid symmetry.
- cells for inoculum moi
Calculate the cell count implied by a PFU inoculum and a target nominal multiplicity of infection.