-
Notifications
You must be signed in to change notification settings - Fork 6
Description
I am not sure if this is the intended behavior but it seems like tau_2 is dependent on tau_1, i.e., the rate of feature being selected, judging from the article on arxiv and also the code. It seems that this would prioritize tau_1 over tau_2 and tau_2 will be scaled according to the rate of the feature being selected during the feature selection.
I conducted a simulation of tau_2 of one feature x at different rate the feature being selected, and I plot positive rate of x against tau_2 (right):

It clearly shows that the tau_2 is scaled significantly with the frequency of the feature being selected by the model. If the features is not selected 100% of in all model, the range of tau_2 is not (0 to 1).
Seeing this might be problematic, I added a scaling factor w.r.t to the observed zero-rate (left). (rate of feature not selected across K runs), and this return the range back to (0 to 1).
I just want to ask if this is the intended behavior and how could this affect the results of feature selection?