hey guys
as i said..i had a look at all weve posted and
this is what we did in general:
research on:
statistics
how many accidents?
which types of vehicles are involved?
which pedestrians are mostly involved?
reasons
- why do accidents happen?
- which fault is it mostly?
- focused on car interior
- pedestrians attention to other stuff like ipod
- why are ped. impatient?
-> psychology of waiting
-> how to visualize time
car technology
- types of car lights in general
- different types of front lights
- car to car
- car to environment
- car interior
-> too much stuff that steals attention
-> ER button
- existing car to car systems
-> "fleetnet" by daimler chrysler
-> "now" network on wheels
-> "willwarn" wireless local danger warning eu project testing networks on the street
-> cellphone positioning data
- enlightener: a thin clear plastic sheet with a concentric surface that can be fittet to car windows
and enhances the visibility of blind spots
- special mirror constructions instead of hightech
environment
- LED road markers
- induction loops
- different road signs: good or bad ones
- signaling at city intersections. signs, traffic lights, markings on the ground bla
technology developments we researched
- zebra stripes with higher visibility reflectors
- Monolithic Microwave integrated circuits (MMICs)
-> light sensors origionally developed for millitary use
- High intensity discharge lighting (HID)
-> type of headlight
- Hellaa - lanechange warning system
- Mazda 626 SensorCar
- Volvo's EyeCar
-> measures where drivers eyes are and adjusts headlights for optimal visibility
- Donnelly VideoMirror Camera Vision System
- philips lumalive
- intelligent mirror
- rfid
- airwave city car
- oled
- inspiration research on light in general
what we've produced
- car to car mindmap
- sketches in general
- busy intersection sketches
- creation of a concrete scenario
-> scenario sketches/ factors/ problems
- future intersection sketches: adress all senses, sandras pole etc
- animations
- your intersection experiment in ny:)
Thursday, November 27, 2008
Monday, November 24, 2008
This is what we gotta do
Logistics of built product-Contact manufacturers: (thomas register .com)
-LED-lit monitors (TVs)
-LED maufactures (sizes/spacing/type of wiring/room required)
-timing, chips, etc. -> integrations
-set syntax/rules of intersection timing
Group interaction:
-sensors: what is the point? finalize type, how/when it works
-Lauren + Jenny: pedestrian finder, walkway lighting, etc
-Oz + Hiro: HUD interaction
Presentation:
-order
-finding holes
-explanation/ back-up w/ research
-LED-lit monitors (TVs)
-LED maufactures (sizes/spacing/type of wiring/room required)
-timing, chips, etc. -> integrations
-set syntax/rules of intersection timing
Group interaction:
-sensors: what is the point? finalize type, how/when it works
-Lauren + Jenny: pedestrian finder, walkway lighting, etc
-Oz + Hiro: HUD interaction
Presentation:
-order
-finding holes
-explanation/ back-up w/ research
Saturday, November 22, 2008
Yesterday we took pictures of the different proportions of the inner and outer circles of the radial sign at an intersection to observe which ones were or ere not working.
Today we will take pictures of the intersection walk / don't walk cycle so that we can place our ideas for the animated signs in it.
List of things to accomplish by sunday:
1. take picctures of the intersection
2. reward with hot beverage
3. make all animations of circles:
- 3 partial right of way options (complete with L.E.D. placement)
- 1 animation of the finalized walk/don't walk cycle. complete with L.E.D. placement
4. place animations in intersection photos
Today we will take pictures of the intersection walk / don't walk cycle so that we can place our ideas for the animated signs in it.
List of things to accomplish by sunday:
1. take picctures of the intersection
2. reward with hot beverage
3. make all animations of circles:
- 3 partial right of way options (complete with L.E.D. placement)
- 1 animation of the finalized walk/don't walk cycle. complete with L.E.D. placement
4. place animations in intersection photos
Thursday, November 20, 2008
things we've concluded.
DECISIONS/QUESTIONS for the day:
ticker experience: a-ha moment: ticker rhythm must stay the same at every intersection to keep patience (if each tick mark takes 3 seconds to appear, the pedestrian will become impatient and/or the signal will appear to be broken. we need to create the illusion of a swiftly moving intersection)
XSLOW GIF
size test: to determine optimum viewing size for circular light case, we have created a matrix based on existing measurements of current crosswalk lighted signals. we will test printouts of thirty six variations to determine the most advantageous ratio of walk man to ticker to environment. from here, we will determine the number of leds based on the longest wait/go time we can find.
XMATRIX
led size: determined by perimeter of circular light case divided by number of seconds of longest intersection wait/go time gives us the size of each tick. from here, we will figure out the size of led that will fit in each tick mark. we plan on accounting for extra time in addition to the longest wait/go just to be safe.
reasons for rhythm: tick must happen every second for constant stimulus and constant rhythm universal for all intersections. the second also references the clock and is an innate timing measurement. because tick marks blink every second, tick size varies according to intersection wait/go time frames.
black background: creates maximum contrast between colors and against cityscape. another reason for this is that a color background would be black at night anyway.
CURRENT SIGNALS:
technology behind current boxes: why so thick? what's inside?
color of current boxes: what's significant about school bus yellow? should aesthetics match new street furniture (bus shelters, new stands) from CEMUSA?
back of new boxes: ads? time? weather? blank?
tasks for tonight:
-brainstorm partial right of way
-visit columbus circle
-check lights for manufacturer's info
XCOLUMBUS CIRCLE PHOTO
tasks for next few days:
-time traffic lights
(keep individual logs)
ticker experience: a-ha moment: ticker rhythm must stay the same at every intersection to keep patience (if each tick mark takes 3 seconds to appear, the pedestrian will become impatient and/or the signal will appear to be broken. we need to create the illusion of a swiftly moving intersection)
XSLOW GIF
size test: to determine optimum viewing size for circular light case, we have created a matrix based on existing measurements of current crosswalk lighted signals. we will test printouts of thirty six variations to determine the most advantageous ratio of walk man to ticker to environment. from here, we will determine the number of leds based on the longest wait/go time we can find.
XMATRIX
led size: determined by perimeter of circular light case divided by number of seconds of longest intersection wait/go time gives us the size of each tick. from here, we will figure out the size of led that will fit in each tick mark. we plan on accounting for extra time in addition to the longest wait/go just to be safe.
reasons for rhythm: tick must happen every second for constant stimulus and constant rhythm universal for all intersections. the second also references the clock and is an innate timing measurement. because tick marks blink every second, tick size varies according to intersection wait/go time frames.
black background: creates maximum contrast between colors and against cityscape. another reason for this is that a color background would be black at night anyway.
CURRENT SIGNALS:
technology behind current boxes: why so thick? what's inside?
color of current boxes: what's significant about school bus yellow? should aesthetics match new street furniture (bus shelters, new stands) from CEMUSA?
back of new boxes: ads? time? weather? blank?
tasks for tonight:
-brainstorm partial right of way
-visit columbus circle
-check lights for manufacturer's info
XCOLUMBUS CIRCLE PHOTO
tasks for next few days:
-time traffic lights
(keep individual logs)
Friday, November 14, 2008
Subscribe to:
Posts (Atom)




















