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
Is your feature request related to a problem? Please describe.
Since DiceCELoss is available as a loss, it would make sense for it to be available as a metric too.
Describe the solution you'd like
Either a dedicated DiceCELoss metric like e.g. MeanDice for the DiceLoss OR a pluggable DiceCELossMetric which can be used as input to IgniteMetric.
Describe alternatives you've considered
Passing the DiceCELoss into IgniteMetric results in an error since it does not have a reset button. Which kinda makes sense, this is no metric, it does something different.
Additional context
I am also curious about why the dice got implemented at two places, namely MeanDice and the DiceLoss. From a quick glance I believe they do the same computation - so is there any reason for the code to duplicated here? The calculation logic for both should be the same.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Since DiceCELoss is available as a loss, it would make sense for it to be available as a metric too.
Describe the solution you'd like
Either a dedicated DiceCELoss metric like e.g. MeanDice for the DiceLoss OR a pluggable DiceCELossMetric which can be used as input to IgniteMetric.
Describe alternatives you've considered
Passing the DiceCELoss into IgniteMetric results in an error since it does not have a reset button. Which kinda makes sense, this is no metric, it does something different.
Additional context
I am also curious about why the dice got implemented at two places, namely MeanDice and the DiceLoss. From a quick glance I believe they do the same computation - so is there any reason for the code to duplicated here? The calculation logic for both should be the same.
The text was updated successfully, but these errors were encountered: