Google OR-Tools v9.12
a fast and portable software suite for combinatorial optimization
Loading...
Searching...
No Matches
cp_model_checker.h
Go to the documentation of this file.
1// Copyright 2010-2025 Google LLC
2// Licensed under the Apache License, Version 2.0 (the "License");
3// you may not use this file except in compliance with the License.
4// You may obtain a copy of the License at
5//
6// http://www.apache.org/licenses/LICENSE-2.0
7//
8// Unless required by applicable law or agreed to in writing, software
9// distributed under the License is distributed on an "AS IS" BASIS,
10// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
11// See the License for the specific language governing permissions and
12// limitations under the License.
13
14#ifndef OR_TOOLS_SAT_CP_MODEL_CHECKER_H_
15#define OR_TOOLS_SAT_CP_MODEL_CHECKER_H_
16
17#include <cstdint>
18#include <string>
19#include <vector>
20
21#include "absl/types/span.h"
22#include "ortools/sat/cp_model.pb.h"
23#include "ortools/sat/sat_parameters.pb.h"
24
25namespace operations_research {
26namespace sat {
27
28// Verifies that the given model satisfies all the properties described in the
29// proto comments. Returns an empty string if it is the case, otherwise fails at
30// the first error and returns a human-readable description of the issue.
31//
32// The extra parameter is internal and mainly for debugging. After the problem
33// has been presolved, we have a stricter set of properties we want to enforce.
34//
35// TODO(user): Add any needed overflow validation because we are far from
36// exhaustive. We could also run a small presolve that tighten variable bounds
37// before the overflow check to facilitate the lives of our users, but it is a
38// some work to put in place.
39std::string ValidateCpModel(const CpModelProto& model,
40 bool after_presolve = false);
41
42// Some validation (in particular the floating point objective) requires to
43// read parameters.
44//
45// TODO(user): Ideally we would have just one ValidateCpModel() function but
46// this was introduced after many users already use ValidateCpModel() without
47// parameters.
48std::string ValidateInputCpModel(const SatParameters& params,
49 const CpModelProto& model);
50
51// Check if a given linear expression can create overflow. It is exposed to test
52// new constraints created during the presolve.
53bool PossibleIntegerOverflow(const CpModelProto& model,
54 absl::Span<const int> vars,
55 absl::Span<const int64_t> coeffs,
56 int64_t offset = 0);
57
58// Verifies that the given variable assignment is a feasible solution of the
59// given model. The values vector should be in one to one correspondence with
60// the model.variables() list of variables.
61//
62// The last two arguments are optional and help debugging a failing constraint
63// due to presolve.
64bool SolutionIsFeasible(const CpModelProto& model,
65 absl::Span<const int64_t> variable_values,
66 const CpModelProto* mapping_proto = nullptr,
67 const std::vector<int>* postsolve_mapping = nullptr);
68
69// Checks a single constraint for feasibility.
70// This has some overhead, and should only be used for debugging.
71// The full model is needed for scheduling constraints that refers to intervals.
72bool ConstraintIsFeasible(const CpModelProto& model,
73 const ConstraintProto& constraint,
74 absl::Span<const int64_t> variable_values);
75
76} // namespace sat
77} // namespace operations_research
78
79#endif // OR_TOOLS_SAT_CP_MODEL_CHECKER_H_
std::string ValidateInputCpModel(const SatParameters &params, const CpModelProto &model)
std::string ValidateCpModel(const CpModelProto &model, bool after_presolve)
bool SolutionIsFeasible(const CpModelProto &model, absl::Span< const int64_t > variable_values, const CpModelProto *mapping_proto, const std::vector< int > *postsolve_mapping)
bool ConstraintIsFeasible(const CpModelProto &model, const ConstraintProto &constraint, absl::Span< const int64_t > variable_values)
bool PossibleIntegerOverflow(const CpModelProto &model, absl::Span< const int > vars, absl::Span< const int64_t > coeffs, int64_t offset)
In SWIG mode, we don't want anything besides these top-level includes.