Corollary 3
Lax496464.Corollary3 · concepts/Lax496464/Corollary3.lean · lax-496464
No public endorsements yet.
Loading review…
Sign in with ORCIDNatural Language Statement
Theorem
When all preprocessing times are equal, the problem is solved in time. With the total preprocessing time a partial solution has spent is determined by how many jobs it has selected, so the instant the dual table runs over takes only values, and the bound of the second corollary becomes .
Concept map
In the paper
- page 6 of this submission's paper
Lean source view on GitHub
| 1 | import Lax496464.Problems |
| 2 | import Lax496464.ProperInstances |
| 3 | |
| 4 | /-! |
| 5 | --- |
| 6 | title: Corollary 3 |
| 7 | type: theorem |
| 8 | --- |
| 9 | When all preprocessing times are equal, the problem is solved in time. With |
| 10 | the total preprocessing time a partial solution has spent is determined by how |
| 11 | many jobs it has selected, so the instant the dual table runs over takes only |
| 12 | values, and the bound of the second corollary becomes . |
| 13 | |
| 14 | # Formalization Notes |
| 15 | |
| 16 | The slice is stated on the decoded instance, as the existence of a common preprocessing |
| 17 | time, rather than as a condition on the entries of the word. The two say the same thing |
| 18 | on an admissible word, and the first is the condition a reader checks the claim against. |
| 19 | |
| 20 | The uniform case is a restriction on the instance only; no assumption is made about the |
| 21 | weights, which may be arbitrary. That is what distinguishes this corollary from the |
| 22 | unweighted case of the fourth theorem. |
| 23 | |
| 24 | The domain also asks that every processing time be positive, . This is the paper's |
| 25 | standing assumption for the recursions behind the algorithms — a job with has an |
| 26 | empty second operation, and the characterization of the feasible sets, on which everything |
| 27 | rests, is stated for jobs that have a genuine one — but the paper does not repeat it in each |
| 28 | claim, and a statement about a program that reads an arbitrary word has to. |
| 29 | -/ |
| 30 | |
| 31 | namespace Lax496464.Corollary3 |
| 32 | |
| 33 | open Lax496464.WordEncoding Lax496464.Problems Lax496464.ParameterizedComplexity |
| 34 | open Lax496464.ProperInstances |
| 35 | open Lax808846.Ram Lax808846.RamComputes |
| 36 | |
| 37 | open Classical in |
| 38 | /-- **Corollary 3.** With equal preprocessing times the problem is decided within |
| 39 | `c · (n+1)^(m+1)` instructions, plus the cost of sorting. -/ |
| 40 | axiom corollary3_time : |
| 41 | ∃ (prog : Program) (c : ℕ), ∀ w : ℕ, |
| 42 | ComputesInTime w prog |
| 43 | {x | x ∈ DecisionInstances ∧ Fits c w x ∧ |
| 44 | (∃ I W, EncodesDecisionInstance x I W ∧ Uniform I) ∧ |
| 45 | c * (jobCount x + 1) ^ (machineCount x + 1) ≤ 2 ^ w ∧ |
| 46 | (∀ j < jobCount x, 0 < procTime x j)} |
| 47 | (fun x => if Yes x then [1] else [0]) |
| 48 | (fun x => c * (jobCount x + 1) ^ (machineCount x + 1) + c * sortCost x) |
| 49 | |
| 50 | end Lax496464.Corollary3 |
| 51 |
Formalization Notes
The slice is stated on the decoded instance, as the existence of a common preprocessing time, rather than as a condition on the entries of the word. The two say the same thing on an admissible word, and the first is the condition a reader checks the claim against.
The uniform case is a restriction on the instance only; no assumption is made about the weights, which may be arbitrary. That is what distinguishes this corollary from the unweighted case of the fourth theorem.
The domain also asks that every processing time be positive, . This is the paper's standing assumption for the recursions behind the algorithms — a job with has an empty second operation, and the characterization of the feasible sets, on which everything rests, is stated for jobs that have a genuine one — but the paper does not repeat it in each claim, and a statement about a program that reads an arbitrary word has to.
Discussion
Ask a question or add context. Endorsements and structured flags are kept in the review panel above.
0 comments