Open kechan opened 2 years ago
That's correct, I added the SplitValidationLoss to monitor the matching classification performance on the known vs the unknown classes to get a sense of how well an embedding is generalizing during training. I would recommend using the EvalCallback if you don't have any Unknown classes though. The two callbacks are very similar, so much so that I'm thinking of combining them at some point into a more general callback that also supports the retrieval metrics.
Can you share the error msg you were getting? I can likely add a check for the length and/or a more informative error msg to that.
@owenvallis I pasted it in my original post (maybe for better discovery if someone searches for it).
It appears that this callback:
will generate a "invalid length" kind of error. I browsed the code a little bit and figured that the known_class must be a subset of all the classes such that there's at least 1 unknown class (it doesn't handle 0 unknown class). I wonder if this is by design since the name has Split in it.
This is what the error looks like: