You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rename the y-axis labels on each plot to: 1433 - Norbert
accuracy(%), Profit(OCEAN), Stake(OCEAN)
accuracy plot rescale to min 30 - 70 bounds 1433 - Norbert
the accuracies are mostly between this 2 values so updating the bound will eliminate the free spaces
show confidence interval if 1 track is shown 1434 - Mustafa
similar to what we have inside the simulation plots, so confidence intervals inside the accuracy plot, but only of just 1
track is shown
display selected table rows as first elements 1439 - Calina
when fields are selected, especially on predictoors table with pre configured addresses, if they are not in between the
first x visible rows, it’s not clear that there are any rows selected. Once something is selected sort the rows so that is
displayed at the start
…1435) (#1437)
* Fix#1433: Rename figures y axis and updated accuracy plot range (#1435)
* Fix#1441: Display number of rows for each table (#1442)
* Fix#1439: Show selected lines first in predictoor dashboard (#1443)
* Fix#1449: Issue with feed searching when predictoors selected. (#1449)
* Fix#1453: Predictoor table columns to match later renditions (#1454)
* Fix#1434: Show the confidence interval on the Accuracy plot (#1440)
* Fix#1462: The x axis is not order bug (#1463)
* Fix#1464: Add tooltips (#1465)
* Fix#1438: Calculate and display tx fee costs (#1444)
---------
Co-authored-by: Mustafa Tunçay <[email protected]>
Co-authored-by: Călina Cenan <[email protected]>
Target
Add costs, tooltips and final fixes and updates to make the UX of the first page of dashboard better before moving to other pager
Super epic issue can be found here
TODO
track is shown
first x visible rows, it’s not clear that there are any rows selected. Once something is selected sort the rows so that is
displayed at the start
UI sketch for v0.3:
The text was updated successfully, but these errors were encountered: