Fitting and testing models
In a minute
Modelling is a cycle: choose a model type, find its , test it against the facts, then use it to predict. Most marks go to the reasons: why this model, which , and how far you can trust a prediction.
You'll be able to
- Follow the modelling process to choose, fit, test and use a model from 2.5.
- Justify a model from the shape of the data, the properties of its graph or the context.
- Find parameters from an , from given points, or from up to three linear equations solved on your GDC.
- State a reasonable domain for a model in context.
- Test a model against data and comment on whether it is appropriate and reasonable.
- Make predictions from a model and explain the dangers of .
Before you start3 quick questions on what this builds on
Revise first: 1.8 Solving equations with technology, 2.2 Function concepts, domain and range and 2.5 Modelling with functions
The modelling process
A is a function that describes a real situation, approximately. You build one in four steps, and you go round again if the test fails.
Step 1 uses the families from 2.5. Choose from the context, the shape of the data, or both.
Same change each step, such as a fixed charge per hour: linear. Rises to a peak and falls back symmetrically (or falls to a lowest point and rises again): quadratic.
Same percentage change each step, or changing fastest at the start and then levelling off towards a value: exponential. Repeats at regular intervals: sinusoidal. Different rules on different intervals: piecewise.
With a table of data, test the pattern. Equal differences between -values (for equal steps in ) suggest linear. Equal ratios suggest exponential.
Try it first, then reveal one step at a time.
- (a) Each extra hour adds the same amount, so the cost is linear: . is the call-out fee and the rate per hour.
- (b) The pie cools fast at first, then slowly, levelling off at . An exponential model with an asymptote fits: .
- (c) Tides rise and fall again and again with a regular period. A sinusoidal model fits: .
- (a) linear; (b) exponential, levelling off at ; (c) sinusoidal.
Try it first, then reveal one step at a time.
- (a) Differences: , , . They grow, so the data is not linear.
- (b) Ratios: , , . A constant ratio means the same percentage growth each week: exponential.
- The initial value is and the weekly factor is , so .
- Check: , which matches the data.
Finding the parameters
Once you've chosen the type, each unknown parameter needs one fact about the situation. There are three ways to use those facts.
1. Initial condition: put . In this gives , since .
2. Substitute a point: a known value, such as , gives one equation. Solve it on your GDC, writing the equation down first.
3. Simultaneous equations: if several parameters are unknown, substitute one point per parameter. For each point gives a linear equation in , and . Solve the on your GDC.
Try it first, then reveal one step at a time.
- (a) Initial condition: . Since , , so .
- (b) Substitute the point . Write the equation down: .
- Solve on the GDC (solver, or graph both sides and intersect):
- Store the full value of for later parts. Check: .
Try it first, then reveal one step at a time.
- Substitute each point: , and .
- On the GDC, , and stand for , and . Enter the rows ; ; .
- The solver gives , and . So .
- Check with : .
- (b) , so the vertex is a maximum. Axis: , and m.
A reasonable domain
A formula may give an output for any , but the situation does not allow every . The of a model is the set of inputs where it makes sense.
Ask three questions. Where does it start (often )? Where does it stop making sense (a height or a price reaches , a tank is empty)? Must the input be a whole number (people, tickets, items)?
Try it first, then reveal one step at a time.
- The model starts when the stone is thrown, so .
- It stops when the stone hits the sea: solve , giving or .
- Reject , a time before the throw. After the model gives negative heights.
Try it first, then reveal one step at a time.
- (a) A price can't be negative, so .
- The number of tickets can't be negative: , so .
- So . At nobody buys a ticket.
- (b) tickets, a whole number, so it is fine here. For a price like it gives tickets: the model is only approximate.
Testing a model
A model is appropriate if it matches the data and behaves sensibly where the data stops. Test both.
1. Test against data: compare the model's values with the measured values . A small percentage error , from 1.6, means a close fit.
2. Test against the context: check the graph's features. Does it go negative when it can't? Does it keep rising when it must level off? Does an asymptote or a maximum match a real limit?
Try it first, then reveal one step at a time.
- (a) 2024 is . megalitres.
- Percentage error: .
- (b) The error is under , so the model fits 2024 well.
- But it assumes growth every year for ever. Water saving or a drought could break that, so check it against new data.
Try it first, then reveal one step at a time.
- Model A: .
- Model B:
- Total sales can never decrease, let alone be negative. Model A is a downward parabola, so it must turn and fall: its maximum is at .
- Model B increases for all and levels off at its asymptote . That fits total sales slowing down as most buyers already have the game.
- Model B: total sales cannot decrease, but model A falls after and predicts thousand at week 12; model B keeps increasing towards its asymptote .
Predictions and extrapolation
Using a model means substituting into it, or solving it for an input. Then say what the answer means in context, with units.
Exponential growth is the classic danger. Food, space or money runs out, so real growth slows. The further you extrapolate, the less you should trust the answer.
Try it first, then reveal one step at a time.
- (a) , so about rabbits.
- (b) , so about rabbits.
- (c) is inside the data range : interpolation, so the estimate is reliable if the model fits well.
- is far outside it: extrapolation. The island's food and space are limited, so growth will slow. The prediction is probably far too high.
Try it first, then reveal one step at a time.
- (a) Write the equation: .
- Graph and with a window such as , , and find the intersection:
- So downloads reach thousand after about months, during the seventh month.
- (b) is outside the data range , so this is extrapolation. Growth may slow as the app's market fills up, so it may take longer.
Common mistakes
- Rounding a parameter, then using the rounded value. Store the GDC's full value and round only the final answer.
- Giving a 3 s.f. decimal when the exact value of a parameter is asked for. Write the exact value.
- Accepting an impossible prediction, such as negative sales or more people than live in a country. Say the model fails there.
- Giving a context reason when a mathematical one is asked for. Name a feature of the graph, such as the asymptote.
- Leaving a count as a decimal when the nearest integer is asked for. Round once, at the end.
Exam tips
- "Find" a parameter: write the equation you substitute into, then solve it. The written equation earns the method mark even if the GDC answer slips.
- "Comment" on a model: give a judgement (reasonable or not) and a reason from the data or the context.
- "Justify" a model choice: point to the data's pattern (differences, ratios, levelling off) or a property of the curve that matches the context.
Key takeaways
Practise this
15 past-paper questions on Modelling with exponential functions in the AI HL bank, each with a mark scheme and a worked explanation.