In working with them (I must specify that I work for storm water engineers) I have discovered a couple of important things: (Remember I'm a computer programmer working for storm water engineers, so these are going to be heavily biased towards computer related complaints)
#1. They don't want the computer simulation to produce results that match reality. Instead they want the simulation to reproduce results generated by older, buggy computer models that are known to be erroneous.
#2. Because of this they have no interest in advancing the practice of civil engineering, but instead, focus on advancing their own career by helping propagate buggy models that have THEIR method in them.
#3. To them, "Calibration" is the process of filling in minor details of the model to make a particular simulation match a real life event, and you only need to calibrate against one event to be able to use model for prediction. This is OBVIOUSLY wrong, and does nothing but hide the bugs of the model (And it's methods.) They don't attempt to calibrate the model against multiple storms with known data. Because of this they are unaware of how far off their predictions are.
#4. In lew of the aforementioned "Calibration" They are more than happy to accept a 300% error margin (as compared to real measured data) on the model when it is first run. As a scientist I see 300% and say "WOAH! Obviously my model's fundamental equations need to be adjusted." they say "300%? No biggy, we'll just calibrate it and it'll be fine."
#5. Since every time they've actually looked at anything they're using they realize they are probably going to kill someone with it, the term "testing" has just been removed from their vocabulary. Ask a civil engineer to test the model and what will happen is that they'll install the program, open the about box, and correct your spelling of "High Lord God" next to their name. And then manage to completely miss the fact that when you tell the program to run the model it doesn't, and instead displays the message "You mother sucks monkey tails!" Then when someone notices (which it can take up to 2 years after RELEASE!) they get all mad at you instead. When you bring up the fact that that kind of bug should have been noticed during the testing phase, and that the only way that it could have been missed is if they hadn't even actually opened the program, they claim that it's unreasonable to expect them to have actually tested it when you asked them too. (I've actually had this happen! Ok... So it didn't make any references to primate sucking, but the model completely failed to run and actually crashed to desktop)
#6. "Consistency" is more important than "Accuracy" to civil engineers. What this means to you, the citizen of "who knows where", USA, is that if the model was horribly bugged before, no amount of inventiveness will ever be applied to fixing the problem. Instead of running the better algorithm (which they will agree is FAR superior,) they will instead demand that all new software be able to produce the invalid result. Meaning that if an older model was flawed in some way that caused them to build the dam too weak, a newer, better model that says that they're going to kill 20,000 people downstream is inherently "wrong" and that the old way (Which they will admit is "also wrong, but still superior to the new method", despite evidence to the contrary) must be written into the software.
#7. The effect of "Simplifying Assumptions". When the models are written, some number of variables have to be left out (A point which I can understand) to make the model actually reasonable to run. So a "Simplifying Assumption" is made, and the variable is removed from the calculations. However, these assumptions inherently create limitations in the model that have to be understood when using it. However, they don't tell anyone these assumptions. This means that if a model designed to simulate water in a channel has the requirement "The channel cannot be longer than the distance water travels in one time step", there's nothing stopping the other, equally unenlightened civil engineers from using the model to simulate a mile and a half long channel, with one minute time steps, and water that's moving about 3 ft/s.
#8. Because of #5 and #7, no one ever checks the numbers to see if the result of the model actually makes sense. Instead they treat it like a perfect black box that produces perfect little gold plated numbers that are irrefutable, no matter what kind of garbage they feed into it. GIGO (Garbage In - Garbage Out) doesn't seem to click with them. So court battles are won and lost based on these happy little garbage numbers. (I've tested this: as long as you give them a number with the right number of digits, you could have selected it out of a hat and they won't notice.)
#9. And yet, however inaccurate, and imprecise the number may be, if it doesn't have EXACTLY the right number of decimal places, it's a wrong number. If the engineer claims that the model is accurate to 10%, so you make it clip the number to 2 significant figures (Note: SIGNIFICANT FIGURES, not decimal places, (they don't seem to understand the difference...)) they will give you all kinds of hell. You can try to defend yourself with "Look, I gave them a whole extra garbage figure to work from," and the response you'll get is "You WILL display it to 3 decimal places!?
#10. If you haven?t already noticed, the fine art of error analysis is kind of lost on civil engineers. I have NEVER seen any civil engineering report (Including the ones that I've had to make programs to write) that gives any kind of reasonable error report. Not one 1000 CFS +- 20 CFS.
#11. Civil engineers are one of the few academic groups that DOES NOT USE METRIC. For some idiotic reason, ALL of their math is done in Imperial units. Even suggesting the possibility of rewriting the equation to use metric units to make them simpler will result in a cry of "BLASTPHEMY!" (You'd be amazed how many of their equations could have EVERY coefficient removed if you used the appropriate metric unit)
#12. They have zip, zero, zilch understanding of statistics. To them, a storm that is on average stronger than 99% of storms is a "1 in a Hundred Year Storm" (No kidding, you know those late afternoon thundershowers? Ya, the ones we see like twice a week during the summer? Ya, those are classified as "1 in Two Year Storms") And when they say it, they actually BELIEVE that a "one in two year storm" only happens once every two years! Turns out that the statistical analysis they're running returns the "excedence probability" in terms of once excedence per X storms. So in actuality, a "2 year storm" is actually a "One in Two STORM storm" (i.e. If this storm isn't at least that strong, the next one likely is.)
#13. Worse yet, they design systems to handle the "One in a Hundred Year Storm". What this means to you, home owner extraordinaire, is that since that actually means that one in a hundred storms is stronger than the design, and (in my area) there are 30 or so storms a year, that your house should get flooded about once every three to four years. Luckily, many of their models are absolutely horrible, and since they typically are off by 300% or so, the things are often so horribly over designed that it's actually funny. Unfortunately the models are off by + OR - 300%, so sometimes the thing doesn't even handle any water at all.
I think that's all of the big ones. Well, the ones that will eventually kill us all, anyway. (The civil lawsuit system being the ONLY reason that more people haven?t died). There's plenty more, but those are the ones that I think have the biggest impact on the health and welfare of the populace at large.
To think that I work for these kind of people... I should quit.
Mood: Angry and Frightened