- Conceptualise, prototype, and test how in-car sensors (at least camera(s) + accelerometers) might be used to improve the safety and experience of road users. The work should be based on a user-centered methodology and result in a proof-of-concept physical prototype, building on existing libraries and solutions wherever possible.
- In-car sensing is already widespread (e.g. dash-cams, GPS, etc.), but there may be as yet untapped use cases that are enabled by in-car sensing (e.g. monitoring lane-keeping through vision systems, potentially integrated into a dash-cam or mobile phone, and alerting drivers to dangerous driving; or accelerometers detecting potholes, swerving, and other hazards). The resulting information may be helpful to drivers (alerting them of risk factors), as well as to Traffic Operations Centres (alerting them of potentially hazardous road conditions etc).
- Consider the use of mobile devices as sensors, as well as separate stand-alone units (e.g. issued and required by rental companies).
- Aim to identify use-cases for your in-car sensors that have a significant potential impact (e.g. on reducing accidents or reducing travel times) - an assessment of the scale of this impact should form part of the project. Solutions should be thoroughly "usability design" tested by people outside the project team (by allowing them to interact and/or provide feedback on mockups, simulations and prototypes), and technically feasible using current technology, but need not be implemented as far as a minimum viable product (i.e. a proof of concept is fine).
- The project team (the students and, optionally, supervising staff) will be expected to attend at least three meetings at the NZTA Innovation Zone: a project briefing, a progress update, and a project debrief.
- The project briefing will outline preferred development principles and technologies to be used for the project - e.g. Cloud first, GitHub code repository, build automation, DevOps, etc.
- Android and iOS apps (where applicable) should use the same base C # code. We use Xamarin as our current mobile app development framework for code reusability – a loan MacBook can be made available for use at the NZTA Innovation Zone if required.
- Hardware might include mobile phones, Arduino, the Raspberry Pi3 platform, which supports tensorflow,(e.g. https://www.youtube.com/watch?v=BBwEF6WBUQs) or the Nvidia Jetson TK1 / TX1. (e.g. https://www.youtube.com/watch?v=MCmgfHjMIKg)
- The Student, Supervisor and/or the University must enter into a Privacy Protection Agreement with the Sponsor, prior to any Personal Information (as defined in section 2(1) of the Privacy Act 1993) being provided to the Student, Supervisor and/or the University for the purposes of the Research Project.
- Computer Systems Engineering
- Electrical and Electronic Engineering
Allocated (Not available for preferences)
Lab allocations have not been finalised