Calculation boundary and execution
Acadnix calculator engines are pure application functions separated from their browser forms. The form gathers labelled inputs, the engine validates and calculates, and the result panel explains the output. The current application performs this work in the browser and does not send calculator values to an Acadnix backend or database.
A calculator must represent the page's stated intent. Reusing a convenient engine is not acceptable when the form omits a material input or the output answers a different question.
Validation before arithmetic
Inputs should be rejected when they are missing, non-finite, negative where impossible, outside a stated scale, inconsistent with each other, or likely to create a zero denominator. Reconciliation checks are required where totals must agree, such as correct plus incorrect answers not exceeding total questions.
- Keep units visible and do not mix percentages, marks, credits, minutes, or dates without conversion.
- Show unreachable targets as unreachable instead of returning a plausible-looking number.
- Preserve user-selected eligibility rows, weights, scales, and assumptions beside the answer.
- Treat an invalid or conflicting record as an error to resolve, not as zero.
Weighting, precision, and dates
Weighted calculations use the entered contribution and its matching weight or credits; unlike denominators must not be averaged as if they were equal. Working precision should be retained through dependent steps and rounded for display at the documented output stage so repeated rounding does not silently change the result.
Calendar tools must state whether a boundary is included and avoid time-zone drift when converting date-only inputs. Projections report scenarios from the entered start point; they are not records of work, marks, or attendance already completed.
Formulas, examples, and tests
Interactive launch calculators provide a formula or method summary, a numeric worked example, and a limitation near the form. Engine tests cover representative, boundary, invalid, and rounding behavior where implemented, while content tests check that an interactive launch page has an accompanying method explanation.
Passing tests confirms the cases encoded in the suite; it does not verify an external policy. Exam weights, grade conversions, cutoffs, and eligibility conditions remain user-supplied or unresolved unless an applicable first-party document has been reviewed.
Frequently asked questions
Where do Acadnix calculations run?
They run in the browser through calculator engine functions. The current project has no backend or database for calculator values.
When should a result be rounded?
Keep working precision through dependent steps and round at the calculator's stated display stage. An official document can require a different precision or rounding convention, which must take priority.
Do passing unit tests prove an institution uses the formula?
No. Tests check implemented arithmetic and validation. Only an applicable current first-party document can establish an institution's rule.