It's a common trend in CS research where a paper says that the data or the code will be released, and an empty repo is created to support that conclusion. This helps authors get favorable reviews, and to get accepted in prestigious conferences. Then the code or data are never released, and the authors pretend as they have never promised anything. Unfortunately, it looks like the authors of this paper might be doing just that.
Apologies for the delay in posting the data and code. The data is undergoing cleaning and preprocessing, for easier use. It should be posted by April 10th, the latest. Thank you for your interest.
It's a common trend in CS research where a paper says that the data or the code will be released, and an empty repo is created to support that conclusion. This helps authors get favorable reviews, and to get accepted in prestigious conferences. Then the code or data are never released, and the authors pretend as they have never promised anything. Unfortunately, it looks like the authors of this paper might be doing just that.