Compare sorting and lookup costs
See this course’s project requirements
A tested Python catalog search with linear and binary methods, comparison counts, sortedness checks and a justified method choice.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- A three-case lookup contract with results 5,-1,-1.
- A linear-search trace with six and seven comparisons.
- A sortedness rule and two-step interval trace.
- A terminating binary-search implementation and boundary trace.
- A cost comparison distinguishing lookup from total work.
- A checked algorithm-comparison packet with honest measurement limits.
Review and revise
Use these criteria to check your work and choose what to improve.
- The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
- Normal, boundary and rejected cases are recorded with expected versus observed results.
- The changed case has a correct explanation and does not rely on hidden state.
- The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Want more background?
The idea in everyday life
For IDs [12,18,25,31,44,52,67] and target 52, linear search uses six equality comparisons. Binary search visits two midpoints: 31 and 52. At 31 it evaluates equality (false) then less-than (true); at 52 equality is true. That is three lookup value comparisons plus six adjacent-order comparisons, total nine. Do not include loop-bound or index arithmetic operations in this explicitly defined metric.
Count value comparisons separately from midpoint probes and elapsed time. A midpoint probe may perform equality and less-than comparisons. The supplied binary function validates all adjacent pairs on every call, so its complete call is not logarithmic.
Compare sorting and lookup costs — original worked practice
Count value comparisons separately from midpoint probes and elapsed time. A midpoint probe may perform equality and less-than comparisons. The supplied binary function validates all adjacent pairs on every call, so its complete call is not logarithmic.
For IDs [12,18,25,31,44,52,67] and target 52, linear search uses six equality comparisons. Binary search visits two midpoints: 31 and 52. At 31 it evaluates equality (false) then less-than (true); at 52 equality is true. That is three lookup value comparisons plus six adjacent-order comparisons, total nine. Do not include loop-bound or index arithmetic operations in this explicitly defined metric.
1. Step 1
Trace the six equality comparisons used by linear(values, 52).
You should see: Linear search performs six equality comparisons for target 52.
Count value comparisons separately from midpoint probes and elapsed time. A midpoint probe may perform equality and less-than comparisons. The supplied binary function validates all adjacent pairs on every call, so its complete call is not logarithmic.
2. Step 2
Trace binary midpoint 31: equality is false and less-than is true; midpoint 52: equality is true. Record three value comparisons across two probes.
You should see: Binary lookup performs three value comparisons at two midpoint probes.
Count value comparisons separately from midpoint probes and elapsed time. A midpoint probe may perform equality and less-than comparisons. The supplied binary function validates all adjacent pairs on every call, so its complete call is not logarithmic.
3. Step 3
Add the six adjacent greater-than order checks: three plus six equals nine value comparisons per unchanged successful call.
You should see: The complete call performs nine value comparisons, excluding loop/index operations.
Count value comparisons separately from midpoint probes and elapsed time. A midpoint probe may perform equality and less-than comparisons. The supplied binary function validates all adjacent pairs on every call, so its complete call is not logarithmic.
4. Step 4
Compare reuse of a separately verified unchanged catalog with the supplied function, which rechecks order on every call. State the defined metric and data-change limitation.
You should see: A checked unchanged catalog can support a different optimized design; this supplied implementation still rechecks on each call.
Count value comparisons separately from midpoint probes and elapsed time. A midpoint probe may perform equality and less-than comparisons. The supplied binary function validates all adjacent pairs on every call, so its complete call is not logarithmic.
What to finish
A cost comparison distinguishing lookup from total work.
Watch for this
Describing each checked lookup as logarithmic when the supplied guard scans the entire list first.
How can I tell I understand it?
Reproduce the target-52 trace with six linear comparisons and nine complete binary value comparisons. Identify two midpoint probes separately, and explain why changed data must be revalidated and the supplied guard prevents an end-to-end logarithmic claim.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.