Change one setup variable, then prove it

Generated from content/lms/platform-specific-spec-miata/04-set-the-alignment-baseline-that-makes-the-car-honest/04-adjust-one-variable-at-a-time.md; edit the source file, not this page.

Source path: content/lms/platform-specific-spec-miata/04-set-the-alignment-baseline-that-makes-the-car-honest/04-adjust-one-variable-at-a-time.md

Course: Race a Spec Miata by the rulebook

Module: Set the alignment baseline that makes the car honest

Estimated duration: 45 minutes

The skill in this lesson is not knowing every alignment number. The skill is learning how to make a setup change without lying to yourself about what caused the result. In an alignment-baseline module, that matters because the car only becomes honest when the driver and crew stop blending variables together. If you change rear toe, front camber, tire pressure, and shock settings between runs, then come back saying the car is better, you have not learned which change helped. You have created a mystery with a faster lap attached to it.

The rule is simple: change one variable, run a controlled comparison, collect both driver feedback and measurable evidence, then return to the baseline often enough to know whether the track, tire condition, or driver changed under you. The bonded corpus supports this through a disciplined test method described around configuration testing: run one configuration for a set of laps, change only the configuration under test, average the laps, discard obvious abnormal laps, and return periodically to baseline because conditions and tires can move the goalposts during the session. That method is shown in an aerodynamic example, but the logic is exactly the same for alignment and balance work. The point is not that a Spec Miata alignment behaves like a wing. The point is that a test is only meaningful when the cause is isolated.

For you as the driver, this is part of the job. Bentley states that understanding chassis and suspension adjustments and what they mean to the driver is critical, and the Speed Secrets version of the same guidance says to ask or read until you understand the adjustment. That does not mean you need to become a race engineer before your next HPDE or club race. It means you must know enough to describe the car accurately, change only the thing you meant to change, and judge the result against a baseline instead of against your mood after lunch.

The mechanism behind the method starts at the tires. The suspension and alignment do not create grip in the abstract. The tires are the four contact patches through which the car accelerates, brakes, and changes direction. The same contact patches transmit the control inputs you ask for, and they also send most of the sensory information you use to keep or regain control. That makes setup testing both powerful and easy to corrupt. If a change improves how the tire is used, the driver may feel more confidence, a cleaner rotation, better mid-corner support, or a less nervous exit. If a different variable moved at the same time, those sensations still arrive through the same tires, but now you cannot tell which cause produced them.

The second mechanism is balance. The corpus emphasizes that cornering power and vehicle balance come from a linear car with good mechanical grip, and that mechanical grip is influenced by suspension kinematics. It also warns that suspension design is a world of compromises where experienced people disagree about the details. That is why one-variable testing matters even more at the amateur level. You are not trying to win a philosophical argument about suspension theory in the paddock. You are trying to find out whether one change made this car, on this tire, with this driver, on this track, behave more honestly.

Honest does not always mean faster on the first lap. An honest car is one whose behavior repeats. If you turn in with the same speed and brake release, it gives you the same response. If the rear steps out, it does so for a reason you can name, not randomly. If the front washes, it happens in a consistent phase of the corner rather than appearing once on entry, once at apex, and once on throttle. The lesson title says change one variable, but the deeper aim is repeatability. Repeatability lets you connect cause and effect.

Here is the working sequence. First, define the baseline before you touch the car. The sibling lessons cover the precision alignment, rear toe, seat ballast, and left-right symmetry pieces, so do not duplicate that work here. For this lesson, your baseline is the exact state of the car at the start of the test: alignment sheet, tire pressures as measured, tire set, fuel load if you are tracking it, driver ballast if used, and the session conditions you can observe. You do not need a professional engineering notebook, but you do need enough written detail that tomorrow you could put the car back where it was.

Second, define the question. A poor question is whether the car is better. A usable question is whether one change improved one behavior in one phase of the corner without creating a larger problem elsewhere. For example, you might ask whether an alignment adjustment reduces entry nervousness, whether it improves mid-corner support, or whether it makes the exit easier to repeat. Keep the question narrow. If you cannot say what symptom you are testing, you are not ready to make the change.

Third, pick the variable. The variable may be an alignment setting, a pressure target, or another configuration item, but in this module the focus stays on alignment-baseline work. Because other lessons handle rear toe, ballast, and symmetry in detail, your responsibility here is the test discipline. Choose one knob. Do not let convenience turn the test into a bundle. If the car is already on the plates and somebody suggests making two helpful tweaks while you are there, pause. Two helpful tweaks make one unhelpful conclusion.

Fourth, run enough laps to give the car and driver a fair sample. The corpus example uses five laps per configuration in a wing test. For an intermediate Spec Miata driver, five representative laps is a useful mental model because it discourages judging from a single flyer. Your first lap may be tire warm-up or traffic. Your last lap may be affected by tire heat, fatigue, or a local yellow. A tiny sample lets noise masquerade as signal. The exact number may change with event format, but the principle does not: collect a repeatable sample, not a single emotional lap.

Fifth, record two kinds of evidence. Record what you felt, and record what the timing or data shows. The corpus on data logging emphasizes useful results, calibration, practical problem avoidance, and strategies to extract information for mechanics, engineers, and drivers. That does not require an expensive system. A basic logger, sector times, lap times, and disciplined notes can reveal enough if the test is controlled. The data tells you whether the car went faster, where it went faster, and whether the gain repeated. Your feedback tells you whether the gain came from a behavior you can use under pressure.

Sixth, compare averages and patterns, not heroic exceptions. The corpus example records lap-time averages and discards abnormal high or low times. That is a practical way to avoid being fooled by traffic, a mistake, or one unusually brave lap. In your notes, separate representative laps from contaminated laps. A lap with a point-by, a big correction, or a missed shift is not evidence that the setup is wrong. It is evidence that the lap is not a clean sample. Likewise, a single personal-best lap is not proof that the change worked if the other laps became less repeatable.

Seventh, return to baseline periodically. This is the step drivers skip because it feels like going backward. It is not backward. It is the part that protects the truth. The corpus is clear that conditions may change during a session, and tire deterioration can move the baseline. If the track gets warmer, a breeze changes, rubber goes down, or the tires age through the day, the second configuration may look better or worse for reasons unrelated to the adjustment. Returning to baseline asks whether the original car still behaves like the original car. If it does not, the test environment moved.

For intermediate drivers, the hardest part is usually not the wrenching. It is separating driving adaptation from setup effect. You are learning every lap. If you make a change and then drive the next session with better eyes, better brake release, or more commitment, the lap timer may reward the driver more than the setup. That is good driving progress, but it is not setup evidence unless you control for it. Your baseline return is the simplest protection. If you go back to the old setting and the speed stays, the driver may have improved. If the old behavior returns, the setup change probably did something real.

Driver feedback must also be written in phases. Do not say the car understeers. Say when it understeers. Entry understeer, mid-corner understeer, and exit understeer are different problems. Do not say the rear is loose. Say whether it is loose as you release brake, at maintenance throttle, or when you pick up throttle. The corpus does not give a Spec Miata setup chart here, so this lesson will not pretend to prescribe the fix. Your job is to make the symptom sharp enough that one variable can be tested against it.

A useful feedback note has four parts: corner phase, driver input, car response, and confidence cost. For example, you might write that on turn-in the car needed an extra steering correction after brake release, which delayed throttle pickup. Or you might write that the car supported the same entry speed with less hand correction and let you pick up throttle at the same point for three laps in a row. Those notes are more valuable than broad adjectives because they let you test whether the same symptom changed after the adjustment.

Data should be used with the same humility. The corpus points toward calibrated data logging and useful extraction, not blind worship of traces. If the logger is poorly installed, poorly calibrated, or misunderstood, it can give false confidence. Use data to ask better questions. Did the minimum speed improve in the target corner? Did the sector improve where the driver felt the car was better? Did the gain repeat, or was it one lap? Did another sector get worse? A setup change that wins one corner but costs the next straight may still be wrong for the lap.

The phrase one variable can sound too strict for real paddock life. Sometimes a change forces a companion action just to keep the car in a measurable state. For example, after an alignment change, you may need to recheck tire pressures or verify that nothing else moved. That does not mean you are testing tire pressure too. It means you are protecting the test from accidental variables. The discipline is to distinguish the intended variable from housekeeping that keeps the baseline honest. Write both down.

The method also forces you to respect uncertainty. The corpus notes that suspension details involve compromises and disagreement even among designers. That should make you cautious about sweeping conclusions from one afternoon. If your test says a change helped today, it helped under today's conditions with today's driver and tire condition. That is still useful. It is just not a universal law. A good setup notebook is a growing map of evidence, not a pile of commandments.

The right conclusion can be yes, no, or not proven. Yes means the changed configuration produced a repeated improvement in the target behavior, supported by driver notes and timing or data, and the baseline return did not explain it away. No means the change did not improve the target behavior or introduced a bigger cost. Not proven means the test was contaminated by traffic, weather, tire condition, driver inconsistency, or too small a sample. Intermediate drivers often hate not proven because it feels inconclusive. In reality, not proven is a sign that you are becoming more honest. You refused to turn weak evidence into setup doctrine.

There is one more benefit: this method lowers tension between driver and crew. Without a disciplined test, the driver says the car is bad, the crew changes several things, the driver adapts, and nobody knows what worked. With a one-variable test, the conversation becomes specific. The driver reports a symptom. The crew changes one item. The driver runs the same corners with the same intent. The group compares notes and data. That is how amateur testing starts to resemble the professional discipline described in the corpus, even with basic tools.

For a Spec Miata driver setting an alignment baseline, keep the scope narrow. Do not use this lesson to chase every possible setup knob. Use it to protect the lessons around it. The precision alignment gives you a known starting point. Rear toe work gives you one critical balance lever. Driver ballast makes measurements repeatable. Left-right symmetry gives feedback about whether the car is square and honest. This lesson tells you how to test any one of those outcomes without turning the car into a moving pile of unknowns.

At your next event, your standard should be this: before you change the car, you can name the symptom, the single variable, the expected improvement, the sample size, the evidence you will collect, and the condition under which you will return to baseline. If you cannot do those things, wait. A setup change made without a test plan may still make the car faster, but it will not teach you much. The purpose of a baseline is not to freeze the car forever. The purpose is to give every future change something honest to push against.

Worked example: translating the five-lap configuration test to an alignment day

The corpus gives a practical test pattern from an aerodynamic comparison: one configuration was run, only the configuration under test was changed, laps were averaged, abnormal laps were removed, and the baseline was revisited because conditions and tires can change. Apply that same pattern to a Spec Miata alignment day without importing any aero assumptions.

Start with the baseline alignment already covered elsewhere in this module. Your question is narrow: does one alignment change make the target corner phase easier to repeat? You choose one variable and leave the rest of the car alone. You run a short baseline sample, aiming for five representative laps if the session format allows it. You write notes immediately after the run: where the symptom appeared, what input you were making, how the car responded, and whether the response cost confidence or lap time.

Then you make only the planned change. You do not add a second alignment tweak because the car is already on the rack. You do not change pressure targets as a performance experiment at the same time. You do normal checks so the car is safe and measurable, but the test variable remains one item. Then you run the same plan again. You compare the average of representative laps, not just the fastest lap, and you mark laps contaminated by traffic or mistakes so they do not become fake evidence.

The conclusion is not simply faster or slower. If the lap average improves and your notes say the target behavior improved in the same phase of the corner, the change has evidence behind it. If the lap time improves but the driver notes do not match the intended symptom, you may have found a driver improvement, a condition change, or a benefit somewhere else. If the car feels better but the average gets worse, you need to decide whether the comfort is useful or whether it hides a time cost. The point is that the test produces a defensible next question instead of a paddock argument.

Worked example: when the track or tires move the baseline

Imagine the morning baseline run feels nervous on entry, so you make one alignment change to calm that phase. The next run feels better and the lap average improves. If you stop there, the change looks proven. But the corpus warns that weather, track conditions, and tire deterioration can change the baseline during a session. In a real event, the surface may gain rubber, the temperature may rise, the driver may learn the corner, or the tires may move out of their best window.

The disciplined response is to return to baseline, even if it feels inefficient. Put the car back to the original setting as closely as practical and run another representative sample. If the original behavior returns, your change has stronger evidence. If the original setup is now also faster and calmer, the improvement probably did not come only from the adjustment. The track, driver, or tire state changed enough to confuse the first comparison.

This is where many intermediate drivers learn the difference between a setup result and a session result. A session result says the car was faster after lunch. A setup result says the car was faster because one isolated variable changed and the baseline check did not explain the gain away. The second conclusion is harder to earn, but it is the one you can use later.

Common mistakes

The first mistake is the bundled change. You change two or three things because each one seems sensible. The car improves, but the lesson is lost. Good looks like one intended variable, written down before the run, with every other adjustment either unchanged or recorded as safety housekeeping.

The second mistake is the fastest-lap trap. You make a change, set one good lap, and declare victory. The corpus example uses averages and discards abnormal laps because isolated laps can be distorted by traffic, driver risk, or unusual conditions. Good looks like comparing representative laps and asking whether the gain repeated.

The third mistake is refusing to go back to baseline. Drivers skip the return because they do not want to give up a setting that feels promising. Good looks like treating the baseline return as part of the test, not a retreat. If the baseline now behaves differently, the environment changed and the conclusion must be softened.

The fourth mistake is vague feedback. You say the car is loose or tight without saying where in the corner and under which input. Good looks like phase-specific feedback: entry, middle, exit, brake release, maintenance throttle, or throttle pickup. The sharper the symptom, the easier it is to choose one variable and judge the result.

The fifth mistake is uncalibrated data confidence. A logger can be useful, but the corpus emphasizes installing, calibrating, and extracting useful information. Good looks like using data as evidence only when you understand what it is measuring and when the traces support the driver notes rather than replacing them.

The sixth mistake is turning one day into a universal rule. The corpus treats vehicle dynamics and suspension work as a field of compromises, not simple recipes. Good looks like recording the condition, tire state, driver, and track context so the conclusion remains tied to the evidence that produced it.

Drill: baseline-change-baseline proof run

At your next event, run a three-part drill built around one setup question. The drill takes two or three sessions depending on event format, and the success criterion is not a personal best. The success criterion is that you can defend whether the change helped, did not help, or was not proven.

Part one is the baseline sample. Before the session, write the symptom in one sentence and name the corner phase. Run up to five representative laps if the session allows. After the session, write driver notes before looking too deeply at lap times: what the car did, when it did it, and what it cost you. Then mark the laps that were contaminated by traffic, flags, or clear driving mistakes.

Part two is the single change. Make one planned adjustment only. Run the same style of sample. Use the same target corners and the same driving intent. After the run, write notes in the same format. Then compare representative lap averages, sector behavior if you have it, and the specific symptom you named before the test.

Part three is the baseline return. Put the car back to the original setting as closely as practical and repeat a shorter sample if track time is limited. If the original behavior returns, the test result is stronger. If the original setting now behaves like the changed setting, write not proven and record the likely contaminating factors. This drill teaches discipline. It also teaches patience, because the most valuable answer may be that the day did not give you clean evidence.

Cross-references inside this module

Use this lesson after the precision alignment lesson because one-variable testing depends on a known starting point. Use it alongside the rear-toe lesson, but do not let this lesson become a rear-toe tuning guide; rear toe is a specific variable, while this lesson is the method for testing any one variable honestly. Use it with the ballast lesson because repeatable measurement requires the car to be measured in a repeatable state. Use it with the symmetry lesson because left-right consistency can be a feedback signal when the car does not respond the same way in comparable corners.

The common thread is honesty. A baseline alignment, driver ballast, rear-toe discipline, and left-right symmetry all reduce hidden variables. This lesson turns that reduced-variable car into a test platform. You are not just making changes. You are learning which changes deserve to stay.

When this principle breaks down

One-variable testing can be limited by the event. Short sessions, traffic, weather shifts, tire age, and driver learning can all make the evidence weak. The correct response is not to invent certainty. The correct response is to narrow the question, collect what evidence you can, return to baseline when possible, and label the conclusion honestly.

There are also cases where a change cannot be isolated perfectly because the car must remain safe and measurable. If a setup change requires a safety check or a pressure reset to keep the car within a known operating state, record that housekeeping. Do not pretend it was invisible. The method survives real-world messiness when you write down what changed and refuse to overstate the result.

Finally, the principle breaks down when the driver cannot repeat the input. Since the tires carry both control inputs and sensory feedback, inconsistent driving can look like inconsistent setup. If your brake release, turn-in speed, or throttle pickup changes every lap, do fewer setup experiments and more driving repetition. A clean test needs a repeatable driver as much as a repeatable car.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Competition Car Aerodynamics 3rd Edition McBeath Simon	c0cd0f54-6d9c-7f08-e9af-37c31b3421d3	345	1	uio_books_raw_v1
2	Competition Car Aerodynamics 3rd Edition McBeath Simon	4b5e1aa7-14cf-aacf-908a-c47094ea7ba5	504	1	uio_books_raw_v1
3	Ultimate Speed Secrets - Ross Bentley	149c4d5c-d228-0358-acc0-8a92ac07ec7c	50	1	uio_books_raw_v1
4	Speed Secrets Professional Race Driving Techniques Ross Bentley	26bc8e35-76a6-4f72-ea86-df10ba43a636	14	1	uio_books_raw_v1
5	Racing Chassis and Suspension Design Carroll Smith	148524fa-62af-201e-6dff-3b729c84477a	8	1	uio_books_raw_v1
6	Racing Chassis and Suspension Design Carroll Smith	b2ec800e-0c99-a3e6-0e31-c935e35adfbb	9	1	uio_books_raw_v1
7	The Racing and High-Performance Tire Paul Haney	b7f57ad2-d935-17b9-144f-3fb747b5236e	290	1	uio_books_raw_v1
8	Competition Car Aerodynamics 3rd Edition McBeath Simon	9e3001fd-e626-5565-9b11-bc3cab151d27	281	1	uio_books_raw_v1