Skip to content

Commit

Permalink
Merge pull request #272 from adrhill/ah/fix-vgg-dropout
Browse files Browse the repository at this point in the history 
Fix VGG dropout probability
  • Loading branch information
@theabhirath
theabhirath authored Jan 18, 2024
2 parents eed0c64 + 01bb4ad commit 052d311
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 3 deletions.
2 changes: 1 addition & 1 deletion Project.toml
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name = "Metalhead"
uuid = "dbeba491-748d-5e0e-a39e-b530a07fa0cc"
version = "0.9.2"
version = "0.9.3"

[deps]
Artifacts = "56f22d72-fd6d-98f1-02f0-08ddc0907c33"
Expand Down
5 changes: 3 additions & 2 deletions src/convnets/vgg.jl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ Create a VGG style model with specified `depth`.
([reference](https://arxiv.org/abs/1409.1556v6)).
!!! warning
`VGG` does not currently support pretrained weights for the `batchnorm = true` option.
# Arguments
Expand All @@ -130,7 +130,8 @@ end
function VGG(depth::Integer; pretrain::Bool = false, batchnorm::Bool = false,
inchannels::Integer = 3, nclasses::Integer = 1000)
_checkconfig(depth, keys(VGG_CONFIGS))
layers = vgg((224, 224); config = VGG_CONFIGS[depth], batchnorm, inchannels, nclasses)
layers = vgg((224, 224); config = VGG_CONFIGS[depth], batchnorm, inchannels, nclasses,
dropout_prob = 0.5)
model = VGG(layers)
if pretrain
artifact_name = string("vgg", depth)
Expand Down

2 comments on commit 052d311

@theabhirath
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/99076

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.9.3 -m "<description of version>" 052d3111f4ccd063042b1cc8363b5ef74e3d50d4
git push origin v0.9.3

Please sign in to comment.