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
{{ message }}
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.
Currently NaN appears to be treated as zero when sorting the "Default metric" column in WebUI. (I'm using NNI v1.6 by the way.)
This becomes an issue, for example, when you have a minimization problem with non-NaN metrics being always positive. After sorting in the ascending order, if you have many NaN cases, you'll have to scroll down a lot to see the best (minimal) metric. You will encounter the same issue even you sort in the descending order.
Since NaN is always undesirable, it would be nice if NaN is treated as positive infinity for minimization problems, while treated as negative infinity for maximization problems, for the WebUI sorting purpose only
The text was updated successfully, but these errors were encountered:
Currently NaN appears to be treated as zero when sorting the "Default metric" column in WebUI. (I'm using NNI v1.6 by the way.)
This becomes an issue, for example, when you have a minimization problem with non-NaN metrics being always positive. After sorting in the ascending order, if you have many NaN cases, you'll have to scroll down a lot to see the best (minimal) metric. You will encounter the same issue even you sort in the descending order.
Since NaN is always undesirable, it would be nice if NaN is treated as positive infinity for minimization problems, while treated as negative infinity for maximization problems, for the WebUI sorting purpose only
The text was updated successfully, but these errors were encountered: