-
Notifications
You must be signed in to change notification settings - Fork 36
Description
Issue
The metadata endpoint includes time-series profit data that is used to render the chart displayed on strategy tiles. The property in the payload is: summary_statistics.compounding_unrealised_trading_profitability.
This data should be ordered chronologically, with only a single record per timestamp. Several strategies have duplicate timestamp entries (with inconsistent values), and one strategy has entries which are out of chronological order.
Impact
This issue affects the chart migration effort on frontend (ChartIQ → TradingView). ChartIQ was swallowing these data issues, but TradingView is throwing an exception when there are duplicates or out-of-order entries.
We could implement some data cleansing on frontend, it seems better to address this at the source.
Details
See discord thread.
Duplicates
List of strategies with duplicate timestamps (and count of duplicates):
enzyme-polygon-eth-breakout: 1
base-memex: 180
base-sentimeme: 1
base-ath: 52
Example of duplicate entries from base-memex at indices 31-32:
[1736510400, 0.016308241802061696],
[1736510400, 0.015454018260557367],
Out-of-order
Strategy with out-of-order entries (and count):
base-sentimeme: 1
Example of out-of-order entries at indices 279-81:
[1739944800,0],
[1739923200,0],
[1739944919,0],