Description
Project Specifications
Your task is to complete Parts 1–4 in the “Runaway Robot” project on Udacity. While you may use the Udacity IDE to test your code against some test cases, you must submit your code to Canvas for grading using the Assignments link in the canvas navigation bar.
We will run your code against 10 test cases per part to grade your work. Each test case is worth 2.5 points, so there is a maximum of 100 points. We will run your code once per test case; passing a test case is worth 2.5 point, and failing a test case is worth 0 points.
The parameters for the test cases will satisfy the following constraints:
- -20.0 <= target_starting_position_x <= 20.0
- -20.0 <=target_starting_position_y <= 20.0
- -math.pi <= target_starting_heading < pi
- 10 <= abs( target_period ) <= 50
- 0 <= target_speed <= 5.0
- -20.0 <= hunter_starting_position_x <= 20.0
- – 20.0 <= hunter_starting_position_y <= 20.0
- -math.pi <= hunter_starting_heading < pi
target_period will be an integer. It represents the number of time steps required for the robot to make one complete cycle.
A positive value for target_period means that the robot will move counterclockwise; a negative value means the robot will move clockwise.
The standard deviation of the Gaussian applied to the target’s measurements will be 0 in Part 1, 0.05 times the target’s speed in Parts 2–4.
The hunter bot (if present) will have a max speed twice that of the target in Part 3 and 0.99 that of the target in Part 4.
The requirements for passing a test case are:
- Part 1: Identifies the position of the target within a distance of 02*target_speed using at most 10 calls to estimate_next_pos
- Part 2: Identifies the position of the target within a distance of 0.02*target_speed using at most 1000 calls to estimate_next_pos
- Parts 3&4: Puts the hunter within a distance of 02*target_speed of the target using at most 1000 calls to next_move
- All Parts: The code takes a maximum of 5 seconds per test case; taking longer than 5 seconds will result in the failure of the test case
- All Parts: No exceptions are raised; any exception raised during the execution of a test case will result in the failure of the test case
As you will only upload the studentMain files in your submission, any changes you make to robot.py or matrix.py will not be seen. If you want to modify those classes for your submission, include the classes in the appropriate studentMainN.py files (and don’t import robot or matrix). You’re also welcome to use any other libraries that are accepted in the Udacity interface (e.g. numpy ).
The submission must consist of Python 2.7 files labeled studentMain1.py, studentMain2.py , studentMain3.py, and studentMain4.py. Do not zip, tar, or archive the files together. Files that do not follow this format will receive a penalty of -20 pts.
Your studentMainN.py files should execute NO code when they are imported. (i.e. comment out any testing code you may have, we only want to test the estimate_next_pos or next_move function.) They should also NOT display a GUI or Visualization when we import them or call your function under test. If we have to manually edit your code to comment out your own testing harness or visualization you will receive a -20 point penalty.
Additionally, you may use any packages that are accepted in the Udacity interface, but any code that does not run in the Udacity interface will receive no credit. This includes using Python 3, packages not available in Python 2.7, or packages not recognized by the Udacity IDE. You can always check your packages work by uploaded them to the Udacity IDE and seeing whether an error is raised.
Testing Your Code
On Canvas, we have posted a testing suite similar to the one we’ll be using for grading the Runaway Robot project. To use the testing suite, put testing_suite_full.py into the same directory as the studentMainN.py files (and robot.py and matrix.py if you are using the default versions), then run
python testing_suite_full.py
In the testing suite, we’ve provided 10 premade test cases. We will use 10 other, secret test cases to score your project. You should ensure that your code consistently succeeds on each of the given test cases as well as on a wide range of other test cases of your own design, as we will only run your code once per graded test case.
