Chris Amow
8c2ef80966
It was never in the enabled timeframes, so it held zero bars and produced no levels, but it still carried weight 8 in the scoring table and forced bucket_start to special-case a wall-clock ET anchor whose entire purpose was surviving DST transitions. That was the most intricate logic in session.py, maintained for a timeframe nobody used. Daily is now the only session-anchored bucket, which is a much easier rule to state and to keep correct. The DST parametrised tests go with it; the Sunday open and daily boundary cases remain. Manual-line tests move to 1h, so the weight assertions drop from 8 to 4. The plan document keeps its 4h examples — rewriting a dozen illustrative sentences would churn more than it clarifies — but the timeframe-roles section now records the removal so nothing reads as a spec to build. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
28 lines
799 B
Text
28 lines
799 B
Text
# Data sources
|
|
LIVE_SOURCE=yahoo
|
|
SEED_SOURCE=yahoo
|
|
YAHOO_SYMBOL=ES=F
|
|
YAHOO_POLL_SECONDS=20
|
|
SEED_1H_RANGE=730d
|
|
SEED_1M_RANGE=8d
|
|
|
|
# Chart and analysis
|
|
TIMEFRAMES=1m,5m,15m,30m,1h,1d
|
|
BASE_TIMEFRAMES=1m,30m,1d
|
|
MAX_BARS_PER_TF=5000
|
|
MA_SETS__1D=sma10,sma20,sma50,sma100,sma200
|
|
MA_SETS__1H=
|
|
DAILY_ANCHOR_ET=18:00
|
|
MANUAL_LINES_PATH=./data/manual_lines.json
|
|
CONFLUENCE_MIN_SCORE=28
|
|
# Four hours. Suppression is per price zone, so an unrelated zone still alerts;
|
|
# this governs only how often the same area repeats. See README.
|
|
ALERT_COOLDOWN_SECONDS=14400
|
|
|
|
# Notifications and access
|
|
NTFY_TOPIC=
|
|
NTFY_SERVER=https://ntfy.sh
|
|
# Blank = no auth (fine locally). In production this is set in Coolify, not
|
|
# here — see README. Sent as the X-Chart-Token header, or ?token= for /ws.
|
|
CHART_AUTH_TOKEN=
|
|
REPLAY_FILE=
|