Degree-day Series Auditor

How to use Degree-day Series Auditor

Choose C or F and either daily means or daily minimum/maximum pairs. Enter your own heating/cooling bases and a half-open date range. Observed days contribute exact positive deviations; missing days remain null in the calendar and are counted separately in every aggregate.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Choose C or F and either daily means or daily minimum/maximum pairs. Enter your own heating/cooling bases and a half-open date range. Observed days contribute exact positive deviations; missing days remain null in the calendar and are counted separately in every aggregate.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• At most 366 calendar days and 366 observations, plus 24 nonempty selected subperiods. Temperatures/bases are −150–150 C or −238–302 F. Gregorian dates 1900–9999 are supported; 10000-01-01 is an exclusive-end sentinel only. This is supplied-data arithmetic, not weather lookup, climate certification or an energy-demand prediction.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.