public final class GlopParameters extends com.google.protobuf.GeneratedMessage implements GlopParametersOrBuilder
next id = 72Protobuf type
operations_research.glop.GlopParameters| Modifier and Type | Class and Description |
|---|---|
static class |
GlopParameters.Builder
next id = 72
|
static class |
GlopParameters.CostScalingAlgorithm
This is only used if use_scaling is true.
|
static class |
GlopParameters.InitialBasisHeuristic
Heuristics to use in the primal simplex to remove fixed slack variables
from the initial basis.
|
static class |
GlopParameters.PricingRule
General strategy used during pricing.
|
static class |
GlopParameters.ScalingAlgorithm
Supported algorithms for scaling:
EQUILIBRATION - progressive scaling by row and column norms until the
marginal difference passes below a threshold.
|
static class |
GlopParameters.SolverBehavior
Like a Boolean with an extra value to let the algorithm decide what is the
best choice.
|
com.google.protobuf.GeneratedMessage.ExtendableBuilder<MessageT extends com.google.protobuf.GeneratedMessage.ExtendableMessage<MessageT>,BuilderT extends com.google.protobuf.GeneratedMessage.ExtendableBuilder<MessageT,BuilderT>>, com.google.protobuf.GeneratedMessage.ExtendableMessage<MessageT extends com.google.protobuf.GeneratedMessage.ExtendableMessage<MessageT>>, com.google.protobuf.GeneratedMessage.ExtendableMessageOrBuilder<MessageT extends com.google.protobuf.GeneratedMessage.ExtendableMessage<MessageT>>, com.google.protobuf.GeneratedMessage.FieldAccessorTable, com.google.protobuf.GeneratedMessage.GeneratedExtension<ContainingT extends com.google.protobuf.Message,T>, com.google.protobuf.GeneratedMessage.UnusedPrivateParameter| Modifier and Type | Method and Description |
|---|---|
boolean |
equals(java.lang.Object obj) |
boolean |
getAllowSimplexAlgorithmChange()
During incremental solve, let the solver decide if it use the primal or
dual simplex algorithm depending on the current solution and on the new
problem.
|
int |
getBasisRefactorizationPeriod()
Number of iterations between two basis refactorizations.
|
boolean |
getChangeStatusToImprecise()
If true, the internal API will change the return status to imprecise if the
solution does not respect the internal tolerances.
|
GlopParameters.CostScalingAlgorithm |
getCostScaling()
optional .operations_research.glop.GlopParameters.CostScalingAlgorithm cost_scaling = 60 [default = CONTAIN_ONE_COST_SCALING]; |
double |
getCrossoverBoundSnappingDistance()
If the starting basis contains FREE variable with bounds, we will move
any such variable to their closer bounds if the distance is smaller than
this parameter.
|
static GlopParameters |
getDefaultInstance() |
GlopParameters |
getDefaultInstanceForType() |
double |
getDegenerateMinistepFactor()
During a degenerate iteration, the more conservative approach is to do a
step of length zero (while shifting the bound of the leaving variable).
|
static com.google.protobuf.Descriptors.Descriptor |
getDescriptor() |
int |
getDevexWeightsResetPeriod()
Devex weights will be reset to 1.0 after that number of updates.
|
double |
getDropMagnitude()
Value in the input LP lower than this will be ignored.
|
double |
getDropTolerance()
In order to increase the sparsity of the manipulated vectors, floating
point values with a magnitude smaller than this parameter are set to zero
(only in some places).
|
double |
getDualFeasibilityTolerance()
Variables whose reduced costs have an absolute value smaller than this
tolerance are not considered as entering candidates.
|
double |
getDualizerThreshold()
When solve_dual_problem is LET_SOLVER_DECIDE, take the dual if the number
of constraints of the problem is more than this threshold times the number
of variables.
|
boolean |
getDualPricePrioritizeNorm()
On some problem like stp3d or pds-100 this makes a huge difference in
speed and number of iterations of the dual simplex.
|
double |
getDualSmallPivotThreshold()
Like small_pivot_threshold but for the dual simplex.
|
boolean |
getDynamicallyAdjustRefactorizationPeriod()
If this is true, then basis_refactorization_period becomes a lower bound on
the number of iterations between two refactorization (provided there is no
numerical accuracy issues).
|
boolean |
getExploitSingletonColumnInInitialBasis()
Whether or not we exploit the singleton columns already present in the
problem when we create the initial basis.
|
GlopParameters.PricingRule |
getFeasibilityRule()
PricingRule to use during the feasibility phase.
|
double |
getHarrisToleranceRatio()
This impacts the ratio test and indicates by how much we allow a basic
variable value that we move to go out of bounds.
|
GlopParameters.InitialBasisHeuristic |
getInitialBasis()
What heuristic is used to try to replace the fixed slack columns in the
initial basis of the primal simplex.
|
double |
getInitialConditionNumberThreshold()
If our upper bound on the condition number of the initial basis (from our
heurisitic or a warm start) is above this threshold, we revert to an all
slack basis.
|
boolean |
getInitializeDevexWithColumnNorms()
Whether we initialize devex weights to 1.0 or to the norms of the matrix
columns.
|
boolean |
getLogSearchProgress()
If true, logs the progress of a solve to LOG(INFO).
|
boolean |
getLogToStdout()
If true, logs will be displayed to stdout instead of using Google log info.
|
double |
getLuFactorizationPivotThreshold()
Threshold for LU-factorization: for stability reasons, the magnitude of the
chosen pivot at a given step is guaranteed to be greater than this
threshold times the maximum magnitude of all the possible pivot choices in
the same column.
|
double |
getMarkowitzSingularityThreshold()
If a pivot magnitude is smaller than this during the Markowitz LU
factorization, then the matrix is assumed to be singular.
|
int |
getMarkowitzZlatevParameter()
How many columns do we look at in the Markowitz pivoting rule to find
a good pivot.
|
double |
getMaxDeterministicTime()
Maximum deterministic time allowed to solve a problem.
|
long |
getMaxNumberOfIterations()
Maximum number of simplex iterations to solve a problem.
|
double |
getMaxNumberOfReoptimizations()
When the solution of phase II is imprecise, we re-run the phase II with the
opposite algorithm from that imprecise solution (i.e., if primal or dual
simplex was used, we use dual or primal simplex, respectively).
|
double |
getMaxTimeInSeconds()
Maximum time allowed in seconds to solve a problem.
|
double |
getMaxValidMagnitude()
Any finite values in the input LP must be below this threshold, otherwise
the model will be reported invalid.
|
double |
getMinimumAcceptablePivot()
We never follow a basis change with a pivot under this threshold.
|
int |
getNumOmpThreads()
Number of threads in the OMP parallel sections.
|
double |
getObjectiveLowerLimit()
The solver will stop as soon as it has proven that the objective is smaller
than objective_lower_limit or greater than objective_upper_limit.
|
double |
getObjectiveUpperLimit()
optional double objective_upper_limit = 41 [default = inf]; |
GlopParameters.PricingRule |
getOptimizationRule()
PricingRule to use during the optimization phase.
|
com.google.protobuf.Parser<GlopParameters> |
getParserForType() |
boolean |
getPerturbCostsInDualSimplex()
When this is true, then the costs are randomly perturbed before the dual
simplex is even started.
|
double |
getPreprocessorZeroTolerance()
A floating point tolerance used by the preprocessors.
|
double |
getPrimalFeasibilityTolerance()
This tolerance indicates by how much we allow the variable values to go out
of bounds and still consider the current solution primal-feasible.
|
boolean |
getProvideStrongOptimalGuarantee()
If true, then when the solver returns a solution with an OPTIMAL status,
we can guarantee that:
- The primal variable are in their bounds.
|
boolean |
getPushToVertex()
If the optimization phases finishes with super-basic variables (i.e.,
variables that either 1) have bounds but are FREE in the basis, or 2) have
no bounds and are FREE in the basis at a nonzero value), then run a "push"
phase to push these variables to bounds, obtaining a vertex solution.
|
int |
getRandomSeed()
At the beginning of each solve, the random number generator used in some
part of the solver is reinitialized to this seed.
|
double |
getRatioTestZeroThreshold()
During the primal simplex (resp.
|
double |
getRecomputeEdgesNormThreshold()
Note that the threshold is a relative error on the actual norm (not the
squared one) and that edge norms are always greater than 1.
|
double |
getRecomputeReducedCostsThreshold()
We estimate the accuracy of the iteratively computed reduced costs.
|
double |
getRefactorizationThreshold()
We estimate the factorization accuracy of B during each pivot by using
the fact that we can compute the pivot coefficient in two ways:
- From direction[leaving_row].
|
double |
getRelativeCostPerturbation()
The magnitude of the cost perturbation is given by
RandomIn(1.0, 2.0) * (
relative_cost_perturbation * cost
+ relative_max_cost_perturbation * max_cost);
|
double |
getRelativeMaxCostPerturbation()
optional double relative_max_cost_perturbation = 55 [default = 1e-07]; |
GlopParameters.ScalingAlgorithm |
getScalingMethod()
optional .operations_research.glop.GlopParameters.ScalingAlgorithm scaling_method = 57 [default = EQUILIBRATION]; |
int |
getSerializedSize() |
double |
getSmallPivotThreshold()
When we choose the leaving variable, we want to avoid small pivot because
they are the less precise and may cause numerical instabilities.
|
double |
getSolutionFeasibilityTolerance()
When the problem status is OPTIMAL, we check the optimality using this
relative tolerance and change the status to IMPRECISE if an issue is
detected.
|
GlopParameters.SolverBehavior |
getSolveDualProblem()
Whether or not we solve the dual of the given problem.
|
boolean |
getUseDedicatedDualFeasibilityAlgorithm()
We have two possible dual phase I algorithms.
|
boolean |
getUseDualSimplex()
Whether or not we use the dual simplex algorithm instead of the primal.
|
boolean |
getUseImpliedFreePreprocessor()
If presolve runs, include the pass that detects implied free variables.
|
boolean |
getUseMiddleProductFormUpdate()
Whether or not to use the middle product form update rather than the
standard eta LU update.
|
boolean |
getUsePreprocessing()
Whether or not we use advanced preprocessing techniques.
|
boolean |
getUseScaling()
Whether or not we scale the matrix A so that the maximum coefficient on
each line and each column is 1.0.
|
boolean |
getUseTransposedMatrix()
Whether or not we keep a transposed version of the matrix A to speed-up the
pricing at the cost of extra memory and the initial tranposition
computation.
|
boolean |
hasAllowSimplexAlgorithmChange()
During incremental solve, let the solver decide if it use the primal or
dual simplex algorithm depending on the current solution and on the new
problem.
|
boolean |
hasBasisRefactorizationPeriod()
Number of iterations between two basis refactorizations.
|
boolean |
hasChangeStatusToImprecise()
If true, the internal API will change the return status to imprecise if the
solution does not respect the internal tolerances.
|
boolean |
hasCostScaling()
optional .operations_research.glop.GlopParameters.CostScalingAlgorithm cost_scaling = 60 [default = CONTAIN_ONE_COST_SCALING]; |
boolean |
hasCrossoverBoundSnappingDistance()
If the starting basis contains FREE variable with bounds, we will move
any such variable to their closer bounds if the distance is smaller than
this parameter.
|
boolean |
hasDegenerateMinistepFactor()
During a degenerate iteration, the more conservative approach is to do a
step of length zero (while shifting the bound of the leaving variable).
|
boolean |
hasDevexWeightsResetPeriod()
Devex weights will be reset to 1.0 after that number of updates.
|
boolean |
hasDropMagnitude()
Value in the input LP lower than this will be ignored.
|
boolean |
hasDropTolerance()
In order to increase the sparsity of the manipulated vectors, floating
point values with a magnitude smaller than this parameter are set to zero
(only in some places).
|
boolean |
hasDualFeasibilityTolerance()
Variables whose reduced costs have an absolute value smaller than this
tolerance are not considered as entering candidates.
|
boolean |
hasDualizerThreshold()
When solve_dual_problem is LET_SOLVER_DECIDE, take the dual if the number
of constraints of the problem is more than this threshold times the number
of variables.
|
boolean |
hasDualPricePrioritizeNorm()
On some problem like stp3d or pds-100 this makes a huge difference in
speed and number of iterations of the dual simplex.
|
boolean |
hasDualSmallPivotThreshold()
Like small_pivot_threshold but for the dual simplex.
|
boolean |
hasDynamicallyAdjustRefactorizationPeriod()
If this is true, then basis_refactorization_period becomes a lower bound on
the number of iterations between two refactorization (provided there is no
numerical accuracy issues).
|
boolean |
hasExploitSingletonColumnInInitialBasis()
Whether or not we exploit the singleton columns already present in the
problem when we create the initial basis.
|
boolean |
hasFeasibilityRule()
PricingRule to use during the feasibility phase.
|
boolean |
hasHarrisToleranceRatio()
This impacts the ratio test and indicates by how much we allow a basic
variable value that we move to go out of bounds.
|
int |
hashCode() |
boolean |
hasInitialBasis()
What heuristic is used to try to replace the fixed slack columns in the
initial basis of the primal simplex.
|
boolean |
hasInitialConditionNumberThreshold()
If our upper bound on the condition number of the initial basis (from our
heurisitic or a warm start) is above this threshold, we revert to an all
slack basis.
|
boolean |
hasInitializeDevexWithColumnNorms()
Whether we initialize devex weights to 1.0 or to the norms of the matrix
columns.
|
boolean |
hasLogSearchProgress()
If true, logs the progress of a solve to LOG(INFO).
|
boolean |
hasLogToStdout()
If true, logs will be displayed to stdout instead of using Google log info.
|
boolean |
hasLuFactorizationPivotThreshold()
Threshold for LU-factorization: for stability reasons, the magnitude of the
chosen pivot at a given step is guaranteed to be greater than this
threshold times the maximum magnitude of all the possible pivot choices in
the same column.
|
boolean |
hasMarkowitzSingularityThreshold()
If a pivot magnitude is smaller than this during the Markowitz LU
factorization, then the matrix is assumed to be singular.
|
boolean |
hasMarkowitzZlatevParameter()
How many columns do we look at in the Markowitz pivoting rule to find
a good pivot.
|
boolean |
hasMaxDeterministicTime()
Maximum deterministic time allowed to solve a problem.
|
boolean |
hasMaxNumberOfIterations()
Maximum number of simplex iterations to solve a problem.
|
boolean |
hasMaxNumberOfReoptimizations()
When the solution of phase II is imprecise, we re-run the phase II with the
opposite algorithm from that imprecise solution (i.e., if primal or dual
simplex was used, we use dual or primal simplex, respectively).
|
boolean |
hasMaxTimeInSeconds()
Maximum time allowed in seconds to solve a problem.
|
boolean |
hasMaxValidMagnitude()
Any finite values in the input LP must be below this threshold, otherwise
the model will be reported invalid.
|
boolean |
hasMinimumAcceptablePivot()
We never follow a basis change with a pivot under this threshold.
|
boolean |
hasNumOmpThreads()
Number of threads in the OMP parallel sections.
|
boolean |
hasObjectiveLowerLimit()
The solver will stop as soon as it has proven that the objective is smaller
than objective_lower_limit or greater than objective_upper_limit.
|
boolean |
hasObjectiveUpperLimit()
optional double objective_upper_limit = 41 [default = inf]; |
boolean |
hasOptimizationRule()
PricingRule to use during the optimization phase.
|
boolean |
hasPerturbCostsInDualSimplex()
When this is true, then the costs are randomly perturbed before the dual
simplex is even started.
|
boolean |
hasPreprocessorZeroTolerance()
A floating point tolerance used by the preprocessors.
|
boolean |
hasPrimalFeasibilityTolerance()
This tolerance indicates by how much we allow the variable values to go out
of bounds and still consider the current solution primal-feasible.
|
boolean |
hasProvideStrongOptimalGuarantee()
If true, then when the solver returns a solution with an OPTIMAL status,
we can guarantee that:
- The primal variable are in their bounds.
|
boolean |
hasPushToVertex()
If the optimization phases finishes with super-basic variables (i.e.,
variables that either 1) have bounds but are FREE in the basis, or 2) have
no bounds and are FREE in the basis at a nonzero value), then run a "push"
phase to push these variables to bounds, obtaining a vertex solution.
|
boolean |
hasRandomSeed()
At the beginning of each solve, the random number generator used in some
part of the solver is reinitialized to this seed.
|
boolean |
hasRatioTestZeroThreshold()
During the primal simplex (resp.
|
boolean |
hasRecomputeEdgesNormThreshold()
Note that the threshold is a relative error on the actual norm (not the
squared one) and that edge norms are always greater than 1.
|
boolean |
hasRecomputeReducedCostsThreshold()
We estimate the accuracy of the iteratively computed reduced costs.
|
boolean |
hasRefactorizationThreshold()
We estimate the factorization accuracy of B during each pivot by using
the fact that we can compute the pivot coefficient in two ways:
- From direction[leaving_row].
|
boolean |
hasRelativeCostPerturbation()
The magnitude of the cost perturbation is given by
RandomIn(1.0, 2.0) * (
relative_cost_perturbation * cost
+ relative_max_cost_perturbation * max_cost);
|
boolean |
hasRelativeMaxCostPerturbation()
optional double relative_max_cost_perturbation = 55 [default = 1e-07]; |
boolean |
hasScalingMethod()
optional .operations_research.glop.GlopParameters.ScalingAlgorithm scaling_method = 57 [default = EQUILIBRATION]; |
boolean |
hasSmallPivotThreshold()
When we choose the leaving variable, we want to avoid small pivot because
they are the less precise and may cause numerical instabilities.
|
boolean |
hasSolutionFeasibilityTolerance()
When the problem status is OPTIMAL, we check the optimality using this
relative tolerance and change the status to IMPRECISE if an issue is
detected.
|
boolean |
hasSolveDualProblem()
Whether or not we solve the dual of the given problem.
|
boolean |
hasUseDedicatedDualFeasibilityAlgorithm()
We have two possible dual phase I algorithms.
|
boolean |
hasUseDualSimplex()
Whether or not we use the dual simplex algorithm instead of the primal.
|
boolean |
hasUseImpliedFreePreprocessor()
If presolve runs, include the pass that detects implied free variables.
|
boolean |
hasUseMiddleProductFormUpdate()
Whether or not to use the middle product form update rather than the
standard eta LU update.
|
boolean |
hasUsePreprocessing()
Whether or not we use advanced preprocessing techniques.
|
boolean |
hasUseScaling()
Whether or not we scale the matrix A so that the maximum coefficient on
each line and each column is 1.0.
|
boolean |
hasUseTransposedMatrix()
Whether or not we keep a transposed version of the matrix A to speed-up the
pricing at the cost of extra memory and the initial tranposition
computation.
|
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable |
internalGetFieldAccessorTable() |
boolean |
isInitialized() |
static GlopParameters.Builder |
newBuilder() |
static GlopParameters.Builder |
newBuilder(GlopParameters prototype) |
GlopParameters.Builder |
newBuilderForType() |
protected GlopParameters.Builder |
newBuilderForType(com.google.protobuf.AbstractMessage.BuilderParent parent) |
static GlopParameters |
parseDelimitedFrom(java.io.InputStream input) |
static GlopParameters |
parseDelimitedFrom(java.io.InputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
static GlopParameters |
parseFrom(byte[] data) |
static GlopParameters |
parseFrom(byte[] data,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
static GlopParameters |
parseFrom(java.nio.ByteBuffer data) |
static GlopParameters |
parseFrom(java.nio.ByteBuffer data,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
static GlopParameters |
parseFrom(com.google.protobuf.ByteString data) |
static GlopParameters |
parseFrom(com.google.protobuf.ByteString data,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
static GlopParameters |
parseFrom(com.google.protobuf.CodedInputStream input) |
static GlopParameters |
parseFrom(com.google.protobuf.CodedInputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
static GlopParameters |
parseFrom(java.io.InputStream input) |
static GlopParameters |
parseFrom(java.io.InputStream input,
com.google.protobuf.ExtensionRegistryLite extensionRegistry) |
static com.google.protobuf.Parser<GlopParameters> |
parser() |
GlopParameters.Builder |
toBuilder() |
void |
writeTo(com.google.protobuf.CodedOutputStream output) |
canUseUnsafe, computeStringSize, computeStringSizeNoTag, emptyBooleanList, emptyDoubleList, emptyFloatList, emptyIntList, emptyList, emptyLongList, getAllFields, getDescriptorForType, getField, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof, internalGetMapField, internalGetMapFieldReflection, isStringEmpty, makeMutableCopy, makeMutableCopy, mergeFromAndMakeImmutableInternal, newFileScopedGeneratedExtension, newInstance, newMessageScopedGeneratedExtension, parseDelimitedWithIOException, parseDelimitedWithIOException, parseUnknownField, parseUnknownFieldProto3, parseWithIOException, parseWithIOException, parseWithIOException, parseWithIOException, serializeBooleanMapTo, serializeIntegerMapTo, serializeLongMapTo, serializeStringMapTo, writeReplace, writeString, writeStringNoTagfindInitializationErrors, getInitializationErrorString, hashFields, toStringaddAll, checkByteStringIsUtf8, toByteArray, toByteString, writeDelimitedTo, writeToclone, finalize, getClass, notify, notifyAll, wait, wait, waitpublic static final int SCALING_METHOD_FIELD_NUMBER
public static final int FEASIBILITY_RULE_FIELD_NUMBER
public static final int OPTIMIZATION_RULE_FIELD_NUMBER
public static final int REFACTORIZATION_THRESHOLD_FIELD_NUMBER
public static final int RECOMPUTE_REDUCED_COSTS_THRESHOLD_FIELD_NUMBER
public static final int RECOMPUTE_EDGES_NORM_THRESHOLD_FIELD_NUMBER
public static final int PRIMAL_FEASIBILITY_TOLERANCE_FIELD_NUMBER
public static final int DUAL_FEASIBILITY_TOLERANCE_FIELD_NUMBER
public static final int RATIO_TEST_ZERO_THRESHOLD_FIELD_NUMBER
public static final int HARRIS_TOLERANCE_RATIO_FIELD_NUMBER
public static final int SMALL_PIVOT_THRESHOLD_FIELD_NUMBER
public static final int MINIMUM_ACCEPTABLE_PIVOT_FIELD_NUMBER
public static final int DROP_TOLERANCE_FIELD_NUMBER
public static final int USE_SCALING_FIELD_NUMBER
public static final int COST_SCALING_FIELD_NUMBER
public static final int INITIAL_BASIS_FIELD_NUMBER
public static final int USE_TRANSPOSED_MATRIX_FIELD_NUMBER
public static final int BASIS_REFACTORIZATION_PERIOD_FIELD_NUMBER
public static final int DYNAMICALLY_ADJUST_REFACTORIZATION_PERIOD_FIELD_NUMBER
public static final int SOLVE_DUAL_PROBLEM_FIELD_NUMBER
public static final int DUALIZER_THRESHOLD_FIELD_NUMBER
public static final int SOLUTION_FEASIBILITY_TOLERANCE_FIELD_NUMBER
public static final int PROVIDE_STRONG_OPTIMAL_GUARANTEE_FIELD_NUMBER
public static final int CHANGE_STATUS_TO_IMPRECISE_FIELD_NUMBER
public static final int MAX_NUMBER_OF_REOPTIMIZATIONS_FIELD_NUMBER
public static final int LU_FACTORIZATION_PIVOT_THRESHOLD_FIELD_NUMBER
public static final int MAX_TIME_IN_SECONDS_FIELD_NUMBER
public static final int MAX_DETERMINISTIC_TIME_FIELD_NUMBER
public static final int MAX_NUMBER_OF_ITERATIONS_FIELD_NUMBER
public static final int MARKOWITZ_ZLATEV_PARAMETER_FIELD_NUMBER
public static final int MARKOWITZ_SINGULARITY_THRESHOLD_FIELD_NUMBER
public static final int USE_DUAL_SIMPLEX_FIELD_NUMBER
public static final int ALLOW_SIMPLEX_ALGORITHM_CHANGE_FIELD_NUMBER
public static final int DEVEX_WEIGHTS_RESET_PERIOD_FIELD_NUMBER
public static final int USE_PREPROCESSING_FIELD_NUMBER
public static final int USE_MIDDLE_PRODUCT_FORM_UPDATE_FIELD_NUMBER
public static final int INITIALIZE_DEVEX_WITH_COLUMN_NORMS_FIELD_NUMBER
public static final int EXPLOIT_SINGLETON_COLUMN_IN_INITIAL_BASIS_FIELD_NUMBER
public static final int DUAL_SMALL_PIVOT_THRESHOLD_FIELD_NUMBER
public static final int PREPROCESSOR_ZERO_TOLERANCE_FIELD_NUMBER
public static final int OBJECTIVE_LOWER_LIMIT_FIELD_NUMBER
public static final int OBJECTIVE_UPPER_LIMIT_FIELD_NUMBER
public static final int DEGENERATE_MINISTEP_FACTOR_FIELD_NUMBER
public static final int RANDOM_SEED_FIELD_NUMBER
public static final int NUM_OMP_THREADS_FIELD_NUMBER
public static final int PERTURB_COSTS_IN_DUAL_SIMPLEX_FIELD_NUMBER
public static final int USE_DEDICATED_DUAL_FEASIBILITY_ALGORITHM_FIELD_NUMBER
public static final int RELATIVE_COST_PERTURBATION_FIELD_NUMBER
public static final int RELATIVE_MAX_COST_PERTURBATION_FIELD_NUMBER
public static final int INITIAL_CONDITION_NUMBER_THRESHOLD_FIELD_NUMBER
public static final int LOG_SEARCH_PROGRESS_FIELD_NUMBER
public static final int LOG_TO_STDOUT_FIELD_NUMBER
public static final int CROSSOVER_BOUND_SNAPPING_DISTANCE_FIELD_NUMBER
public static final int PUSH_TO_VERTEX_FIELD_NUMBER
public static final int USE_IMPLIED_FREE_PREPROCESSOR_FIELD_NUMBER
public static final int MAX_VALID_MAGNITUDE_FIELD_NUMBER
public static final int DROP_MAGNITUDE_FIELD_NUMBER
public static final int DUAL_PRICE_PRIORITIZE_NORM_FIELD_NUMBER
public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()
protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessagepublic boolean hasScalingMethod()
optional .operations_research.glop.GlopParameters.ScalingAlgorithm scaling_method = 57 [default = EQUILIBRATION];hasScalingMethod in interface GlopParametersOrBuilderpublic GlopParameters.ScalingAlgorithm getScalingMethod()
optional .operations_research.glop.GlopParameters.ScalingAlgorithm scaling_method = 57 [default = EQUILIBRATION];getScalingMethod in interface GlopParametersOrBuilderpublic boolean hasFeasibilityRule()
PricingRule to use during the feasibility phase.
optional .operations_research.glop.GlopParameters.PricingRule feasibility_rule = 1 [default = STEEPEST_EDGE];hasFeasibilityRule in interface GlopParametersOrBuilderpublic GlopParameters.PricingRule getFeasibilityRule()
PricingRule to use during the feasibility phase.
optional .operations_research.glop.GlopParameters.PricingRule feasibility_rule = 1 [default = STEEPEST_EDGE];getFeasibilityRule in interface GlopParametersOrBuilderpublic boolean hasOptimizationRule()
PricingRule to use during the optimization phase.
optional .operations_research.glop.GlopParameters.PricingRule optimization_rule = 2 [default = STEEPEST_EDGE];hasOptimizationRule in interface GlopParametersOrBuilderpublic GlopParameters.PricingRule getOptimizationRule()
PricingRule to use during the optimization phase.
optional .operations_research.glop.GlopParameters.PricingRule optimization_rule = 2 [default = STEEPEST_EDGE];getOptimizationRule in interface GlopParametersOrBuilderpublic boolean hasRefactorizationThreshold()
We estimate the factorization accuracy of B during each pivot by using the fact that we can compute the pivot coefficient in two ways: - From direction[leaving_row]. - From update_row[entering_column]. If the two values have a relative difference above this threshold, we trigger a refactorization.
optional double refactorization_threshold = 6 [default = 1e-09];hasRefactorizationThreshold in interface GlopParametersOrBuilderpublic double getRefactorizationThreshold()
We estimate the factorization accuracy of B during each pivot by using the fact that we can compute the pivot coefficient in two ways: - From direction[leaving_row]. - From update_row[entering_column]. If the two values have a relative difference above this threshold, we trigger a refactorization.
optional double refactorization_threshold = 6 [default = 1e-09];getRefactorizationThreshold in interface GlopParametersOrBuilderpublic boolean hasRecomputeReducedCostsThreshold()
We estimate the accuracy of the iteratively computed reduced costs. If it falls below this threshold, we reinitialize them from scratch. Note that such an operation is pretty fast, so we can use a low threshold. It is important to have a good accuracy here (better than the dual_feasibility_tolerance below) to be sure of the sign of such a cost.
optional double recompute_reduced_costs_threshold = 8 [default = 1e-08];hasRecomputeReducedCostsThreshold in interface GlopParametersOrBuilderpublic double getRecomputeReducedCostsThreshold()
We estimate the accuracy of the iteratively computed reduced costs. If it falls below this threshold, we reinitialize them from scratch. Note that such an operation is pretty fast, so we can use a low threshold. It is important to have a good accuracy here (better than the dual_feasibility_tolerance below) to be sure of the sign of such a cost.
optional double recompute_reduced_costs_threshold = 8 [default = 1e-08];getRecomputeReducedCostsThreshold in interface GlopParametersOrBuilderpublic boolean hasRecomputeEdgesNormThreshold()
Note that the threshold is a relative error on the actual norm (not the squared one) and that edge norms are always greater than 1. Recomputing norms is a really expensive operation and a large threshold is ok since this doesn't impact directly the solution but just the entering variable choice.
optional double recompute_edges_norm_threshold = 9 [default = 100];hasRecomputeEdgesNormThreshold in interface GlopParametersOrBuilderpublic double getRecomputeEdgesNormThreshold()
Note that the threshold is a relative error on the actual norm (not the squared one) and that edge norms are always greater than 1. Recomputing norms is a really expensive operation and a large threshold is ok since this doesn't impact directly the solution but just the entering variable choice.
optional double recompute_edges_norm_threshold = 9 [default = 100];getRecomputeEdgesNormThreshold in interface GlopParametersOrBuilderpublic boolean hasPrimalFeasibilityTolerance()
This tolerance indicates by how much we allow the variable values to go out of bounds and still consider the current solution primal-feasible. We also use the same tolerance for the error A.x - b. Note that the two errors are closely related if A is scaled in such a way that the greatest coefficient magnitude on each column is 1.0. This is also simply called feasibility tolerance in other solvers.
optional double primal_feasibility_tolerance = 10 [default = 1e-08];hasPrimalFeasibilityTolerance in interface GlopParametersOrBuilderpublic double getPrimalFeasibilityTolerance()
This tolerance indicates by how much we allow the variable values to go out of bounds and still consider the current solution primal-feasible. We also use the same tolerance for the error A.x - b. Note that the two errors are closely related if A is scaled in such a way that the greatest coefficient magnitude on each column is 1.0. This is also simply called feasibility tolerance in other solvers.
optional double primal_feasibility_tolerance = 10 [default = 1e-08];getPrimalFeasibilityTolerance in interface GlopParametersOrBuilderpublic boolean hasDualFeasibilityTolerance()
Variables whose reduced costs have an absolute value smaller than this tolerance are not considered as entering candidates. That is they do not take part in deciding whether a solution is dual-feasible or not. Note that this value can temporarily increase during the execution of the algorithm if the estimated precision of the reduced costs is higher than this tolerance. Note also that we scale the costs (in the presolve step) so that the cost magnitude range contains one. This is also known as the optimality tolerance in other solvers.
optional double dual_feasibility_tolerance = 11 [default = 1e-08];hasDualFeasibilityTolerance in interface GlopParametersOrBuilderpublic double getDualFeasibilityTolerance()
Variables whose reduced costs have an absolute value smaller than this tolerance are not considered as entering candidates. That is they do not take part in deciding whether a solution is dual-feasible or not. Note that this value can temporarily increase during the execution of the algorithm if the estimated precision of the reduced costs is higher than this tolerance. Note also that we scale the costs (in the presolve step) so that the cost magnitude range contains one. This is also known as the optimality tolerance in other solvers.
optional double dual_feasibility_tolerance = 11 [default = 1e-08];getDualFeasibilityTolerance in interface GlopParametersOrBuilderpublic boolean hasRatioTestZeroThreshold()
During the primal simplex (resp. dual simplex), the coefficients of the direction (resp. update row) with a magnitude lower than this threshold are not considered during the ratio test. This tolerance is related to the precision at which a Solve() involving the basis matrix can be performed. TODO(user): Automatically increase it when we detect that the precision of the Solve() is worse than this.
optional double ratio_test_zero_threshold = 12 [default = 1e-09];hasRatioTestZeroThreshold in interface GlopParametersOrBuilderpublic double getRatioTestZeroThreshold()
During the primal simplex (resp. dual simplex), the coefficients of the direction (resp. update row) with a magnitude lower than this threshold are not considered during the ratio test. This tolerance is related to the precision at which a Solve() involving the basis matrix can be performed. TODO(user): Automatically increase it when we detect that the precision of the Solve() is worse than this.
optional double ratio_test_zero_threshold = 12 [default = 1e-09];getRatioTestZeroThreshold in interface GlopParametersOrBuilderpublic boolean hasHarrisToleranceRatio()
This impacts the ratio test and indicates by how much we allow a basic variable value that we move to go out of bounds. The value should be in [0.0, 1.0) and should be interpreted as a ratio of the primal_feasibility_tolerance. Setting this to 0.0 basically disables the Harris ratio test while setting this too close to 1.0 will make it difficult to keep the variable values inside their bounds modulo the primal_feasibility_tolerance. Note that the same comment applies to the dual simplex ratio test. There, we allow the reduced costs to be of an infeasible sign by as much as this ratio times the dual_feasibility_tolerance.
optional double harris_tolerance_ratio = 13 [default = 0.5];hasHarrisToleranceRatio in interface GlopParametersOrBuilderpublic double getHarrisToleranceRatio()
This impacts the ratio test and indicates by how much we allow a basic variable value that we move to go out of bounds. The value should be in [0.0, 1.0) and should be interpreted as a ratio of the primal_feasibility_tolerance. Setting this to 0.0 basically disables the Harris ratio test while setting this too close to 1.0 will make it difficult to keep the variable values inside their bounds modulo the primal_feasibility_tolerance. Note that the same comment applies to the dual simplex ratio test. There, we allow the reduced costs to be of an infeasible sign by as much as this ratio times the dual_feasibility_tolerance.
optional double harris_tolerance_ratio = 13 [default = 0.5];getHarrisToleranceRatio in interface GlopParametersOrBuilderpublic boolean hasSmallPivotThreshold()
When we choose the leaving variable, we want to avoid small pivot because they are the less precise and may cause numerical instabilities. For a pivot under this threshold times the infinity norm of the direction, we try various countermeasures in order to avoid using it.
optional double small_pivot_threshold = 14 [default = 1e-06];hasSmallPivotThreshold in interface GlopParametersOrBuilderpublic double getSmallPivotThreshold()
When we choose the leaving variable, we want to avoid small pivot because they are the less precise and may cause numerical instabilities. For a pivot under this threshold times the infinity norm of the direction, we try various countermeasures in order to avoid using it.
optional double small_pivot_threshold = 14 [default = 1e-06];getSmallPivotThreshold in interface GlopParametersOrBuilderpublic boolean hasMinimumAcceptablePivot()
We never follow a basis change with a pivot under this threshold.
optional double minimum_acceptable_pivot = 15 [default = 1e-06];hasMinimumAcceptablePivot in interface GlopParametersOrBuilderpublic double getMinimumAcceptablePivot()
We never follow a basis change with a pivot under this threshold.
optional double minimum_acceptable_pivot = 15 [default = 1e-06];getMinimumAcceptablePivot in interface GlopParametersOrBuilderpublic boolean hasDropTolerance()
In order to increase the sparsity of the manipulated vectors, floating point values with a magnitude smaller than this parameter are set to zero (only in some places). This parameter should be positive or zero.
optional double drop_tolerance = 52 [default = 1e-14];hasDropTolerance in interface GlopParametersOrBuilderpublic double getDropTolerance()
In order to increase the sparsity of the manipulated vectors, floating point values with a magnitude smaller than this parameter are set to zero (only in some places). This parameter should be positive or zero.
optional double drop_tolerance = 52 [default = 1e-14];getDropTolerance in interface GlopParametersOrBuilderpublic boolean hasUseScaling()
Whether or not we scale the matrix A so that the maximum coefficient on each line and each column is 1.0.
optional bool use_scaling = 16 [default = true];hasUseScaling in interface GlopParametersOrBuilderpublic boolean getUseScaling()
Whether or not we scale the matrix A so that the maximum coefficient on each line and each column is 1.0.
optional bool use_scaling = 16 [default = true];getUseScaling in interface GlopParametersOrBuilderpublic boolean hasCostScaling()
optional .operations_research.glop.GlopParameters.CostScalingAlgorithm cost_scaling = 60 [default = CONTAIN_ONE_COST_SCALING];hasCostScaling in interface GlopParametersOrBuilderpublic GlopParameters.CostScalingAlgorithm getCostScaling()
optional .operations_research.glop.GlopParameters.CostScalingAlgorithm cost_scaling = 60 [default = CONTAIN_ONE_COST_SCALING];getCostScaling in interface GlopParametersOrBuilderpublic boolean hasInitialBasis()
What heuristic is used to try to replace the fixed slack columns in the initial basis of the primal simplex.
optional .operations_research.glop.GlopParameters.InitialBasisHeuristic initial_basis = 17 [default = TRIANGULAR];hasInitialBasis in interface GlopParametersOrBuilderpublic GlopParameters.InitialBasisHeuristic getInitialBasis()
What heuristic is used to try to replace the fixed slack columns in the initial basis of the primal simplex.
optional .operations_research.glop.GlopParameters.InitialBasisHeuristic initial_basis = 17 [default = TRIANGULAR];getInitialBasis in interface GlopParametersOrBuilderpublic boolean hasUseTransposedMatrix()
Whether or not we keep a transposed version of the matrix A to speed-up the pricing at the cost of extra memory and the initial tranposition computation.
optional bool use_transposed_matrix = 18 [default = true];hasUseTransposedMatrix in interface GlopParametersOrBuilderpublic boolean getUseTransposedMatrix()
Whether or not we keep a transposed version of the matrix A to speed-up the pricing at the cost of extra memory and the initial tranposition computation.
optional bool use_transposed_matrix = 18 [default = true];getUseTransposedMatrix in interface GlopParametersOrBuilderpublic boolean hasBasisRefactorizationPeriod()
Number of iterations between two basis refactorizations. Note that various conditions in the algorithm may trigger a refactorization before this period is reached. Set this to 0 if you want to refactorize at each step.
optional int32 basis_refactorization_period = 19 [default = 64];hasBasisRefactorizationPeriod in interface GlopParametersOrBuilderpublic int getBasisRefactorizationPeriod()
Number of iterations between two basis refactorizations. Note that various conditions in the algorithm may trigger a refactorization before this period is reached. Set this to 0 if you want to refactorize at each step.
optional int32 basis_refactorization_period = 19 [default = 64];getBasisRefactorizationPeriod in interface GlopParametersOrBuilderpublic boolean hasDynamicallyAdjustRefactorizationPeriod()
If this is true, then basis_refactorization_period becomes a lower bound on the number of iterations between two refactorization (provided there is no numerical accuracy issues). Depending on the estimated time to refactorize vs the extra time spend in each solves because of the LU update, we try to balance the two times.
optional bool dynamically_adjust_refactorization_period = 63 [default = true];hasDynamicallyAdjustRefactorizationPeriod in interface GlopParametersOrBuilderpublic boolean getDynamicallyAdjustRefactorizationPeriod()
If this is true, then basis_refactorization_period becomes a lower bound on the number of iterations between two refactorization (provided there is no numerical accuracy issues). Depending on the estimated time to refactorize vs the extra time spend in each solves because of the LU update, we try to balance the two times.
optional bool dynamically_adjust_refactorization_period = 63 [default = true];getDynamicallyAdjustRefactorizationPeriod in interface GlopParametersOrBuilderpublic boolean hasSolveDualProblem()
Whether or not we solve the dual of the given problem. With a value of auto, the algorithm decide which approach is probably the fastest depending on the problem dimensions (see dualizer_threshold).
optional .operations_research.glop.GlopParameters.SolverBehavior solve_dual_problem = 20 [default = LET_SOLVER_DECIDE];hasSolveDualProblem in interface GlopParametersOrBuilderpublic GlopParameters.SolverBehavior getSolveDualProblem()
Whether or not we solve the dual of the given problem. With a value of auto, the algorithm decide which approach is probably the fastest depending on the problem dimensions (see dualizer_threshold).
optional .operations_research.glop.GlopParameters.SolverBehavior solve_dual_problem = 20 [default = LET_SOLVER_DECIDE];getSolveDualProblem in interface GlopParametersOrBuilderpublic boolean hasDualizerThreshold()
When solve_dual_problem is LET_SOLVER_DECIDE, take the dual if the number of constraints of the problem is more than this threshold times the number of variables.
optional double dualizer_threshold = 21 [default = 1.5];hasDualizerThreshold in interface GlopParametersOrBuilderpublic double getDualizerThreshold()
When solve_dual_problem is LET_SOLVER_DECIDE, take the dual if the number of constraints of the problem is more than this threshold times the number of variables.
optional double dualizer_threshold = 21 [default = 1.5];getDualizerThreshold in interface GlopParametersOrBuilderpublic boolean hasSolutionFeasibilityTolerance()
When the problem status is OPTIMAL, we check the optimality using this relative tolerance and change the status to IMPRECISE if an issue is detected. The tolerance is "relative" in the sense that our thresholds are: - tolerance * max(1.0, abs(bound)) for crossing a given bound. - tolerance * max(1.0, abs(cost)) for an infeasible reduced cost. - tolerance for an infeasible dual value.
optional double solution_feasibility_tolerance = 22 [default = 1e-06];hasSolutionFeasibilityTolerance in interface GlopParametersOrBuilderpublic double getSolutionFeasibilityTolerance()
When the problem status is OPTIMAL, we check the optimality using this relative tolerance and change the status to IMPRECISE if an issue is detected. The tolerance is "relative" in the sense that our thresholds are: - tolerance * max(1.0, abs(bound)) for crossing a given bound. - tolerance * max(1.0, abs(cost)) for an infeasible reduced cost. - tolerance for an infeasible dual value.
optional double solution_feasibility_tolerance = 22 [default = 1e-06];getSolutionFeasibilityTolerance in interface GlopParametersOrBuilderpublic boolean hasProvideStrongOptimalGuarantee()
If true, then when the solver returns a solution with an OPTIMAL status, we can guarantee that: - The primal variable are in their bounds. - The dual variable are in their bounds. - If we modify each component of the right-hand side a bit and each component of the objective function a bit, then the pair (primal values, dual values) is an EXACT optimal solution of the perturbed problem. - The modifications above are smaller than the associated tolerances as defined in the comment for solution_feasibility_tolerance (*). (*): This is the only place where the guarantee is not tight since we compute the upper bounds with scalar product of the primal/dual solution and the initial problem coefficients with only double precision. Note that whether or not this option is true, we still check the primal/dual infeasibility and objective gap. However if it is false, we don't move the primal/dual values within their bounds and leave them untouched.
optional bool provide_strong_optimal_guarantee = 24 [default = true];hasProvideStrongOptimalGuarantee in interface GlopParametersOrBuilderpublic boolean getProvideStrongOptimalGuarantee()
If true, then when the solver returns a solution with an OPTIMAL status, we can guarantee that: - The primal variable are in their bounds. - The dual variable are in their bounds. - If we modify each component of the right-hand side a bit and each component of the objective function a bit, then the pair (primal values, dual values) is an EXACT optimal solution of the perturbed problem. - The modifications above are smaller than the associated tolerances as defined in the comment for solution_feasibility_tolerance (*). (*): This is the only place where the guarantee is not tight since we compute the upper bounds with scalar product of the primal/dual solution and the initial problem coefficients with only double precision. Note that whether or not this option is true, we still check the primal/dual infeasibility and objective gap. However if it is false, we don't move the primal/dual values within their bounds and leave them untouched.
optional bool provide_strong_optimal_guarantee = 24 [default = true];getProvideStrongOptimalGuarantee in interface GlopParametersOrBuilderpublic boolean hasChangeStatusToImprecise()
If true, the internal API will change the return status to imprecise if the solution does not respect the internal tolerances.
optional bool change_status_to_imprecise = 58 [default = true];hasChangeStatusToImprecise in interface GlopParametersOrBuilderpublic boolean getChangeStatusToImprecise()
If true, the internal API will change the return status to imprecise if the solution does not respect the internal tolerances.
optional bool change_status_to_imprecise = 58 [default = true];getChangeStatusToImprecise in interface GlopParametersOrBuilderpublic boolean hasMaxNumberOfReoptimizations()
When the solution of phase II is imprecise, we re-run the phase II with the opposite algorithm from that imprecise solution (i.e., if primal or dual simplex was used, we use dual or primal simplex, respectively). We repeat such re-optimization until the solution is precise, or we hit this limit.
optional double max_number_of_reoptimizations = 56 [default = 40];hasMaxNumberOfReoptimizations in interface GlopParametersOrBuilderpublic double getMaxNumberOfReoptimizations()
When the solution of phase II is imprecise, we re-run the phase II with the opposite algorithm from that imprecise solution (i.e., if primal or dual simplex was used, we use dual or primal simplex, respectively). We repeat such re-optimization until the solution is precise, or we hit this limit.
optional double max_number_of_reoptimizations = 56 [default = 40];getMaxNumberOfReoptimizations in interface GlopParametersOrBuilderpublic boolean hasLuFactorizationPivotThreshold()
Threshold for LU-factorization: for stability reasons, the magnitude of the chosen pivot at a given step is guaranteed to be greater than this threshold times the maximum magnitude of all the possible pivot choices in the same column. The value must be in [0,1].
optional double lu_factorization_pivot_threshold = 25 [default = 0.01];hasLuFactorizationPivotThreshold in interface GlopParametersOrBuilderpublic double getLuFactorizationPivotThreshold()
Threshold for LU-factorization: for stability reasons, the magnitude of the chosen pivot at a given step is guaranteed to be greater than this threshold times the maximum magnitude of all the possible pivot choices in the same column. The value must be in [0,1].
optional double lu_factorization_pivot_threshold = 25 [default = 0.01];getLuFactorizationPivotThreshold in interface GlopParametersOrBuilderpublic boolean hasMaxTimeInSeconds()
Maximum time allowed in seconds to solve a problem.
optional double max_time_in_seconds = 26 [default = inf];hasMaxTimeInSeconds in interface GlopParametersOrBuilderpublic double getMaxTimeInSeconds()
Maximum time allowed in seconds to solve a problem.
optional double max_time_in_seconds = 26 [default = inf];getMaxTimeInSeconds in interface GlopParametersOrBuilderpublic boolean hasMaxDeterministicTime()
Maximum deterministic time allowed to solve a problem. The deterministic time is more or less correlated to the running time, and its unit should be around the second (at least on a Xeon(R) CPU E5-1650 v2 @ 3.50GHz). TODO(user): Improve the correlation.
optional double max_deterministic_time = 45 [default = inf];hasMaxDeterministicTime in interface GlopParametersOrBuilderpublic double getMaxDeterministicTime()
Maximum deterministic time allowed to solve a problem. The deterministic time is more or less correlated to the running time, and its unit should be around the second (at least on a Xeon(R) CPU E5-1650 v2 @ 3.50GHz). TODO(user): Improve the correlation.
optional double max_deterministic_time = 45 [default = inf];getMaxDeterministicTime in interface GlopParametersOrBuilderpublic boolean hasMaxNumberOfIterations()
Maximum number of simplex iterations to solve a problem. A value of -1 means no limit.
optional int64 max_number_of_iterations = 27 [default = -1];hasMaxNumberOfIterations in interface GlopParametersOrBuilderpublic long getMaxNumberOfIterations()
Maximum number of simplex iterations to solve a problem. A value of -1 means no limit.
optional int64 max_number_of_iterations = 27 [default = -1];getMaxNumberOfIterations in interface GlopParametersOrBuilderpublic boolean hasMarkowitzZlatevParameter()
How many columns do we look at in the Markowitz pivoting rule to find a good pivot. See markowitz.h.
optional int32 markowitz_zlatev_parameter = 29 [default = 3];hasMarkowitzZlatevParameter in interface GlopParametersOrBuilderpublic int getMarkowitzZlatevParameter()
How many columns do we look at in the Markowitz pivoting rule to find a good pivot. See markowitz.h.
optional int32 markowitz_zlatev_parameter = 29 [default = 3];getMarkowitzZlatevParameter in interface GlopParametersOrBuilderpublic boolean hasMarkowitzSingularityThreshold()
If a pivot magnitude is smaller than this during the Markowitz LU factorization, then the matrix is assumed to be singular. Note that this is an absolute threshold and is not relative to the other possible pivots on the same column (see lu_factorization_pivot_threshold).
optional double markowitz_singularity_threshold = 30 [default = 1e-15];hasMarkowitzSingularityThreshold in interface GlopParametersOrBuilderpublic double getMarkowitzSingularityThreshold()
If a pivot magnitude is smaller than this during the Markowitz LU factorization, then the matrix is assumed to be singular. Note that this is an absolute threshold and is not relative to the other possible pivots on the same column (see lu_factorization_pivot_threshold).
optional double markowitz_singularity_threshold = 30 [default = 1e-15];getMarkowitzSingularityThreshold in interface GlopParametersOrBuilderpublic boolean hasUseDualSimplex()
Whether or not we use the dual simplex algorithm instead of the primal.
optional bool use_dual_simplex = 31 [default = false];hasUseDualSimplex in interface GlopParametersOrBuilderpublic boolean getUseDualSimplex()
Whether or not we use the dual simplex algorithm instead of the primal.
optional bool use_dual_simplex = 31 [default = false];getUseDualSimplex in interface GlopParametersOrBuilderpublic boolean hasAllowSimplexAlgorithmChange()
During incremental solve, let the solver decide if it use the primal or dual simplex algorithm depending on the current solution and on the new problem. Note that even if this is true, the value of use_dual_simplex still indicates the default algorithm that the solver will use.
optional bool allow_simplex_algorithm_change = 32 [default = false];hasAllowSimplexAlgorithmChange in interface GlopParametersOrBuilderpublic boolean getAllowSimplexAlgorithmChange()
During incremental solve, let the solver decide if it use the primal or dual simplex algorithm depending on the current solution and on the new problem. Note that even if this is true, the value of use_dual_simplex still indicates the default algorithm that the solver will use.
optional bool allow_simplex_algorithm_change = 32 [default = false];getAllowSimplexAlgorithmChange in interface GlopParametersOrBuilderpublic boolean hasDevexWeightsResetPeriod()
Devex weights will be reset to 1.0 after that number of updates.
optional int32 devex_weights_reset_period = 33 [default = 150];hasDevexWeightsResetPeriod in interface GlopParametersOrBuilderpublic int getDevexWeightsResetPeriod()
Devex weights will be reset to 1.0 after that number of updates.
optional int32 devex_weights_reset_period = 33 [default = 150];getDevexWeightsResetPeriod in interface GlopParametersOrBuilderpublic boolean hasUsePreprocessing()
Whether or not we use advanced preprocessing techniques.
optional bool use_preprocessing = 34 [default = true];hasUsePreprocessing in interface GlopParametersOrBuilderpublic boolean getUsePreprocessing()
Whether or not we use advanced preprocessing techniques.
optional bool use_preprocessing = 34 [default = true];getUsePreprocessing in interface GlopParametersOrBuilderpublic boolean hasUseMiddleProductFormUpdate()
Whether or not to use the middle product form update rather than the standard eta LU update. The middle form product update should be a lot more efficient (close to the Forrest-Tomlin update, a bit slower but easier to implement). See for more details: Qi Huangfu, J. A. Julian Hall, "Novel update techniques for the revised simplex method", 28 january 2013, Technical Report ERGO-13-0001 http://www.maths.ed.ac.uk/hall/HuHa12/ERGO-13-001.pdf
optional bool use_middle_product_form_update = 35 [default = true];hasUseMiddleProductFormUpdate in interface GlopParametersOrBuilderpublic boolean getUseMiddleProductFormUpdate()
Whether or not to use the middle product form update rather than the standard eta LU update. The middle form product update should be a lot more efficient (close to the Forrest-Tomlin update, a bit slower but easier to implement). See for more details: Qi Huangfu, J. A. Julian Hall, "Novel update techniques for the revised simplex method", 28 january 2013, Technical Report ERGO-13-0001 http://www.maths.ed.ac.uk/hall/HuHa12/ERGO-13-001.pdf
optional bool use_middle_product_form_update = 35 [default = true];getUseMiddleProductFormUpdate in interface GlopParametersOrBuilderpublic boolean hasInitializeDevexWithColumnNorms()
Whether we initialize devex weights to 1.0 or to the norms of the matrix columns.
optional bool initialize_devex_with_column_norms = 36 [default = true];hasInitializeDevexWithColumnNorms in interface GlopParametersOrBuilderpublic boolean getInitializeDevexWithColumnNorms()
Whether we initialize devex weights to 1.0 or to the norms of the matrix columns.
optional bool initialize_devex_with_column_norms = 36 [default = true];getInitializeDevexWithColumnNorms in interface GlopParametersOrBuilderpublic boolean hasExploitSingletonColumnInInitialBasis()
Whether or not we exploit the singleton columns already present in the problem when we create the initial basis.
optional bool exploit_singleton_column_in_initial_basis = 37 [default = true];hasExploitSingletonColumnInInitialBasis in interface GlopParametersOrBuilderpublic boolean getExploitSingletonColumnInInitialBasis()
Whether or not we exploit the singleton columns already present in the problem when we create the initial basis.
optional bool exploit_singleton_column_in_initial_basis = 37 [default = true];getExploitSingletonColumnInInitialBasis in interface GlopParametersOrBuilderpublic boolean hasDualSmallPivotThreshold()
Like small_pivot_threshold but for the dual simplex. This is needed because the dual algorithm does not interpret this value in the same way. TODO(user): Clean this up and use the same small pivot detection.
optional double dual_small_pivot_threshold = 38 [default = 0.0001];hasDualSmallPivotThreshold in interface GlopParametersOrBuilderpublic double getDualSmallPivotThreshold()
Like small_pivot_threshold but for the dual simplex. This is needed because the dual algorithm does not interpret this value in the same way. TODO(user): Clean this up and use the same small pivot detection.
optional double dual_small_pivot_threshold = 38 [default = 0.0001];getDualSmallPivotThreshold in interface GlopParametersOrBuilderpublic boolean hasPreprocessorZeroTolerance()
A floating point tolerance used by the preprocessors. This is used for things like detecting if two columns/rows are proportional or if an interval is empty. Note that the preprocessors also use solution_feasibility_tolerance() to detect if a problem is infeasible.
optional double preprocessor_zero_tolerance = 39 [default = 1e-09];hasPreprocessorZeroTolerance in interface GlopParametersOrBuilderpublic double getPreprocessorZeroTolerance()
A floating point tolerance used by the preprocessors. This is used for things like detecting if two columns/rows are proportional or if an interval is empty. Note that the preprocessors also use solution_feasibility_tolerance() to detect if a problem is infeasible.
optional double preprocessor_zero_tolerance = 39 [default = 1e-09];getPreprocessorZeroTolerance in interface GlopParametersOrBuilderpublic boolean hasObjectiveLowerLimit()
The solver will stop as soon as it has proven that the objective is smaller than objective_lower_limit or greater than objective_upper_limit. Depending on the simplex algorithm (primal or dual) and the optimization direction, note that only one bound will be used at the time. Important: The solver does not add any tolerances to these values, and as soon as the objective (as computed by the solver, so with some imprecision) crosses one of these bounds (strictly), the search will stop. It is up to the client to add any tolerance if needed.
optional double objective_lower_limit = 40 [default = -inf];hasObjectiveLowerLimit in interface GlopParametersOrBuilderpublic double getObjectiveLowerLimit()
The solver will stop as soon as it has proven that the objective is smaller than objective_lower_limit or greater than objective_upper_limit. Depending on the simplex algorithm (primal or dual) and the optimization direction, note that only one bound will be used at the time. Important: The solver does not add any tolerances to these values, and as soon as the objective (as computed by the solver, so with some imprecision) crosses one of these bounds (strictly), the search will stop. It is up to the client to add any tolerance if needed.
optional double objective_lower_limit = 40 [default = -inf];getObjectiveLowerLimit in interface GlopParametersOrBuilderpublic boolean hasObjectiveUpperLimit()
optional double objective_upper_limit = 41 [default = inf];hasObjectiveUpperLimit in interface GlopParametersOrBuilderpublic double getObjectiveUpperLimit()
optional double objective_upper_limit = 41 [default = inf];getObjectiveUpperLimit in interface GlopParametersOrBuilderpublic boolean hasDegenerateMinistepFactor()
During a degenerate iteration, the more conservative approach is to do a step of length zero (while shifting the bound of the leaving variable). That is, the variable values are unchanged for the primal simplex or the reduced cost are unchanged for the dual simplex. However, instead of doing a step of length zero, it seems to be better on degenerate problems to do a small positive step. This is what is recommended in the EXPAND procedure described in: P. E. Gill, W. Murray, M. A. Saunders, and M. H. Wright. "A practical anti- cycling procedure for linearly constrained optimization". Mathematical Programming, 45:437\u2013474, 1989. Here, during a degenerate iteration we do a small positive step of this factor times the primal (resp. dual) tolerance. In the primal simplex, this may effectively push variable values (very slightly) further out of their bounds (resp. reduced costs for the dual simplex). Setting this to zero reverts to the more conservative approach of a zero step during degenerate iterations.
optional double degenerate_ministep_factor = 42 [default = 0.01];hasDegenerateMinistepFactor in interface GlopParametersOrBuilderpublic double getDegenerateMinistepFactor()
During a degenerate iteration, the more conservative approach is to do a step of length zero (while shifting the bound of the leaving variable). That is, the variable values are unchanged for the primal simplex or the reduced cost are unchanged for the dual simplex. However, instead of doing a step of length zero, it seems to be better on degenerate problems to do a small positive step. This is what is recommended in the EXPAND procedure described in: P. E. Gill, W. Murray, M. A. Saunders, and M. H. Wright. "A practical anti- cycling procedure for linearly constrained optimization". Mathematical Programming, 45:437\u2013474, 1989. Here, during a degenerate iteration we do a small positive step of this factor times the primal (resp. dual) tolerance. In the primal simplex, this may effectively push variable values (very slightly) further out of their bounds (resp. reduced costs for the dual simplex). Setting this to zero reverts to the more conservative approach of a zero step during degenerate iterations.
optional double degenerate_ministep_factor = 42 [default = 0.01];getDegenerateMinistepFactor in interface GlopParametersOrBuilderpublic boolean hasRandomSeed()
At the beginning of each solve, the random number generator used in some part of the solver is reinitialized to this seed. If you change the random seed, the solver may make different choices during the solving process. Note that this may lead to a different solution, for example a different optimal basis. For some problems, the running time may vary a lot depending on small change in the solving algorithm. Running the solver with different seeds enables to have more robust benchmarks when evaluating new features. Also note that the solver is fully deterministic: two runs of the same binary, on the same machine, on the exact same data and with the same parameters will go through the exact same iterations. If they hit a time limit, they might of course yield different results because one will have advanced farther than the other.
optional int32 random_seed = 43 [default = 1];hasRandomSeed in interface GlopParametersOrBuilderpublic int getRandomSeed()
At the beginning of each solve, the random number generator used in some part of the solver is reinitialized to this seed. If you change the random seed, the solver may make different choices during the solving process. Note that this may lead to a different solution, for example a different optimal basis. For some problems, the running time may vary a lot depending on small change in the solving algorithm. Running the solver with different seeds enables to have more robust benchmarks when evaluating new features. Also note that the solver is fully deterministic: two runs of the same binary, on the same machine, on the exact same data and with the same parameters will go through the exact same iterations. If they hit a time limit, they might of course yield different results because one will have advanced farther than the other.
optional int32 random_seed = 43 [default = 1];getRandomSeed in interface GlopParametersOrBuilderpublic boolean hasNumOmpThreads()
Number of threads in the OMP parallel sections. If left to 1, the code will not create any OMP threads and will remain single-threaded.
optional int32 num_omp_threads = 44 [default = 1];hasNumOmpThreads in interface GlopParametersOrBuilderpublic int getNumOmpThreads()
Number of threads in the OMP parallel sections. If left to 1, the code will not create any OMP threads and will remain single-threaded.
optional int32 num_omp_threads = 44 [default = 1];getNumOmpThreads in interface GlopParametersOrBuilderpublic boolean hasPerturbCostsInDualSimplex()
When this is true, then the costs are randomly perturbed before the dual simplex is even started. This has been shown to improve the dual simplex performance. For a good reference, see Huangfu Q (2013) "High performance simplex solver", Ph.D, dissertation, University of Edinburgh.
optional bool perturb_costs_in_dual_simplex = 53 [default = false];hasPerturbCostsInDualSimplex in interface GlopParametersOrBuilderpublic boolean getPerturbCostsInDualSimplex()
When this is true, then the costs are randomly perturbed before the dual simplex is even started. This has been shown to improve the dual simplex performance. For a good reference, see Huangfu Q (2013) "High performance simplex solver", Ph.D, dissertation, University of Edinburgh.
optional bool perturb_costs_in_dual_simplex = 53 [default = false];getPerturbCostsInDualSimplex in interface GlopParametersOrBuilderpublic boolean hasUseDedicatedDualFeasibilityAlgorithm()
We have two possible dual phase I algorithms. Both work on an LP that minimize the sum of dual infeasiblities. One use dedicated code (when this param is true), the other one use exactly the same code as the dual phase II but on an auxiliary problem where the variable bounds of the original problem are changed. TODO(user): For now we have both, but ideally the non-dedicated version will win since it is a lot less code to maintain.
optional bool use_dedicated_dual_feasibility_algorithm = 62 [default = true];hasUseDedicatedDualFeasibilityAlgorithm in interface GlopParametersOrBuilderpublic boolean getUseDedicatedDualFeasibilityAlgorithm()
We have two possible dual phase I algorithms. Both work on an LP that minimize the sum of dual infeasiblities. One use dedicated code (when this param is true), the other one use exactly the same code as the dual phase II but on an auxiliary problem where the variable bounds of the original problem are changed. TODO(user): For now we have both, but ideally the non-dedicated version will win since it is a lot less code to maintain.
optional bool use_dedicated_dual_feasibility_algorithm = 62 [default = true];getUseDedicatedDualFeasibilityAlgorithm in interface GlopParametersOrBuilderpublic boolean hasRelativeCostPerturbation()
The magnitude of the cost perturbation is given by RandomIn(1.0, 2.0) * ( relative_cost_perturbation * cost + relative_max_cost_perturbation * max_cost);
optional double relative_cost_perturbation = 54 [default = 1e-05];hasRelativeCostPerturbation in interface GlopParametersOrBuilderpublic double getRelativeCostPerturbation()
The magnitude of the cost perturbation is given by RandomIn(1.0, 2.0) * ( relative_cost_perturbation * cost + relative_max_cost_perturbation * max_cost);
optional double relative_cost_perturbation = 54 [default = 1e-05];getRelativeCostPerturbation in interface GlopParametersOrBuilderpublic boolean hasRelativeMaxCostPerturbation()
optional double relative_max_cost_perturbation = 55 [default = 1e-07];hasRelativeMaxCostPerturbation in interface GlopParametersOrBuilderpublic double getRelativeMaxCostPerturbation()
optional double relative_max_cost_perturbation = 55 [default = 1e-07];getRelativeMaxCostPerturbation in interface GlopParametersOrBuilderpublic boolean hasInitialConditionNumberThreshold()
If our upper bound on the condition number of the initial basis (from our heurisitic or a warm start) is above this threshold, we revert to an all slack basis.
optional double initial_condition_number_threshold = 59 [default = 1e+50];hasInitialConditionNumberThreshold in interface GlopParametersOrBuilderpublic double getInitialConditionNumberThreshold()
If our upper bound on the condition number of the initial basis (from our heurisitic or a warm start) is above this threshold, we revert to an all slack basis.
optional double initial_condition_number_threshold = 59 [default = 1e+50];getInitialConditionNumberThreshold in interface GlopParametersOrBuilderpublic boolean hasLogSearchProgress()
If true, logs the progress of a solve to LOG(INFO). Note that the same messages can also be turned on by displaying logs at level 1 for the relevant files.
optional bool log_search_progress = 61 [default = false];hasLogSearchProgress in interface GlopParametersOrBuilderpublic boolean getLogSearchProgress()
If true, logs the progress of a solve to LOG(INFO). Note that the same messages can also be turned on by displaying logs at level 1 for the relevant files.
optional bool log_search_progress = 61 [default = false];getLogSearchProgress in interface GlopParametersOrBuilderpublic boolean hasLogToStdout()
If true, logs will be displayed to stdout instead of using Google log info.
optional bool log_to_stdout = 66 [default = true];hasLogToStdout in interface GlopParametersOrBuilderpublic boolean getLogToStdout()
If true, logs will be displayed to stdout instead of using Google log info.
optional bool log_to_stdout = 66 [default = true];getLogToStdout in interface GlopParametersOrBuilderpublic boolean hasCrossoverBoundSnappingDistance()
If the starting basis contains FREE variable with bounds, we will move any such variable to their closer bounds if the distance is smaller than this parameter. The starting statuses can contains FREE variables with bounds, if a user set it like this externally. Also, any variable with an initial BASIC status that was not kept in the initial basis is marked as FREE before this step is applied. Note that by default a FREE variable is assumed to be zero unless a starting value was specified via SetStartingVariableValuesForNextSolve(). Note that, at the end of the solve, some of these FREE variable with bounds and an interior point value might still be left in the final solution. Enable push_to_vertex to clean these up.
optional double crossover_bound_snapping_distance = 64 [default = inf];hasCrossoverBoundSnappingDistance in interface GlopParametersOrBuilderpublic double getCrossoverBoundSnappingDistance()
If the starting basis contains FREE variable with bounds, we will move any such variable to their closer bounds if the distance is smaller than this parameter. The starting statuses can contains FREE variables with bounds, if a user set it like this externally. Also, any variable with an initial BASIC status that was not kept in the initial basis is marked as FREE before this step is applied. Note that by default a FREE variable is assumed to be zero unless a starting value was specified via SetStartingVariableValuesForNextSolve(). Note that, at the end of the solve, some of these FREE variable with bounds and an interior point value might still be left in the final solution. Enable push_to_vertex to clean these up.
optional double crossover_bound_snapping_distance = 64 [default = inf];getCrossoverBoundSnappingDistance in interface GlopParametersOrBuilderpublic boolean hasPushToVertex()
If the optimization phases finishes with super-basic variables (i.e., variables that either 1) have bounds but are FREE in the basis, or 2) have no bounds and are FREE in the basis at a nonzero value), then run a "push" phase to push these variables to bounds, obtaining a vertex solution. Note this situation can happen only if a starting value was specified via SetStartingVariableValuesForNextSolve().
optional bool push_to_vertex = 65 [default = true];hasPushToVertex in interface GlopParametersOrBuilderpublic boolean getPushToVertex()
If the optimization phases finishes with super-basic variables (i.e., variables that either 1) have bounds but are FREE in the basis, or 2) have no bounds and are FREE in the basis at a nonzero value), then run a "push" phase to push these variables to bounds, obtaining a vertex solution. Note this situation can happen only if a starting value was specified via SetStartingVariableValuesForNextSolve().
optional bool push_to_vertex = 65 [default = true];getPushToVertex in interface GlopParametersOrBuilderpublic boolean hasUseImpliedFreePreprocessor()
If presolve runs, include the pass that detects implied free variables.
optional bool use_implied_free_preprocessor = 67 [default = true];hasUseImpliedFreePreprocessor in interface GlopParametersOrBuilderpublic boolean getUseImpliedFreePreprocessor()
If presolve runs, include the pass that detects implied free variables.
optional bool use_implied_free_preprocessor = 67 [default = true];getUseImpliedFreePreprocessor in interface GlopParametersOrBuilderpublic boolean hasMaxValidMagnitude()
Any finite values in the input LP must be below this threshold, otherwise the model will be reported invalid. This is needed to avoid floating point overflow when evaluating bounds * coeff for instance. In practice, users shouldn't use super large values in an LP. With the default threshold, even evaluating large constraint with variables at their bound shouldn't cause any overflow.
optional double max_valid_magnitude = 70 [default = 1e+30];hasMaxValidMagnitude in interface GlopParametersOrBuilderpublic double getMaxValidMagnitude()
Any finite values in the input LP must be below this threshold, otherwise the model will be reported invalid. This is needed to avoid floating point overflow when evaluating bounds * coeff for instance. In practice, users shouldn't use super large values in an LP. With the default threshold, even evaluating large constraint with variables at their bound shouldn't cause any overflow.
optional double max_valid_magnitude = 70 [default = 1e+30];getMaxValidMagnitude in interface GlopParametersOrBuilderpublic boolean hasDropMagnitude()
Value in the input LP lower than this will be ignored. This is similar to drop_tolerance but more aggressive as this is used before scaling. This is mainly here to avoid underflow and have simpler invariant in the code, like a * b == 0 iff a or b is zero and things like this.
optional double drop_magnitude = 71 [default = 1e-30];hasDropMagnitude in interface GlopParametersOrBuilderpublic double getDropMagnitude()
Value in the input LP lower than this will be ignored. This is similar to drop_tolerance but more aggressive as this is used before scaling. This is mainly here to avoid underflow and have simpler invariant in the code, like a * b == 0 iff a or b is zero and things like this.
optional double drop_magnitude = 71 [default = 1e-30];getDropMagnitude in interface GlopParametersOrBuilderpublic boolean hasDualPricePrioritizeNorm()
On some problem like stp3d or pds-100 this makes a huge difference in speed and number of iterations of the dual simplex.
optional bool dual_price_prioritize_norm = 69 [default = false];hasDualPricePrioritizeNorm in interface GlopParametersOrBuilderpublic boolean getDualPricePrioritizeNorm()
On some problem like stp3d or pds-100 this makes a huge difference in speed and number of iterations of the dual simplex.
optional bool dual_price_prioritize_norm = 69 [default = false];getDualPricePrioritizeNorm in interface GlopParametersOrBuilderpublic final boolean isInitialized()
isInitialized in interface com.google.protobuf.MessageLiteOrBuilderisInitialized in class com.google.protobuf.GeneratedMessagepublic void writeTo(com.google.protobuf.CodedOutputStream output)
throws java.io.IOException
writeTo in interface com.google.protobuf.MessageLitewriteTo in class com.google.protobuf.GeneratedMessagejava.io.IOExceptionpublic int getSerializedSize()
getSerializedSize in interface com.google.protobuf.MessageLitegetSerializedSize in class com.google.protobuf.GeneratedMessagepublic boolean equals(java.lang.Object obj)
equals in interface com.google.protobuf.Messageequals in class com.google.protobuf.AbstractMessagepublic int hashCode()
hashCode in interface com.google.protobuf.MessagehashCode in class com.google.protobuf.AbstractMessagepublic static GlopParameters parseFrom(java.nio.ByteBuffer data) throws com.google.protobuf.InvalidProtocolBufferException
com.google.protobuf.InvalidProtocolBufferExceptionpublic static GlopParameters parseFrom(java.nio.ByteBuffer data, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws com.google.protobuf.InvalidProtocolBufferException
com.google.protobuf.InvalidProtocolBufferExceptionpublic static GlopParameters parseFrom(com.google.protobuf.ByteString data) throws com.google.protobuf.InvalidProtocolBufferException
com.google.protobuf.InvalidProtocolBufferExceptionpublic static GlopParameters parseFrom(com.google.protobuf.ByteString data, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws com.google.protobuf.InvalidProtocolBufferException
com.google.protobuf.InvalidProtocolBufferExceptionpublic static GlopParameters parseFrom(byte[] data) throws com.google.protobuf.InvalidProtocolBufferException
com.google.protobuf.InvalidProtocolBufferExceptionpublic static GlopParameters parseFrom(byte[] data, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws com.google.protobuf.InvalidProtocolBufferException
com.google.protobuf.InvalidProtocolBufferExceptionpublic static GlopParameters parseFrom(java.io.InputStream input) throws java.io.IOException
java.io.IOExceptionpublic static GlopParameters parseFrom(java.io.InputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws java.io.IOException
java.io.IOExceptionpublic static GlopParameters parseDelimitedFrom(java.io.InputStream input) throws java.io.IOException
java.io.IOExceptionpublic static GlopParameters parseDelimitedFrom(java.io.InputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws java.io.IOException
java.io.IOExceptionpublic static GlopParameters parseFrom(com.google.protobuf.CodedInputStream input) throws java.io.IOException
java.io.IOExceptionpublic static GlopParameters parseFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws java.io.IOException
java.io.IOExceptionpublic GlopParameters.Builder newBuilderForType()
newBuilderForType in interface com.google.protobuf.MessagenewBuilderForType in interface com.google.protobuf.MessageLitepublic static GlopParameters.Builder newBuilder()
public static GlopParameters.Builder newBuilder(GlopParameters prototype)
public GlopParameters.Builder toBuilder()
toBuilder in interface com.google.protobuf.MessagetoBuilder in interface com.google.protobuf.MessageLiteprotected GlopParameters.Builder newBuilderForType(com.google.protobuf.AbstractMessage.BuilderParent parent)
newBuilderForType in class com.google.protobuf.AbstractMessagepublic static GlopParameters getDefaultInstance()
public static com.google.protobuf.Parser<GlopParameters> parser()
public com.google.protobuf.Parser<GlopParameters> getParserForType()
getParserForType in interface com.google.protobuf.MessagegetParserForType in interface com.google.protobuf.MessageLitegetParserForType in class com.google.protobuf.GeneratedMessagepublic GlopParameters getDefaultInstanceForType()
getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuildergetDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilderCopyright © 2024. All rights reserved.