circadian midpoint clockwheel · meter band gauge

Average Sleep Midpoint Clocks Without Turning Midnight into Noon

Midpoint clocks near midnight should not average to lunchtime. Keep the recorded overnight window and its circular direction visible before using a diary to ask a clinician about timing.

1 · Night code | bedtime HH:MM | wake clock HH:MM

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: This circadian midpoint clockwheel calculates in the tab from Night code | bedtime HH:MM | wake clock HH:MM. No input-collection endpoint, AI request or file upload is built into it. Drafts may be saved locally; explicit input-state links and optional external formatting can disclose the records. Use non-sensitive codes and clear the draft when finished.

Perspective: Before: midnight split the diary into misleadingly large and small numbers. After: midpoint directions and their concentration stay together on one clock wheel.

2 · Read the circadian midpoint clockwheel

Diary arithmetic only: no sleep diagnosis, chronotype assessment or treatment advice. Confirm clock conventions and bring persistent sleep concerns and the original dated diary to a qualified clinician; do not change care from this midpoint.

Paid layer: circadian midpoint clockwheel filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one full, unwatermarked circadian midpoint clockwheel App execution
three invented readings and unlimited calculations in the paired article demo
copy the complete working and boundary; voluntarily share non-sensitive input state

What $4 one-time adds

subsequent circadian midpoint clockwheel App calculations through a browser-local convenience signal
boundary-preserving print and row-and-summary CSV of this circadian midpoint clockwheel; conditional retyping budget uses only your entered minutes
five local headline/count/time summaries, separately deletable; full-input draft is separate and not a backup

HYPOTHESIS / PROTOTYPE: the proposed $4 one-time price concerns filing this circadian midpoint clockwheel, not obtaining its answer. No checkout is available. An optional manual-retyping baseline computes a conditional one-export retyping budget; preparation, review, measured savings and buyer demand are not implied.

Local history (this device)

No saved runs yet — your first run files here.

Filing prototype — checkout unavailable

Checkout is unavailable. Browser-local, profile-scoped convenience gating is best-effort, not server-verified access. A URL or browser flag is not proof of payment. Clearing browser data removes local state; no account or cross-device recovery is provided.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the circadian midpoint clockwheel

This clockwheel is for a factual diary conversation, not a bedtime prescription. Enter one main sleep window per row using clocks from the same local-time convention. It assumes the next occurrence of the wake clock within 24 hours; it cannot represent a date-line jump, daylight-saving clock change or a window longer than a day. Naps and split sleep should not be silently combined into a main window. A midpoint is halfway through an entered clock window, not measured sleep onset, sleep stages or a chronotype. If the diary covers changing offsets, preserve the actual dates and offsets elsewhere and discuss how to analyze them before using these clock-only rows.

Boundary and sources

Declared local method: Convert each midpoint to an angle of 2π times its minute-of-day divided by 1,440. Average cosine and sine separately, use atan2 to recover the mean angle, and normalize midnight to zero. The vector length R is between zero and one. Numerically, R at or below 10⁻¹⁰ is treated as canceled and causes an explicit error; below your review floor the mean remains a mathematical result but is labeled partial because the directions are dispersed. Nights are equally weighted, not weighted by duration.
Every sample code, measurement, date, price, fingerprint and scenario is invented. Artifact checks do not verify reader data, policies, actual files, tickets, votes or health/accessibility outcomes.
Google’s official Gemini pricing page, fetched 2026-10-01, lists AI Studio access in its Free section, limited model access and free input/output tokens. Free-tier content may be used to improve products. Optional external formatting may require an account; limits/access can change. Manual local entry needs none. Do not send sensitive records.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this circadian midpoint clockwheel for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a circadian midpoint clockwheel. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Night code | bedtime HH:MM | wake clock HH:MM; the setting is Resultant-length review floor (0–1). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.