Skip to content
This repository was archived by the owner on Nov 13, 2025. It is now read-only.

Releases: PrivyXe/Technicaly

Create a new release

01 Oct 22:31
@PrivyXe PrivyXe
v1.0.0
dd047b6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Create a new release

🚀 Technicaly v1.0.0

Professional technical analysis platform for smart trading.

  • 30+ technical indicators (RSI, MACD, Bollinger Bands…)
  • 30+ candlestick patterns detection
  • Multi-timeframe analysis (15m to 1d)
  • Advanced risk management tools

Get instant market insights and trade smarter. Start your 1-month FREE trial today!

Loading

v1.0.1 Update

06 Oct 19:37
@PrivyXe PrivyXe
v.1.0.1
dd047b6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v1.0.1 Update Latest
Latest

🚀 Release v1.0.1 — Logic Refinement & Stability Update

🔧 Core Fixes & Logic Improvements

🧩 IndicatorCalculator.kt
Fixed: Incorrect EMA loop range.
Replaced for (i in period.index) with for (i in period until index + 1) to ensure proper EMA propagation.
Reason: The old loop caused incomplete or incorrect EMA calculations.
Improved: calculateSMA() now checks for Double.isFinite() instead of rejecting values <= 0.
Reason: Prevents valid low-priced assets from returning null due to false zero filtering.
Deprecated: CMF_Old() and MFI_Old() functions marked as @ Deprecated.
Reason: To remove confusion between legacy and modern implementations.

⚙️ SignalConfig.kt
Fixed: Increased daily (D1) timeframe minimum data requirement from 150 → 250.
Reason: Ensures sufficient candles for SMA200 and EMA200 calculations.
Logic Update: Replaced
minOf(calculatedMin, maxReasonableMin)
with
maxOf(maxPeriod, minOf(calculatedMin, maxReasonableMin))
Reason: Prevents the system from using too few data points for long-term indicators.

📈 VWAP Logic
Improved: findSessionStart() now derives the session start from candle openTime instead of relying on system clock.
Reason: Provides consistent session detection across exchanges and time zones.

🧠 Design Consistency & Code Cleanup
Removed redundant or legacy functions to simplify maintenance.
Improved code readability and naming consistency.
Ensured indicator logic is fully aligned across modules.

✅ Outcome
EMA and SMA calculations are now consistent and accurate.
Long-term indicators (SMA200, EMA200) compute properly across all timeframes.
VWAP session detection is robust in multi-timezone environments.
Deprecated legacy indicators improve future maintainability.

Assets 3
Loading