[QST]: CUOPT_MIP_RELATIVE_GAP cannot be set in MILP solving config

[bzk226]

What is your question?

data = {
    "csr_constraint_matrix": {
        "offsets": [0, 2],
        "indices": [0, 1],
        "values": [1.0, 1.0]
    },
    "constraint_bounds": {
        "upper_bounds": [5000.0],
        "lower_bounds": [0.0]
    },
    "objective_data": {
        "coefficients": [1.2, 1.7],
        "scalability_factor": 1.0,
        "offset": 0.0
    },
    "variable_bounds": {
        "upper_bounds": [3000.0, 5000.0],
        "lower_bounds": [0.0, 0.0]
    },
    "maximize": True,
    "variable_names": ["x", "y"],
    "variable_types": ["I", "I"]
    "solver_config":{
        "time_limit": 30,
        'heuristics_only': False,  
        "mip_relative_gap": 0.01 
    }
}

solution = cuopt_service_client.get_LP_solve(data, response_type="dict")

'mip_relative_gap' was considered as extra inputs. How to set relative gap for MILP problems?

[rgsl888prabhu]

What is your question?

data = {
    "csr_constraint_matrix": {
        "offsets": [0, 2],
        "indices": [0, 1],
        "values": [1.0, 1.0]
    },
    "constraint_bounds": {
        "upper_bounds": [5000.0],
        "lower_bounds": [0.0]
    },
    "objective_data": {
        "coefficients": [1.2, 1.7],
        "scalability_factor": 1.0,
        "offset": 0.0
    },
    "variable_bounds": {
        "upper_bounds": [3000.0, 5000.0],
        "lower_bounds": [0.0, 0.0]
    },
    "maximize": True,
    "variable_names": ["x", "y"],
    "variable_types": ["I", "I"]
    "solver_config":{
        "time_limit": 30,
        'heuristics_only': False,  
        "mip_relative_gap": 0.01 
    }
}

solution = cuopt_service_client.get_LP_solve(data, response_type="dict")

'mip_relative_gap' was considered as extra inputs. How to set relative gap for MILP problems?

Hi, there are 2 issues, one is where it is located and another issue with naming which cuOpt needs to fix.

I have shared updated example, but we will fix naming in future.

"solver_config":{
   "time_limit": 30,
   'heuristics_only': False,  
   "tolerances":  {
       "relative_mip_gap": 0.01 
   }
 }

[rgsl888prabhu]

Created an issue for naming NVIDIA/cuopt#193

[bzk226]

Thanks for your example, now I can input mip gap into the solver

[tmckayus]

Actually, you do not have to change the name to "relative_mip_gap". As long as the setting is in the right place under "tolerances" you can still use "mip_relative_gap".

In 25.05 I patched the service to allow both before the validation is done, for backward compatibility. If you use "relative_mip_gap" it will change it internally to mip_relative_gap before setting.