mecc-monash / robot-challenge Goto Github PK

To make it more competitive

• Add stopwatch display
• Reset on restart and level change
• Stop when paused / start when unpausing
• Stop when reach goal
• Change colour when reach goal
• Position it nicely on screen

If we can fine-tune this, it would help to make the challenges more applicable to the real world.

Either as a wall or by implementing gravity

Trees, stationary cars, houses or anything else.
To be avoided using the ultrasonic sensors.
Linked to #7

RBC-style

Models can take a while to load. This wait time can cause issues with physics as the simulation begins running as soon as a page load/refresh occurs. Would want this to be minimally intrusive so it doesn't interrupt the flow of changing code and seeing the live-reload.

Would be fun to watch and good for promo.

Either with yellow/white lines for use with colour-sensoring, or walled if ultrasonic sensors have been implemented ala micro mouse competition.

Need a straightforward way to define, set up and transition between different levels/scenes.

This needs to take into account the way that a participant would enter the microcontroller code.

The most simple route would just be to have different html files for each. Need to see whether this works well with the VSCode Live Server extension.

Decide which parts of the challenges we would tackle as a group, which are to be done in the participants' own time.

• How long to spend on each section
• What skills we expect participants to take away

Colour sensing could be achieved using raycasting (intersectObjects) and checking against a list of known mesh types.

Potentially behind a ? button so that it's visible but not too intrusive when refreshing. Could check a flag in localStorage to see if already seen.

Similar to colour sensors, implemented using raycasting.

To make it fair for all the competitors drive speed should be capped