cold start handling in ranked batch sampling

[modal-python]

cold start handling in ranked batch sampling

[cosmic-cortex]

Great, thanks! It is certainly not added. I'll take a look at the paper as soon as possible!

[cosmic-cortex]

Thanks for the PR! Fixed by #29.

[zhangyu94]

Hmm... This issue and PR #29 actually are addressing different problems.
This issue is on the problem that the best cold start instance is not added to the first batch (in ranked_batch), while PR #29 address the problem that the computation of instance index is incorrect (in select_instance).

I haven't started a pull request for this issue since solving it very likely requires changing the API of select_cold_start_instance.
If needed, I can start a PR for this issue later today.

[cosmic-cortex]

Sorry, remembered the issue wrong and didn't read the post again before commenting. Issue reopened! :)

[cosmic-cortex]

In any case, no need to rush with the PR! Probably I won't have time to work on this week, so any help is appreciated!

[zhangyu94]

Hi, I have opened PR #30 for this issue.

By the way, I think it will be great if we can compose the cold start handling mechanism that currently works for ranked batch sampling (and possibly other cold start handling strategies in the future) with other active sampling strategies supported by modAL.

[cosmic-cortex]

Alright, thanks for the PR! I finally had the time to review and merge it. Currently, some cold start is implemented for the utility measure functions, but it only checks whether the estimator has been fitted yet, and if not, it returns a zero array. Implementing the same density based cold start criteria for a general query function is a good idea.

[zhangyu94]

I see. I will take a look at how to integrate cold start handling mechanisms.

One thing that I have been thinking about is whether it is better to pass the cold start function to the query strategy functions or to the Learner when initialized. It is logically sounder to pass cold start criteria to a query strategy since "cold start criteria" are part of the "query strategy", while in implementation, it seems much easier to do it the other way. If we pass the cold start criteria to the Learner, it seems that we only need to change the Learner.query method to support cold start handling for all the query strategies. By comparison, if the cold start criteria is to be passed to the query strategy functions, all the query strategy functions may need to be revised.

Thanks.

[cosmic-cortex]

I agree completely. I think it is better if the cold start strategy is passed to the query strategy, even so if all query strategy functions need to be modified.

In connection with this, I also plan to do a refactor of the query strategy functions. If you check the code, for instance here, the implementation of the uncertainty_sampling, margin_sampling, entropy_sampling functions is almost identical, aside from the function they call for calculating the utility. This can be solved with a function factory or some other construct. The only reason I implemented it this way because I wanted to avoid adding docstrings one by one later. Do you have any idea which might be good for this? We might hit two birds with one stone, because this would solve the problem outlined by you.

[zhangyu94]

Hmm... I don't have better ideas than using a function factory.

A possible alternative is to lift the query strategies from functions to instances of a QueryStrategy class. Different instances of this QueryStrategy class can have different scorers (e.g., classifier_entropy) and cold start handlers. This solution doesn't seem to have a clear advantage over the function factory solution.