Solver: check and set type to reconcile class and proto type#5009
Merged
shelhamer merged 1 commit intoBVLC:masterfrom Nov 22, 2016
Merged
Solver: check and set type to reconcile class and proto type#5009shelhamer merged 1 commit intoBVLC:masterfrom
shelhamer merged 1 commit intoBVLC:masterfrom
Conversation
the solver checks its proto type (SolverParameter.type) on instantiation: - if the proto type is unspecified it's set according to the class type `Solver::type()` - if the proto type and class type conflict, the solver dies loudly this helps avoid accidental instantiation of a different solver type than intended when the solver def and class differ. guaranteed type information in the SolverParameter will simplify multi-solver coordination too.
Member
Author
|
Merging—CI failed due to transient networking issue. |
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
2 participants
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.
The solver checks its proto type (SolverParameter.type) on instantiation:
Solver::type()This helps avoid accidental instantiation of a different solver type than intended when the solver def and class differ. For instance if the solver def specifies
type: "Nesterov"but one instantiates anSGDSolverwith that def which type the solver is could be a surprise (it's anSGDSolver).Guaranteed type information in the SolverParameter will simplify multi-solver coordination too; in particular it's needed for correctness of #4563.
@cypof