I don't think I'm talking myself out of a job quite yet. I'll elaborate on my earlier bit - and I think this applies fairly broadly through all levels of engineering and problem solving:DaveW wrote:You sound like someone talking himself out of a job....Jersey Tom wrote:.. how much is it worth sweating the fine details? What's their level of relevance to begin with?
[...]
That could be called sweating over the fine details, but the more successful teams are generally those that pay attention to such details.
There's sweating details for details' sake... there's chasing relevant details... and then there's chasing relevant details in the right order.
The first is a mark of poor / inexperienced engineering, IMO.. and the last is the mark of experience. That's the value in hiring experienced and practical experts, to avoid getting lost in minutiae which isn't going to contribute to better performance. I know of organizations who have gone that route, investing immense time, money, and effort into some super high fidelity modeling of "X" - and then it ultimately having no impact on how they set the car up or go to a race. It amazes me how many high profile organizations have tales of such things.
It screws you over doubly. I'd say it's rare to be sitting around having to really noodle on the question, "Well what more can we do to get performance?" More often you have a list of potential things that you couldn't possibly all get done in several years, and all you have is several months of off season to pursue them. So if you pick the wrong thing to work on, not only is it money out the window but it's time you could have been spending on something with more ROI.
In any event, first question that needs to be asked is, "How is understanding/pursuing this going to make the car go faster?" Next (or going along with it), "Is this really going to change my decision making process?" Then, "What's the level of significance?" Only then can you decide whether to jump down the rabbit hole now, or shelve it and look at it in the near future, or box it up and say it isn't anywhere on the radar yet.
So in this case maybe the first step would be to play around with arbitrary numbers of damping in your model first. See how big it has to be to be of real consequence. Maybe it winds up being on the same order of what you think are ballpark numbers for tires. Maybe it winds up being inconsequential.