FAQs

• Q. The datasets are not complete (i.e., location observations are not provided for all time steps for all individuals), is this an error?
  • A. No, mobile phone location data is not complete — that makes human mobility prediction difficult! Please try to predict the locations of the individuals labeled ‘999’ in each dataset.
• Q. The GEOBLEU code is computationally slow. How can we speed it up?
  • A. Note that you need to compute the GEOBLEU scores for each day per user, not for the entire 15-day trajectory for each individual. If the computation is slow even in this case, please try multi-thread processing. We will post the example code on the GitHub page soon. Please watch out for updates at https://github.com/yahoojapan/geobleu.
• Q. What is the typical range of values of GEOBLEU metrics? I just want to know whether the score is in the same ballpark?
  • A. The results obtained by a simple baseline method was around 0.04 for GEOBLEU, tested by the organizers. Details of the simple baseline method and results are outlined on the GitHub readme “Baseline method and results” section, here: https://github.com/yahoojapan/geobleu.
• Q. Can we use AI agents to implement and test models?
  • A. Yes, you can use any software or code, but please describe it in your short paper if you are invited to submit a paper.