ubriela
commented
9 years ago May be we should not consider Frequency when designing diversity metric? The reason is that we can think of frequency as user's task accomplishment. For example, if we need 20 pictures at all task locations; however, we only obtain 2 now while the deadline is approaching. So, we need to give higher prices to all tasks, especially the ones with low frequency.
Incorporating frequency (F) with diversity (D) is definitely not an easy task. It may require more time to think about it :) But one of my suggestions is that you should think of diversity as an exponential function of entropy. Let's say, we find entropy to be H, then diversity should be D = exp(H) because D has the unit similar to the number of locations. Then, maybe try to incorporate D and F somehow. For example, 0.8D + 0.2F if you think D is more important than F, or 0.5D+0.5F if you believe that they are equally important, or even D*log(F), etc... If you decide to go with your option, make sure to give good reasons for why you believe in it. This is not just a coding task, it is also about reasoning and proving by using real-life factors/analysis. Even if you choose an option (say, D +F), which may seem simple and not good enough at the first glance, but if you can give arguments for explaining why you think it works and convince other people to believe it ( with real-life facts and examples, not with feelings :] ), it could still be perceived as a good solution. In sciences, there are cases, where simple solutions are more than good enough and any sophisticated solutions may just be exaggerations. There are also vice-versa cases, where simple solutions fail, and we need to find more complex options.