As table top gaming is a hobby of mine, I’m always on the lookout for a new game to test out. I’ve played a few new table top games lately and I figured I would share my thoughts and do some reviews. Here’s the round up: Cards Against Humanity, Ticket to Ride, Glass Road.
I was passed along this article today, reporting on a sharp increase in pedestrian fatalities in Minnesota. In the StarTribune letter of the day yesterday, written by Michael D. Hoy, he questioned the conclusions of the reporter, showing that the fatalities fall in line with what is expected of normal fluctuations.
About two-thirds of the time, the statistic will lie within one standard deviation of the mean. This is what happened in the last 11 years. Two-thirds of the years had a death count between 33 and 45.
Also, about 95 percent of the time the statistic will lie within two standard deviations of the mean. Again, this is just about what happened. – Michael D. Hoy
It’s easy to look at collision fluctuations and be immediately concerned, but it’s important to remember that fluctuations can be random without any significant cause. That’s why it’s especially important to have good collision data collection methods in place when looking at collision rates and the safety of intersections. Sadly, most municipal resources are too scarce to spend a lot of time and effort on very involved collision reports.
If you’re a municipality or state agency focused on safety, you face a serious challenge everyday: with limited data, dollars, and man-hours available, how do you pick the most dangerous sites in your jurisdiction?
A background in statistics is always helpful, especially for researchers in this field. But for engineers who want to apply models everyday, there are plenty of methods already figured out for you to use. I highly recommend pursuing a graduate level course on highway safety like I did at NC State. Without delving into a statistics degree, you can pick up many effective methodologies to rank sites. Use them to your advantage and get the most efficient use out of precious tax-dollars while saving as many lives as you can!
It’s important to keep these things in mind:
Look at available data carefully. How long has the intersection been open? How much data do you have? Without enough historical data, it will be impossible to see any kind of trends.
Don’t revisit the same sites every year. Did you check the site last year? What were the findings? Unless the site has changed significantly, there’s no reason to check it again. There are tons of dangerous intersections that you haven’t investigated, get to those next.
Volume bias. Sites with the most collisions aren’t necessarily the most dangerous sites. Ranking sites by the number of collisions gives bias to the busiest intersections with the highest volumes. Similarly, sites at the bottom of the list may be dangerous, but have so few vehicles traveled on that they are skipped altogether.
An increase in collisions doesn’t imply a decrease in safety at the site. Especially in areas of high growth, increased collisions may just be because an increase in traffic. Check historical AADTs when you check historical traffic reports, and pick good comparison sites when comparing increases in collisions at one intersection with other intersections in your systems.
And try not to be overwhelmed by media.
News is always more interesting when there is a fright element, but there is no reason to believe that walking is any worse now than before.
I’ve recently become more involved in the North Carolina Section of the Institute of Transportation Engineers (NCSITE), a fantastic group of people from the industry. I attended a NCSITE lecture and meetup last month and played a lot of catch-up with professionals I know but don’t widely see on a day-to-day basis.
“So, you’re going to the technical retreat in August?”
This is the question of the hour. The thought crossed my mind, but I had such a busy month ahead, I was hesitant to make plans. NCSITE needed commitment early to reserve the facilities they planned to use, and holding off on registration for too long was going to make things difficult for the event.
With some shuffling, it was feasible to adjust my work schedule to get the time off I needed. Peer pressure is the strongest around those who’s careers you admire, so what do you say? You say “Yes.”
* * *
Monday, August 27th
I carpooled with Dr. Reza Jafari of RSTS, Inc., and driving to the retreat was an experience by itself. Never having visited the Caraway Conference Center before, we almost passed it. Reza and I share a curious look turning into the driveway. “Camp Caraway” couldn’t possibly be where we were going, but the name matched the driving directions. From the road, it looks more like a boyscout summer camp.
“I didn’t pack a sleeping bag,” says Evan in the back seat, half-smiling, half-serious. Neither did I.
Following the drive through dense woods, we eventually pull up to a building that could’ve been a stand-in for the Overlook Hotel, so I make a mental note to stay clear of Room 237. After a brief check-in, we meet with other attendees in the conference room, have lunch, and sit down for the afternoon sessions.
Scott Lane, Don Kostelec, and Ram Jagannathan all had wonderful presentations covering decision-making, the design of the human environment, land use, and alternative intersections and interchanges.
After dinner, we had the opportunity to listen to terrific NCSITE stories and experiences of some more prominent and senior members of NCSITE. But what made the retreat truly special were the team building and learning exercises Camp Caraway staff engaged us with afterwards. Climbing aboard some tractor-transit, we took a ride to another side of camp with fields lit for the evening’s activities. The irony of the game titles was not lost on me: transit-trains, red-light / green-light, and a game involving subway cars making roundabouts.
There was more fun, learning, and leadership coming from these activities than I knew what to do with. So I pocketed as much as I could for future reflection, and before I knew it, it was time for s’mores at the campfire.1
Tuesday, August 28th
There was an optional morning jog scheduled. I briefly saw the clock out of one sleep-encrusted eyeball. I then proceeded to close said eyeball and dream about jogging instead.
A light breakfast in the cafeteria and on to more sessions. I especially liked Pete Nicholas’s planned signal design activity. This session was my favorite. Complete with a design scenario, blank plans, and an answer sheet to check once completed, our groups were able to look at a proposed signal location and locate signal poles and heads around utilities and property lines. We then had an introduction to isolated timing and an overview of signal cabinet hardware.
This was followed by an introduction to ITS by Kevin Smith and coordinated signal timing by Denys Vielkanowitz. After a group discussion on the retreat as a whole, it was time for lunch and the ride back home.
Lasting Impressions and Memories
One thing that was especially neat about this retreat: it really held my attention. I rarely found myself compulsively checking my iPhone.2 Yes, Camp Caraway is in the middle of nowhere. But that’s kind of what made it special. We couldn’t just drive home for the night, or separate and go to different restaurants. We were stuck with each other for better or worse, and it allowed us to get to know one another much more than I expected.
I shouldn’t have waited so long to register. If registration was open today for a 2013 retreat, NCSITE would have my money already. Special thanks to the NCSITE members who did all the hard work planning everything, you all did a fantastic job. To students, professionals, and others who couldn’t make it this week: there’s no way around it. You truly missed out.
- Yes, it was a little warm to have a campfire. But after forming trains of sweaty engineers and running around in a soccer field, a seat on a log in front of a fire with marshmallows is as good as any.
- Of course, this could also have been affected by the complete lack of cell signal anywhere near Camp Caraway.
I had the fantastic opportunity to visit Blue Marble Game Company when I was in Los Angeles two weeks ago visiting my friend Joe. Joe works as a game designer at Blue Marble, where he uses technologies like Microsoft Surface and Kinect to create rehabilitation games for people with disabilities or therapists who work with people with disabilities. Today, Microsoft posted a video of their visit and it’s exciting to see Joe in the video along with all his coworkers I met when I was there. Way to go and keep it up!
A friend sent me a link to a recent WRAL article posted yesterday about a fatal collision in Cary on Sunday, February 12th1. Tragically, both passengers in a left-turning vehicle died when the driver crossed the path of another vehicle. This is terrible and my condolences go out to those affected by the incident. I also feel for safety engineers everywhere who feel the emptiness of failure at each reported fatality2, especially the highway safety professionals who work in this jurisdiction. However, as an engineer and scientist it is of utmost importance to step back and remember a few things about working within the confines of the real world: with limited tax funds, systems are imperfect and not every collision is preventable.
Keeping these things in mind, how do traffic engineers decide if an intersection requires a traffic signal? We use a system of “warrants”, or reasons that warrant the installation of a control device. The Manual on Uniform Traffic Control Devices (MUTCD) lists nine signal warrants for varying reasons in Chapter 4C. A pdf of this manual can be found here. These reasons range from volume to school-zone related conditions and yes, even crash experience.4 Most generally, traffic signals are never installed without first qualifying for one or more warrants.
Why? In many cases a signal can make an intersection worse than it started! Traffic signals are often viewed in the public eye as a cure-all, when in fact they can have adverse affects on safety and efficiency: increased delay, increased traffic control disobedience, increased use of other routes such as neighborhoods (just to skip the light!), and others. The increased stops can also increase the number of rear-end collisions at the site as well.4 This has led to the installation of many lights that were never needed, at sites that may now be less safe, at the cost of a six figure installation. Thats right, your average 4-way simple traffic signal costs between $150,000-200,000. Plus continued maintenance from now until forever.
One of the biggest reasons that the public is so ill informed about the affects of traffic signals is the media, and we can see it in this article.2 It’s not necessarily their fault that the public demands stories that move the heart, either in tenderness, controversy, or horror. But people get so caught up in political partisan biases, that many forget how easy it is to be biased to the heart instead of the mind, allowing an element of “controversy” to develop conspiracy, scheme, even frustration in the reader. Lets take a moment to analyze some of the diction used in this article:
“hasn’t met the criteria for a traffic light, despite pleas from drivers and neighbors that the intersection is too dangerous”
I’d be pulling my hair out if there was any left to pull. On the logic side, uninformed readers could assume two very incorrect conclusions: drivers and neighbors always know a dangerous intersection when they see one3, and that pleas from drivers and neighbors warrant a traffic signal. But theres so much on the emotional side as well. Using the word “plea” to stab the hearts of our readers, the author has clearly set the tone of the entire article to:
“People have begged on hand and knee, offering to sacrifice their first born for just one, ONE traffic signal. The site would be safer, and this wouldn’t have happened”.
No wonder people think traffic signals are a cure-all! This conjecture could be patently false. For all we know without adequate evidence, adding a traffic signal could make this site WORSE. But not now. As uninformed citizens we now know that the evil city of Cary is denying us the promise of safety and security that only a traffic signal can bring.
“she attempted to turn left from West Chatham Street onto Cary Parkway and crossed into the path of a Dodge Avenger.”
This one earns the reporter kudos. Notice how quickly and easily the blame of the incident could have been shifted: 1) “she unwittingly pulled in front of traffic”, or 2) “the Dodge Avenger smashed into the side of her vehicle”. Unfortunately for the reader, we don’t know the exact cause of the collision. We may never know for sure. It could’ve easily been texting or another form of distracted driving. The author calls this collision “correctible”, though as a reader we are left unsure as to whether or not it is she or her interviewee that thinks it’s correctible and why. But by calling this collision “correctible”, the public will be wondering why correctible collisions are happening at all. And they should! But they are missing an important piece of the puzzle: some intersections are more correctible than others and warrant more immediate attention and funding, of which there is a finite amount of both.
“In addition to traffic volume and other criteria, to warrant a light an intersection would need to have had five crashes that would have likely been corrected by a traffic light in a single year.”
But I have to draw the line here, this is a complete falsehood and is misreported. Intersections do not require crashes for a traffic signal. In fact, new roads are constantly being built in conjuction with signals before they are even opened. But the remark is so instigating and confusing, it left one commenter with a terrible impression of traffic safety methods. If anything should make an engineer feel like a failure, it is the terrible miscommunication with the public that can lead to this:
Let me see if I have this right….The criteria for installing a traffic light requires multiple occurrences of either property damage, bodily harm, or loss of life. The wisdom of our city fathers leaves much to be desired. carrydoggymom, February 13, 2012 7:55 p.m
As much as a I try to avoid reading the comments section on a news website, it’s important from a public administration point-of-view to see how this fraction of the populace thinks. Some comments are enlightening, some are sad. This time, I was mostly surprised to see intelligent debate in the comments section. Mostly.
“I bet if it was the mayor’s family, there would be a light there tomorrow. What a load of bull!” bjandroxie88, February 13, 2012 7:42 p.m
Here is the advocation that, not only should tax dollars be spent willy-nilly by those in power when they find misfortune, but that politicians should make engineering decisions. There is a problem when the politically inclined try to mingle in the affairs of those who put safety first, a perfect reason why engineers should use MUTCD warrants instead of bending to political pressure from above.
“…If the vehicle was close enough to hit them, it was close enough to see and avoid.” pedsrndad, February 14, 2012 11:56 a.m
While my first instinct is inclined to agree, sight distance plays an important factor in intersection design, and it may need reinvestigation at this particular intersection. Though I imagine it was addressed and not seen as a big problem during the original design, factors such as reclassifying the speed-limit or increased volume year-to-year could play a part in changing the environment here.
I’ve driven the intersection myself, and especially during rush hour it can be difficult to turn left. The median supplies a little refuge, but not much. I glanced at the traffic volume maps, but without knowing more about peak hour data, it’s difficult to say exactly what warrants the intersection can qualify for. I’m surprised it doesn’t hit the peak-hour warrant, or even the school-crossing warrant with it’s proximity to Laurel Park Elementary. With the limited data I have on hand, I might recommend the following traffic studies to take another look at the signal warrants: sight distance study, spot speed study, and/or a volume study.5
If a light is installed in the near future, I hope it will be because it is warranted and that conditions have changed since the last inspection of the intersection. Not because of the ravings of uninformed watchers of the 6 o’clock news. We should all strive to be more cognizant of the impact media can have on the heart of the public, and how important good communication can be when working for the public sector. These efforts will make it easier to limit the affect of a tragic story in the news from opening our wallets too wide when there aren’t enough collisions to merit a new, expensive, and possibly ineffective traffic control device.
Wrap Up (Read: Important Conclusions)
By now you should have gathered the following:
- Traffic signals are not a cure-all; sometimes, when not really needed, they cause problems.
- We use Signal Warrants to come to justified conclusions, recommended by the MUTCD, on whether or not to add a traffic signal at an unsignalized intersection.
- MUTCD has 9 different signal warrants for varying reasons of safety.
- Intersections do not require collisions to warrant a traffic signal.
- “Pleas from drivers and neighbors” is not an MUTCD signal warrant.
- “The mayor found misfortune” is not an MUTCD signal warrant.
- Crashes and fatalities do not necessarily merit an MUTCD signal warrant.
References and Notes:
- Cary intersection doesn’t meet criteria for traffic light, WRAL, Monday, February 13th, 2012
- Mental Note: Prevented collisions never make the news. How could they?
- Mental Note: Drivers and neighbors are an invaluable resource when discussing what they think of an intersection. However, everyone’s seen a collision somewhere. This does not always, a “dangerous” location, make.
- Manual on Uniform Traffic Control Devices 2009, published by the Federal Highway Administration.
- As found in the Highway Safety Engineering Studies Procedural Guide, published by USDOT and FHWA 1991, commonly referred to as “The Parker Manual”.
Twin Cities, MN
I had a few spare weeks recently, and decided to go on a cross-country trek to visit some friends. I also took the opportunity to take in some civil engineering landmarks along the way. First stop was Minneapolis/St. Paul, Minnesota. Had a great time visiting my college buddy Garrett, now a grad student at U of M. We passed by the Civil Engineering building on campus, a building residing almost completely underground. For it’s unique design it was awarded with the Outstanding Civil Engineering Achievement Award by ASCE in 1983.
I visited the new 1-35W Mississippi River Bridge, the replacement bridge on the site of the disastrous 2007 bridge collapse. Improper design as well as large loads from construction equipment and extra layers of pavement caused the original bridge to collapse. Nearby, I walked across the Stone Arch Bridge of Minneapolis, overlooking the only waterfall on the Mississippi river. Built in 1883 and named a Historic Civil Engineering Landmark, the bridge served as a railway bridge but now serves as a pedestrian and bicycle path across the Mississippi. In the area are many parks that serve the historic district and showcase the history of the water-powered mills that put the Twin Cities on the map.
It’s always exciting to see public transportation improvement projects, and it was neat to see the construction of new light rail stations by the local Metro Transit in St. Paul. We also visited the Town Hall Brewery and attended the Beer Dabbler Winter Carnival 2012.
Next stop was Colorado. Not too many civil engineering landmarks on this leg of the trip. Instead, I had the wonderful opportunity to have some family in the area expose me to some really neat experiences. I went ice-fishing, fed buffalo, visited Odell Brewing, and sat in on a volunteer-firefighting training seminar. For those most interested in the sciences, here’s a nerdy exposition: you can calculate the thickness of clear ice h (inches) that can withstand failure from a load of p (tons) with the following formula: h = 4√p
There’s all sorts of other factors you can throw in for safety, and if you plan on driving out on the ice, you should probably give these a good read:
Some more neat information:
Los Angeles, CA
My last stop was LA, visiting another NC State friend and former roommate, Joe. Much warmer than the previous stops, I enjoyed the beautiful sunny weather of Pasadena. I visited Venice Beach, the infamous Hollywood sign, Griffith Park Observatory, El Pueblo, Hollywood Boulevard, La Brea Tarpits, IO West Improv Club, In-N-Out Burger, and Point Fermin Lighthouse.
Of course, my visit to the locale wouldn’t do my “engineering” trek justice if I didn’t review local transportation resources. I rode both the Metro Bus and the Metro Rail, visited Union Station, and found it all to be exceptional for my use as a tourist. Joe commutes to and from work daily via Metro Rail and bicycle (which he can bring on the train) and finds them more than adequate. I was impressed with the timeliness, cleanliness, and usefulness. I only wish we had this kind of rail in Raleigh.
I also noticed the use of ramp meters both here and in Twin Cities. These are not a congestion tool we currently use in North Carolina, so I sent a quick email to Dr. Hummer, professor at NC State, with some questions on use cases and statistics. He responded rather quickly and gave me great information on the topic. They can keep the mainline traffic moving better than Level of Service “F”, preventing a 100-300 vehicles per hour per lane drop in capacity. They break up “platoons” of cars, and can decrease travel time up to 10%. In North Carolina, it’s been easier to add conventional capacity in the past, but NCDOT may need to look at ramp meters more closely for use on I-77 in Charlotte and areas around RTP.
All in all, the trip was very rewarding, and I can’t wait for the next opportunity to do a similar trip in the future. Special thanks to family and friends for taking time to spend with me and making my trip possible!
Those who know me know I like to create, and cooking is a fantastic hobby I’ve picked up. There’s always something new to learn. It’s art. It’s expression. And best of all, you can eat it.
But like all things, if you do it, do it right. Cook like you mean it. Go big or go home. And recently I’ve learned that the culinary arts, or at least the kitchen responsibilities involved therein, have a lot in common with the engineering industry. It was this wonderful article on a chef’s blog that really punched it home to me: sous chefs are engineers, but not all engineers are sous chefs.
Being a sous chef has little to do with the title and all to do with what you make of it…
Cook your ass off. Organize your station better than I would. Stop whining. Turn problems into solutions. Take challenges and ride them one handed. The bull threw you? Get up and get back on. Ask for help when you need it. Rally support that’s available to you. Work cleaner every day. Create systems and implement them. Learn stations you’ve never known.
Get out of your comfort zone.
Manager or not, if an engineering office was a kitchen, everyone should strive to be a sous chef.
Think about it as you set your goals for the new year. Be the sous chef. Leave egos at home, get your hands dirty, and get cooking.
Happy Holidays everyone!
Block quote comes from the following article. Make sure you give it a read: Shuna Fish Lydon, Eggbeater Blog