Quote:
Originally Posted by FalconFour
|
When I tried to look at the image all I got was fuzzy blobs. I don't know if that was a problem with my browser or the image you posted.
Quote:
Originally Posted by dcb
Pretending? If you go to the truck stop and weigh your car, wait for a calm day to do your tests, and the program helps get current air density data off the web for your test site to come up with reasonable figures, how is that pretending? Most obd gauges come within 3%, would you say they are "pretending too"?
|
Forgive me, I did not mean to belittle the effort. I thought this was a discussion about how to maximize the potential accuracy of the measurements that can be made with this proposed new feature.
To clarify the point I was trying to make.
Option A: Collect weather data and enter it with a 3 button interface then have the instrument generate numbers for CDA and CRR that have no record of the mass and weather values used to generate the number. Record these numbers as the only data you have with your notes.
Option B: Only collect the basic coast down timing data on the instrument and log this along with all the weather data and other variables on a spread sheet that can also serve as an electronic note book for research notes.
So the choice as I see it is tedious entry and checking of data each time the weather or mass changes and don't keep track of the raw data. Or you can just enter the raw data into a spread sheet where you can organize all the data and notes as an aid in understanding what the data really means. This makes it very easy to recognize and correct errors like a change in mass because you added or removed a tool box or spare tire but forgot to update the value in the instrument before collecting data. When things like the weather data and derived values are displayed together it's much easier to discriminate between which points to believe and which to toss out in a very noisy data set.
To me option B offers much greater flexibility and ability to process any data gathered ultimately leading to greater accuracy and confidence in measurements made. It also makes the instrument code very simple rather then having to code the UI for entering, displaying, and editing all the weather information.
As dcb points out the key to accuracy is careful attention to detail and consistency in the data collection routine. Well organized notes and test logs are a great way to document the testing as well as cross check for silly errors that come up.
FWIW I have 30 years experience in the automotive research field as part of a team that develops specialized Data Acquisition Systems (DAS) to support research programs. Generally on projects I'm working with programmers, engineers, professors, and research scientist that don't get defensive when I suggest there may be a better way of doing something.
Mike