Week 7 meeting - Jelc-sys/AV-control-handover-in-critical-situation GitHub Wiki

Meeting week 7

Date: 16/10

Present: everyone

Updates so far:

• Unity

  • Breathing light works on Jelco's laptop, but not on Luca's.

• Scenarios we are going to test for takeover (test reaction time)

  • No breathing + visual
  • No breathing + visual + auditory
  • No breathing + visual + auditory + haptic
  • Breathing + visual
  • Breathing + visual + auditory
  • Breathing + visual + auditory + haptic

Should take max. 1 minute per test.

• Scenarios we are going to test for self driving

  • No feedback from car

  • With verbal feedback from car

  • The passenger could still take over in these two scenarios, that's why the car is asking the passenger to pay attention.

So total demo time = 8 x 1 min + 2 min survey + 5 min presentation = 15 mins.

• Survey is going to be separate from experiment, done in google forms
  • 'How much confidence did you have in the car's abilities during the automated maneuver?' (1 to 5)
  • 'How was this affected by the vehicle's communication with you?' (1 to 5)
  • What would you improve about the way the vehicle handled the situation?
  • What would you improve about the vehicle's communication with you?

Overarching theme presentation

• AV - human communication in a critical takeover scenario

Presentation debrief

• Interaction and communication between man and machine
  • By asking for feedback we will increase trust. By using human voice we increase trust.
  • The main form of communication is the cues in themselves
  • Sees police officer
  • Car interior is evolutionary, as the car is level 3 SAE
    • Still has control interfaces such as steering wheel and gas pedal
• Mobility (taxi idea?)
• Traffic; control and management, effects of autonomous vehicles on traffic, safety, urban mobility (V2X)
  • Sees police officer
• Safety & Security (Data is not being stolen)
  • Apply safety measures to car's behavior
  • Car is driving very slow
• Legislation & regulation
  • Regarding liability during accident
  • Car is going on wrong side of road, how is this justified (Police officer)
• Acceptance
  • Regarding trust
  • Takeover possibilities

APs

• Add reaction time description for each cue combination (so you know which time belongs to which cue) - Luca

• Modify situations as required - Luca

• Add music and voice talking to you - Jelco

  • Continuous feedback during automated maneuver
    • In case I crash you are responsible so pay attention pls
  • For takeover: Implement feedback request, after a fixed timer (What did you think of takeover request?)
  • What did you think? Your response will be used in the future to improve the user experience. (only non-takeover scenario)

• Finish presentation (coming Friday)

  • Start with intro about setup (different scenarios)
  • Lecturers can pick one of two scenarios, do experiment
  • Do extensive debrief with motivations behind choices and our expectations
    • Also mention other experience and what we will do with results
  • Reflection!!!!!!!!!!!!!!!

• Record situations (coming Friday)

• Download AntiMicroX for controller