Article Number: 118 | VC6 | Post Date: November 20, 2026 | Updated: November 20, 2026
When using the Smart Optimizer, how do I decide which inputs to enable and how wide to make their search ranges?
You should enable only the inputs that are uncertain, and give each one the narrowest range you can support. Each enabled input enlarges the search space, so a run with two or three inputs will generally converge much sooner than a run with ten. Before proceeding, we recommend you review Chapter 27 of the User’s Guide (learn more).
First, set up your best hypothesis by hand, just as you would without the optimizer. Next, go to Optimizer > Show Optimizer and left-click the empty box next to each input you would like searched, such as Vehicle 1 > dynamics > v (t=0s). Inputs that are known from evidence, such as a surveyed impact location or an EDR speed, should be left unchecked.
There are two ways to set a range in the “parameter settings” menu. You can enter “min value” and “max value” directly.
You can also enable “relative”. The “value” field is then populated from the object’s own input field, and “delta value” sets the search window above and below it. This is useful for inputs such as yaw, where you have a good estimate and would like to search within a few degrees of it.
Estimating a range
Each range should come from something independent of the optimizer, such as a hand calculation, published test data, or a few preliminary runs. Here we use the slide-to-stop example from Chapter 27, where a vehicle brakes to a stop over a distance \(d\) = 107.1 ft on a flat, level surface with a drag factor \(f\) between 0.70 and 0.80. The initial speed is given by:
$$ v_i = \sqrt{2 f g d} $$
Using the lower and upper values of \(f\), we have:
$$ v_i = \sqrt{2\,(0.70)\,(32.2\ \text{ft/s}^2)\,(107.1\ \text{ft})} = 69.5\ \text{ft/s} = 47.4\ \text{mph} $$
$$ v_i = \sqrt{2\,(0.80)\,(32.2\ \text{ft/s}^2)\,(107.1\ \text{ft})} = 74.3\ \text{ft/s} = 50.6\ \text{mph} $$
A search range of 45 mph to 53 mph covers this estimate with some margin. A range of 0 mph to 100 mph also contains the solution, but many of the trials will be spent on speeds the evidence already excludes. In the below image we show the Chapter 27 result for this example, where the wide range of 0 mph to 100 mph was used. The optimizer still arrives at initial speeds from 47 mph to 51 mph, in agreement with the hand calculation, but a narrower range will get there in fewer iterations.
Checking the result
After the run is complete, left-click on an enabled input to see its values for the final generation, sorted by deviation. If the best iterations sit at “min value” or “max value”, the range is likely too narrow, or the starting hypothesis should be revisited. Widen the range and run the optimizer again, since a range that is too narrow can exclude valid solutions.
Uncertainty in the physical evidence should be set in the constraint objects rather than in the input ranges. In the constraint object’s “misc” menu, use “radius”, “delta yaw”, “min v”, and “max v” to set the tolerance for each constraint, and use the weights to prioritize one constraint over another.
For collisions with several unknown inputs, we recommend solving for one vehicle at a time, and repeating the run from a different starting point to check for local minima.
Note, if you change an object’s input value after enabling “relative”, the “value” field is not updated automatically. Toggle “relative” off and on to read the new value.
Upcoming In-Class Training Opportunities
Tags: Smart Optimizer, optimization, search range, sensitivity
© 2026 Virtual CRASH, LLC. All Rights Reserved