Skip to content

run-series.cmd: describe both sides of the session gate #120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mspinola merged 1 commit into from
Sep 25, 2026
Merged

run-series.cmd: describe both sides of the session gate #120

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions docs/examples/windows/run-series.cmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 ------------------------------------------------------------------------
Expand Down
Loading