Independent calculations and app workflow

Binomial probabilities for crisp truth-table rows checked

This diagnostic asks how unusual a crisp truth-table row's outcome count would be under a chosen probability. It uses whole-number counts of trials and successes and calculates the upper-tail probability. The test checks that arithmetic using exact fractions; it does not treat fuzzy memberships as binary trials or adjust for testing many rows.

Reviewed 4 November 2026
Specific testsExact-fraction checks of upper-tail probabilities

What the comparison shows

The independent reference covers 102 upper-tail examples, alongside eight checks of the underlying calculation routines. All 102 generated rows match after Windows line endings are accounted for. The file-format difference and the numerical agreement are recorded separately, so a failed byte comparison is not confused with a different calculated answer.

What does an upper-tail probability mean here?

In crisp data, a case is either in or out of a set. For each truth-table row, every included case counts as a trial, and a case belonging to the selected outcome counts as a success. The null probability is the success probability specified for the test. The upper-tail calculation asks how likely it would be to observe that many successes or more if that probability applied.

The reference must use the same integer counts, null probability and tail direction. The procedure does not correct for testing multiple rows. Fuzzy memberships describe degrees of membership, so treating them as binary trials would change the question rather than extend this comparison.

Which versions belong to these checks?

The table identifies the QuickPLS development and installer versions associated with the saved checks. The expected probabilities come from a separate calculation using exact fractions. The record also distinguishes the calculation checks from the installed report-preparation step.

On a small screen, swipe the table sideways to see every column.

RecordQuickPLS build or result checkedReferenceComparison outcome
Exact binomial truth-table diagnostic evidence1.03.05 / Installer E1.03.06See which mathematical and app-workflow checks were performedMathematical reference plus checks of the specified calculations and app workflows

Checking the probabilities with exact fractions

The reference checks 102 upper-tail examples with exact rational arithmetic, meaning calculations based on fractions rather than rounded intermediate decimals. There are also eight checks of the underlying calculation routines. The source data are binary and crisp, with cases either in or out of each set.

  • The procedure reports unadjusted probabilities for binary crisp data. It does not apply a multiple-testing correction across rows.
  • The original files have different line endings, so comparing their bytes gives a mismatch. After the line endings are normalised, the numerical content matches exactly for all 102 rows.
  • The installed app prepared the report in this test. Saving that report was not tested.
What was checkedValue / scope
Test cases checked against exact-fraction calculations102
Checks of the underlying calculation functions8

What the exact agreement tells you

The comparison supports the upper-tail arithmetic for the stated crisp examples. A small probability means that the observed count would be unusual under the chosen null probability. It is not the probability that a causal claim is true, and a nonpassing row does not establish the absence of the outcome.

Keep the file and calculation checks separate. A line-ending difference changes how text is stored without changing the probability values. The example and routine counts describe focused checks, not independent research studies.

  • This page combines exact-fraction calculations, underlying routine checks and a report-preparation step. It does not use one decimal-error limit for all of them. The unadjusted, upper-tail definition remains part of every interpretation.

How to inspect the binomial test report

The JSON summary covers the 102 probability checks, the calculation-routine checks and the separate file-format finding. It also identifies the tested versions and source documents.

A rerun requires the original crisp inputs, settings and software versions. The download reports completed tests; the original datasets and app source code are not included.

Download the comparison results

See the values we checked, the differences we found and the software versions used. The download also identifies the original test files.

About these tests

These are QuickPLS development comparisons. Each record identifies the reference software or mathematical calculation, the tested build and the settings used.

How to understand these comparisons · Find checks for another method