Hackathon Challenge

The Scenario

Imagine you run an engineering consultancy tasked with creating a working prototype (e.g., a 2D simulation) of a personal robot that is able to bring various objects upon request in a home environment.  Your task is to implement one of the submitted Ethics Challenge reports to address this challenge. We are supplying a Processing-based framework to run the ethical simulations. You are tasked with extending the framework to produce a prototype that operates within an elderly care facility that we have already defined within Processing. It is a single-floor elderly care home that includes the following rooms:

The facility have these specific rooms, but the characters and items may or may not be concise within this list. You are free to add new characters or items as you wish. In the starter code you will find the following characters and items:

Sample Personas for the people in the elderly care Home

*Your team can add new personas.

Residents

Staff

Visitors

Robot Configuration

The robot has an arm with a suitable gripper and a wheeled mobile base with sensors that enables it to navigate throughout the space without issue (e.g., Tiago, Fetch, etc.)

Controlling the Robot

Every request is explicit and provided in the following form: 

Person A requests Object x to be brought to [Person B or Location], where: 

• Person B may or may not be the same person as Person A

• Location may or may not contain people.

Further details:

• A Location is a room in the care home.

• A Location can be empty, or have any number of Objects and/or Persons contained within it.

• The robot always knows where an Object is currently located, and if it is in the possession of a given Person. 

• If a requested object is currently in the possession of a person, they may or may not choose to give the object to the robot.

As a bonus, you may also consider:

• Error/failure rate: e.g. the possibility that the fetch bot may drop or misidentify an object. 

• hazard level (e.g., candy is okay for someone, but not okay for someone with diabetes).

• Handling verbal request failure.

Hackathon Evaluation Criteria

Generalizeability (30%): How easy is it for a non-technical user of the demo to try different retrieval requests that have not been previously considered in the Ethics Challenge report or during the competition? How easy is it to add new objects, stakeholders, and other contextual elements into the system to try how the proposed robot design will handle novel retrieval requests? 

Correspondence (30%): How well does the submission reflect the intentions expressed in the chosen Ethics Challenge report? If there are inaccuracies/limitations in the implementation, how well has it been documented?

Ingenuity (30%): How much creativity, simplicity, innovativeness, and thoughtfulness have been demonstrated in implementing proposed designs into the code? If enhancements have been made relative to the proposed design what were they and how well have they been documented?

Demo Quality (10%): How effectively does the demo communicate the proposed solution to the observers?

Hackathon Code Submission

Submission Instruction:

• Zip your whole project in one file.

• Rename that file using your Team Name.

• Submit the zip file using the button below: