Quality & Methodology

Principles

• Reproducibility: the Notebook is designed to keep inputs, assumptions, and outputs together.
• Explainability: many tools expose an evaluation trace to make interpretation visible.
• Defensive limits: compute endpoints enforce request limits and rate limits for predictable performance.
• Units awareness: conversions and compound units reduce “silent mismatch” errors.
• Human verification: the UI includes sanity checks and encourages cross-verification.

How we validate calculators

There is no single perfect method for all math tools. GetCalcMaster combines:

• Sanity checks embedded in the UI (example conversions, known identities, and boundary cases).
• Regression-style manual test cases maintained alongside releases (so changes don’t silently break workflows).
• Trace-based review via the “Explain” panel to catch parsing and precedence surprises.

Numerical caveats (read this if results matter)

• Floating point: many computations use floating-point arithmetic; rounding is expected.
• Conditioning: some problems are inherently unstable (small input changes cause large output changes).
• Graph sampling: graphs are sampled approximations; increasing resolution can change what you see.
• Units definitions: data units (GB vs GiB), “ton” variants, and domain-specific definitions can differ.
• FX rates: currency tools depend on rate snapshots; always confirm timestamp and source for trading/compliance.

A verification workflow we recommend

1. Check units (including degrees vs radians, and any implicit unit assumptions).
2. Estimate by hand (order of magnitude, sign, and rough bounds).
3. Cross-check with an independent method/tool (textbook identity, spreadsheet, reference calculator).
4. Record assumptions in the Notebook so the result can be reproduced later.

Reporting issues

If something looks wrong, please include:

• The exact input expression or steps to reproduce.
• The tool/page you used (for example: Scientific vs Engineering).
• The expected result (and a reference source if possible).

Use the Contact page.