Skip to content

Fix DoubleTop indicator and improve docstrings#9

Merged
whchien merged 5 commits intomainfrom
debug/double_top
Feb 4, 2026
Merged

Fix DoubleTop indicator and improve docstrings#9
whchien merged 5 commits intomainfrom
debug/double_top

Conversation

@whchien
Copy link
Owner

@whchien whchien commented Feb 3, 2026

Summary

This PR addresses the DoubleTop indicator logical contradiction and improves documentation:

  • Fixed logical error in DoubleTop indicator implementation
  • Updated and clarified docstrings across the indicator module

Changes

  • Fix DoubleTop indicator logical contradiction
  • Update and improve docstrings

Type of Change

  • Bug fix
  • Documentation improvement

Testing

The changes have been validated and are ready for merge.

whchien and others added 5 commits February 3, 2026 11:41
The original implementation had mathematically impossible conditions:
- cond_1: Today's close equals 60-day highest price
- cond_3: Some historical price (30-55 days ago) is GREATER than 60-day highest

These conditions could never both be true simultaneously. If today is the
60-day high, no other day in that window can be higher.

## Solution

Replace contradictory logic with correct double-top pattern detection:

1. **First top**: Maximum price from 30-55 days ago (historical peak)
2. **Pullback**: Minimum price from 1-30 days ago (trough formation)
3. **Breakout**: Current price breaks above first top

## New Conditions

- cond_1: Close at/near 60-day high (2% tolerance)
- cond_2: Meaningful pullback occurred (5% below first top)
- cond_3: First peak comparable to current price (within 10%)
- cond_4: Current price breaks above first top
- cond_5: Price above short-term SMA (uptrend)
- cond_6: Price above long-term SMA (strong trend)
- cond_7: Volume increasing (breakout confirmation)

## Benefits

- Signals can now be generated when valid patterns are detected
- Added comprehensive docstring explaining the pattern
- Better error handling with try/except blocks
- Uses percentage thresholds to handle floating-point precision

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@whchien whchien merged commit 35e6366 into main Feb 4, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant