u/Biiiscuit ·
Reddit — r/algotrading
· 2026년 4월 23일, 15:26
· ⬆ 15 포인트
· 💬 60 개 댓글
| Reddit에서 보기 ↗
AI 요약
=== 요약 ===
- 게시물은 알고리즘 트레이딩을 위한 견고한 스윙 고점/저점 탐지기 구축에 대해 논의하며, 미래 정보 편향을 최소화하는 것을 목표로 함.
- 저자는 3-캔들 패턴을 사용하지만 횡보장에서 너무 많은 신호를 발견; 스윙을 중기(IT) 및 장기(LT) 범주로 분류하고자 함.
- 게시물은 방법론 및 구현에 관한 기술적 문의이며, 특정 자산에 대한 거래 추천이나 분석이 아님.
- **품질 평가:** 이는 기술적 논의/질문이며, 잘 조사된 DD나 투기적 논제가 아님. 알고리즘 설계에 대한 통찰력을 제공하지만 실행 가능한 거래 아이디어는 없음.
=== 심리 ===
중립
=== 매매 아이디어 ===
이 게시물에 실행 가능한 매매 아이디어 없음.
점수15
댓글60
추천 %86%
▶ 전체 게시글 텍스트
I’m working on an algo trading project and trying to build a robust swing high / swing low detector with as little lookahead as possible (ideally none).
Right now my definition is very simple:
\- Swing High: a 3-candle pattern where the middle candle’s high is higher than both neighboring candles’ highs
\- Swing Low: a 3-candle pattern where the middle candle’s low is lower than both neighboring candles’ lows
The issue is this generates a huge number of signals, especially in choppy/low-volatility conditions.
My goal is to classify swings into:
\- IT (Intermediate-Term) swings
\- LT (Long-Term) swings
and filter out insignificant noise.
I’ve found some implementations in TradingView scripts and Python examples, but many of them use things like “highest high of the last 10 bars and next 5 bars” or similar logic. That introduces significant lookahead / future leak, which is exactly what I’m trying to avoid and why I’m emphasizing this constraint.
Main constraint: I want to minimize lookahead bias for backtesting and keep it realistic for live trading.
For those who’ve implemented this before:
1. How do you define “meaningful” swings without introducing too much lag?
2. How do you structure IT vs LT swings? Recursive/fractal approach?
3. Is zero-lookahead realistic, or is 1–2 bar confirmation the practical compromise?
4. Any recommended algorithms / indicators / market structure concepts I should study?
Would appreciate any practical advice or implementation ideas.