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
I always have a hard time finding the results of a benchmark. When I finally get to the results page, some links are broken ("neurips 22 benchopt results"), and some benchmarks are not referenced there (e.g. this one).
For now, the home page focuses on running an existing benchmark. I feel like this is just a very specific way to use benchopt. Could it be improved by being simpler and yet more comprehensive?
One idea to do this: instead of having a rather long home page as it is now, with information hidden all over the place (in the text, in the sidebar, etc.), just put simple access buttons:
"Run an existing benchmark"
"Access benchmark results"
"Access benchmark source codes"
"Add your own benchmark"
... (list all the other ways to use benchopt)
and an isolated button for the user who just wants to discover benchopt, redirecting the user to a high-level description of benchopt?
I know it's very subjective, but I think it might be worth discussing.
The text was updated successfully, but these errors were encountered:
I always have a hard time finding the results of a benchmark. When I finally get to the results page, some links are broken ("neurips 22 benchopt results"), and some benchmarks are not referenced there (e.g. this one).
For now, the home page focuses on running an existing benchmark. I feel like this is just a very specific way to use benchopt. Could it be improved by being simpler and yet more comprehensive?
One idea to do this: instead of having a rather long home page as it is now, with information hidden all over the place (in the text, in the sidebar, etc.), just put simple access buttons:
and an isolated button for the user who just wants to discover benchopt, redirecting the user to a high-level description of benchopt?
I know it's very subjective, but I think it might be worth discussing.
The text was updated successfully, but these errors were encountered: