-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Binning for mutual info calculation #12
Comments
Hi again. I changed the line of code above in order to have a bin interval which should better reflect the asymmetric range of values of ReLUs (approximately; I may be missing some bigger values).
Since this increases the range, I also considered more bins with This is what I get. |
i think somewhat you have similar figure compared with the reviewing paper |
@gladiator8072 yes indeed. Thanks. I have read the paper and the comments. I am inclined to think that the compression phase is to be ascribed to the saturation of the |
not_so_sure, except bin range, the number of bins might cause some noise effects and also relu is unbound on positive side, implies that the range of such direction is not fixed. please let me know you find some secret :D |
Thanks, I read that document. Naftali Tishby and @ravidziv state that the authors of the ICLR paper
However, they do not explain how such information should be estimated in practice, and the code they provide here certainly does a wrong estimate for |
@gladiator8072 The code for that ICLR paper is here https://github.com/artemyk/ibsgd |
awesome! i'm going to study this!! yeah... they didn't mention the correct estimation very detail |
Hi, |
Hi, I have been running your code with the option
-activation_function=1
, i.e. with ReLUs according to the README. However, I noticed that binning for mutual info calculation is performed in between -1 and 1 independent of the activation function.IDNNs/idnns/information/information_process.py
Line 183 in c4abb1d
However, this looks coherent with
tanh
activations only.The text was updated successfully, but these errors were encountered: