From 987d65925a409ffa98e9a4d701f303831252b737 Mon Sep 17 00:00:00 2001 From: Dominik Krupke Date: Tue, 16 Jul 2024 17:17:06 +0200 Subject: [PATCH] Fixed sentence --- 04_modelling.md | 13 +++++++------ README.md | 13 +++++++------ 2 files changed, 14 insertions(+), 12 deletions(-) diff --git a/04_modelling.md b/04_modelling.md index 847cdc0..3051105 100644 --- a/04_modelling.md +++ b/04_modelling.md @@ -601,12 +601,13 @@ model.add(x + y == 10).only_enforce_if([b1, ~b2]) # only enforce if b1 AND NOT > [!WARNING] > -> While `only_enforce_if` often enhances the efficiency of constraint modeling, -> it can still impact the performance of CP-SAT significantly. Doing some -> additional reasoning, you can often find a more efficient way to model your -> problem without having to use `only_enforce_if`. As `only_enforce_if` is often -> a more natural way to model your problem, it is still a good idea to use it to -> get your first prototype running and think about smarter ways later. +> While `only_enforce_if` in CP-SAT is often more efficient than similar +> concepts in classical MIP-solvers, it can still impact the performance of +> CP-SAT significantly. Doing some additional reasoning, you can often find a +> more efficient way to model your problem without having to use +> `only_enforce_if`. As `only_enforce_if` is often a more natural way to model +> your problem, it is still a good idea to use it to get your first prototype +> running and think about smarter ways later. diff --git a/README.md b/README.md index b1dcf7a..d1cdae7 100644 --- a/README.md +++ b/README.md @@ -1000,12 +1000,13 @@ model.add(x + y == 10).only_enforce_if([b1, ~b2]) # only enforce if b1 AND NOT > [!WARNING] > -> While `only_enforce_if` often enhances the efficiency of constraint modeling, -> it can still impact the performance of CP-SAT significantly. Doing some -> additional reasoning, you can often find a more efficient way to model your -> problem without having to use `only_enforce_if`. As `only_enforce_if` is often -> a more natural way to model your problem, it is still a good idea to use it to -> get your first prototype running and think about smarter ways later. +> While `only_enforce_if` in CP-SAT is often more efficient than similar +> concepts in classical MIP-solvers, it can still impact the performance of +> CP-SAT significantly. Doing some additional reasoning, you can often find a +> more efficient way to model your problem without having to use +> `only_enforce_if`. As `only_enforce_if` is often a more natural way to model +> your problem, it is still a good idea to use it to get your first prototype +> running and think about smarter ways later.