You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can also notice that before the change, pooling and relu layers are not printed.
If a "competitor" didn't notice that, it would be (slightly, if not intented) unfair to others. So I think maybe it would be better to optimize profile.py to take this issue into account or give a standard implementation of models to everyone.
The text was updated successfully, but these errors were encountered:
We used the DenseNet model cloned from Kuangliu. In this code the pooling layer and ReLu layer are defined by:
Instead of using:
In the
profile.py
, as the code:So the scoring system will not count the pooling layers and ReLu layers and then shows a fake score slightly better than the real one.
In practise, I here use our best model as an example. By changing replace this line of original code by a
nn.module
version:I got a different number of operations as:
We can also notice that before the change, pooling and relu layers are not printed.
If a "competitor" didn't notice that, it would be (slightly, if not intented) unfair to others. So I think maybe it would be better to optimize
profile.py
to take this issue into account or give a standard implementation of models to everyone.The text was updated successfully, but these errors were encountered: