Fix bug in criteo.py that caused NaN issues (#2150)

Summary:
The original script simply added 3 to the target value before taking the log. This led to the issue that in data preprocessing, if there was a value of -3, it would result in a value of -inf. This problem was mentioned in the issue facebookresearch/dlrm#363 (comment). I changed the preprocessing operation to dense_np -= dense_np.min() - 2 in the tsv_to_npys function, and correctly handled the Criteo Kaggle dataset.

Pull Request resolved: #2150

Reviewed By: spmex

Differential Revision: D77049372

Pulled By: TroyGarden

fbshipit-source-id: c9e2d0de08babd97066810e8f66ac7009e8bd29b

Author: TomekWei

torchrec/datasets/criteo.py

@@ -258,7 +258,7 @@ def row_mapper(row: List[str]) -> Tuple[List[int], List[int], int]:
         del labels
 
         # Log is expensive to compute at runtime.
-        dense_np += 3
+        dense_np -= dense_np.min() - 2
         dense_np = np.log(dense_np, dtype=np.float32)
 
         # To be consistent with dense and sparse.