Add group_norm_groups as FOM-specific parameter#82
Closed
michaelmckinsey1 wants to merge 1 commit into
Closed
Conversation
Collaborator
Author
|
We are going to tie this down as a parameter that should not be changed in the config #87, so this change is now irrelevant |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This parameter will affect convergence.
@PatrickRMiles I'm thinking if there is a better way to do this. Should we list a bunch of parameters here like n_categories, n_instances_used_per_fractal, unet_bottleneck_dim or just print the entire config? sharding? We already have variables listed under
# Internal/dev use onlyin the default config, so maybe those can be assumed to impact FOM