AUC bug report

In ESMM, it seems there is a bug in auc computation. When there is no positive example in a batch, this batch is ignored for the auc computation. We cannot just simply remove this batch from computation, which is different from the auc caculation in tensorflow.

In my opinion, auc should be computed globally, insteady of averaging locally like in x-deeplearning. The all-negative batch can still change the number of FP globally, which cannot be ignored.

This bug makes the performance of esmm pretty high.

Start by locating the ESMM AUC computation and its batch-level aggregation. Compare its handling of all-negative batches with TensorFlow's global AUC behavior, then add or update coverage for batches that contain no positive examples. Done means the metric incorporates false positives from those batches rather than ignoring them.

Written by the indexing model from the issue text.