From ceb51d6c0abb9395eada6d45cdfc15e0897671f3 Mon Sep 17 00:00:00 2001 From: Matt Spinola Date: Fri, 25 Sep 2026 14:50:55 -0400 Subject: [PATCH] run-series.cmd: describe both sides of the session gate The header said the build refuses a bar OLDER than the expected session. With marketdata's ceiling it refuses a newer one too, as unsettled. The deployed copy on the box already carries this wording by hand; the example did not, and since /scheduler/ is gitignored there is nothing that would have told anyone the two had drifted. Pairs with mspinola/marketdata#37. Co-Authored-By: Claude Opus 5 --- docs/examples/windows/run-series.cmd | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/examples/windows/run-series.cmd b/docs/examples/windows/run-series.cmd index adde5fd..77a40d7 100644 --- a/docs/examples/windows/run-series.cmd +++ b/docs/examples/windows/run-series.cmd @@ -22,9 +22,15 @@ REM Stage 2 is the one command below. marketdata-update --build-tradingview read REM ONLY those local files: it validates them (the connector's JSON shape, the REM registry range per kind, strictly increasing stamps, the registry anchors), REM refuses any bar that disagrees with a bar the store already holds (the store -REM is never rewritten by a build), appends only what the store lacks, and -REM refuses as STALE, exit 1 and nothing written, when the newest bar is older -REM than the latest weekday whose 16:30 ET close has passed. +REM is never rewritten by a build), appends only what the store lacks, and gates +REM the newest bar on BOTH sides of the expected session, which is the latest +REM weekday whose 16:30 ET close has passed. Older is refused as STALE and the +REM later routine is the retry. Newer is refused as UNSETTLED: fired before the +REM close, the connector serves the day in progress, and on the put/call ratios it +REM serves it a bar ahead of the breadth counts. That Close still moves, and since +REM a stored bar is never rewritten, storing it once would refuse every later +REM build of the same session until someone cleaned the store by hand. Neither +REM side writes anything. REM REM WHY THERE IS NO RETRY LOOP IN HERE REM ------------------------------------------------------------------------