Smarter retry prediction mechanism

[ivanzvonkov]

Context: When the predicted file amount does not match the input file amount the create_map.ipynb will prompt the user to retry on all files with missing predictions.

Issue: When all predictions or most predictions are missing the system is either in the process of making predictions or predictions have failed for a reason other than latency (eg. bug in prediction code, eo files with missing values). When this occurs retrying on files with missing predictions is not effective and is a waste of time.

Potential solution: Instead of allowing the user to retry any time predicted file amount does not match input file amount, only prompt user to retry when predicted file amount is at least 50% of input file amount. Otherwise alert the user that the system may be unstable and link the logs that should be referenced.