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
The default configuration and the plots are based on the optimal value of the first metric. Currently, when the app is first launched, the default row is not selected/highlighted on the tuning parameters datable and we want to do that.
This seems doable but complicated. Here is a way to add a default selection to a DT table. There is also a way to initialize a reactive value (for input$metrics_rows_selected) via eventReactive().
The text was updated successfully, but these errors were encountered:
I solved this issue by creating a copy of the performance table and finding the row index of the lowest value of the optimal value of the first metric which is the default metric. The following code solved the issue:
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.
The default configuration and the plots are based on the optimal value of the first metric. Currently, when the app is first launched, the default row is not selected/highlighted on the tuning parameters datable and we want to do that.
This seems doable but complicated. Here is a way to add a default selection to a DT table. There is also a way to initialize a reactive value (for input$metrics_rows_selected) via eventReactive().
The text was updated successfully, but these errors were encountered: