add lab-p11 and p11

p11/README.md

+# Project 11 (P11): Analyzing Stars and Planets
+
+
+## Corrections and clarifications:
+
+* None yet.
+
+**Find any issues?** Report to us:
+
+- Shutong Wu <shutong.wu@wisc.edu>
+- Abhinav Harish <aharish2@wisc.edu>
+- Aboli Pai <apai7@wisc.edu>
+- Cathy Cao <ccao35@wisc.edu>
+- Muhammad Musa <mmusa2@wisc.edu>
+- Samuel Guo <sguo258@wisc.edu>
+
+
+## Instructions:
+
+This project will focus on **data analysis**, **creating scatter plots**, and **recursion**. In this project, you will continue from where you left off in P10. You will analyze the data structures you created in P10 to answer some interesting questions about our dataset.
+
+To start, download [`p11.ipynb`](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/p11/p11.ipynb), [`public_tests.py`](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/p11/public_tests.py), [`expected_plots.json`](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/p11/expected_plots.json), and [`broken_data.zip`](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/p11/broken_data.zip).
+
+If it takes too long to load the file `expected_plots.json` on GitLab, you can directly download the file from this link: [`expected_plots.json`](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/raw/main/p11/expected_plots.json). You will need to **Right Click**, and click on the **Save as...** button to save the file through this method.
+
+After downloading `broken_data.zip`, make sure to extract it (using [Mac directions](http://osxdaily.com/2017/11/05/how-open-zip-file-mac/) or [Windows directions](https://support.microsoft.com/en-us/help/4028088/windows-zip-and-unzip-files)). After extracting, you should see a folder called `broken_data`. You may delete `broken_data.zip` after extracting the files inside it.
+
+You may also download [`data.zip`](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/p11/data.zip) and extract it. Alternatively, you could also copy/paste the `data` directory that you worked with in P10 into your P11 directory.
+
+**Important**: You **must** make sure that your file structure looks like this:
+
+```
++-- p11.ipynb
++-- public_tests.py
++-- expected_plots.json
++-- data
+|   +-- .DS_Store
+|   +-- .ipynb_checkpoints
+|   +-- mapping_1.json
+|   +-- mapping_2.json
+|   +-- mapping_3.json
+|   +-- mapping_4.json
+|   +-- mapping_5.json
+|   +-- planets_1.csv
+|   +-- planets_2.csv
+|   +-- planets_3.csv
+|   +-- planets_4.csv
+|   +-- planets_5.csv
+|   +-- stars_1.csv
+|   +-- stars_2.csv
+|   +-- stars_3.csv
+|   +-- stars_4.csv
+|   +-- stars_5.csv
++-- broken_data
+|   +-- .DS_Store
+|   +-- hd
+|   |   +-- 10000
+|   |   |   +-- .ipynb_checkpoints
+|   |   |   +-- .DS_Store
+|   |   |   +-- 10000s.json
+|   |   +-- others.json
+|   +-- k2
+|   |   +-- .ipynb_checkpoints
+|   |   +-- .DS_Store
+|   |   +-- k2s.json
+|   +-- kepler
+|   |   +-- 10
+|   |   |   +-- .DS_Store
+|   |   |   +-- 30
+|   |   |   |   +-- .ipynb_checkpoints
+|   |   |   |   +-- .DS_Store
+|   |   |   |   +-- 30s.json
+|   |   |   +-- other
+|   |   |   |   +-- others.json
+|   |   |   +-- 20s.json
+|   |   |   +-- 80s.json
+|   |   +-- 100
+|   |   |   +-- 100
+|   |   |   |   +-- other
+|   |   |   |   |   +-- .ipynb_checkpoints
+|   |   |   |   |   +-- .DS_Store
+|   |   |   |   |   +-- others.json
+|   |   |   |   +-- 100s.json
+|   |   |   +-- 200
+|   |   |   |   +-- 220
+|   |   |   |   |   +-- 220s.json
+|   |   |   |   +-- 290
+|   |   |   |   |   +-- 290s.json
+|   |   |   |   +-- other
+|   |   |   |   |   +-- .ipynb_checkpoints
+|   |   |   |   |   +-- .DS_Store
+|   |   |   |   |   +-- others.json
+|   |   |   +-- others.json
+|   |   +-- other
+|   |   |   +-- .ipynb_checkpoints
+|   |   |   +-- others.json
+|   +-- other
+|   |   +-- .ipynb_checkpoints
+|   |   +-- others.json
+|   +-- toi
+|   |   +-- .ipynb_checkpoints
+|   |   +-- tois.json
+```
+
+Otherwise, your code may pass on **your computer**, but **fail** on the testing computer.
+
+You will work on `p11.ipynb` and hand it in. You should follow the provided directions for each question. Questions have **specific** directions on what **to do** and what **not to do**.
+
+------------------------------
+
+## IMPORTANT Submission instructions:
+- Review the [Grading Rubric](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/p11/rubric.md), to ensure that you don't lose points during code review.
+- Login to [Gradescope](https://www.gradescope.com/) and upload the zip file into the P11 assignment.
+- If you completed the project with a **partner**, make sure to **add their name** by clicking "Add Group Member"
+in Gradescope when uploading the P11 zip file.
+
+   <img src="images/add_group_member.png" width="400">
+
+   **Warning:** You will have to add your partner on Gradescope even if you have filled out this information in your `p11.ipynb` notebook.
+
+- It is **your responsibility** to make sure that your project clears auto-grader tests on the Gradescope test system. Otter test results should be available within forty minutes after your submission (usually within ten minutes). **Ignore** the `-/100.00` that is displayed to the right. You should be able to see both PASS / FAIL results for the 20 test cases, which is accessible via Gradescope Dashboard (as in the image below):
+
+    <img src="images/gradescope.png" width="400">
+
+- You can view your **final score** at the **end of the page**. If you pass all tests, then you will receive **full points** for the project. Otherwise, you can see your final score in the **summary** section of the test results (as in the image below):
+
+   <img src="images/summary.png" width="400">
+
+   If you want more details on why you lost points on a particular test, you can scroll up to find more details about the test.

p11/images/README.md

+# Images
+
+Images from p11 are stored here.

p11/rubric.md

+# Project 10 (P10) grading rubric
+
+## Code reviews
+
+- The Gradescope autograder will make deductions based on the rubric provided below.
+- To ensure that you don't lose any points, you must review the rubric and make sure that you have followed the instructions provided in the project correctly.
+
+## Rubric
+
+### General guidelines:
+
+- Outputs not visible/did not save the notebook file prior to running the cell containing "export". We cannot see your output if you do not save before generating the zip file. (-3)
+- Used concepts/modules such as `csv.DictReader`, `os.walk`, and `pandas` not covered in class yet. Note that built-in functions that you have been introduced to can be used. (-3)
+- Large outputs such as `stars_dict` or `planets_list` are displayed in the notebook. (-3)
+- Import statements are not mentioned in the required cell at the top of the notebook. (-1)
+
+### Question specific guidelines:
+
+- q1 (3)
+	- incorrect logic is used to answer (-1)
+	- `planets_list` data structure is not used to answer (-1)
+
+- q2 (3)
+	- incorrect logic is used to answer (-1)
+	- recomputed variable defined in Question 1 (-1)
+
+- q3 (3)
+	- incorrect logic is used to answer (-1)
+	- recomputed variable defined in Question 1 (-1)
+	- `stars_dict` data structure is not used to answer (-1)
+
+- q4 (5)
+	- incorrect logic is used to answer (-1)
+	- `planets_list` data structure is not used to answer (-1)
+	- plot is incorrect (-1)
+	- plot is not properly labeled (-1)
+
+- q5 (5)
+	- incorrect comparison operator is used (-1)
+	- `planets_list` data structure is not used to answer (-1)
+	- plot is incorrect (-1)
+	- plot is not properly labeled (-1)
+
+- `star_classes` (3)
+	- data structure is defined incorrectly (-1)
+	- incorrect comparison operators are used (-1)
+	- `stars_dict` data structure is not used (-1)
+
+- q6 (3)
+	- did not ignore the `Star` objects with missing `stellar_luminosity` data (-1)
+	- incorrect logic is used to answer (-1)
+	- `star_classes` data structure is not used to answer (-1)
+
+- q7 (5)
+	- incorrect logic is used to answer (-1)
+	- `star_classes` data structure is not used to answer (-1)
+	- plot is incorrect (-1)
+	- plot is not properly labeled (-1)
+
+- q8 (5)
+	- incorrect comparison operator is used (-1)
+	- `star_classes` data structure is not used to answer (-1)
+	- plot is incorrect (-1)
+	- plot is not properly labeled (-1)
+
+- q9 (5)
+	- incorrect logic is used to answer (-1)
+	- `stars_dict` data structure is not used to answer (-1)
+	- plot is incorrect (-1)
+	- plot is not properly labeled (-1)
+
+- `get_all_paths_in` (6)
+	- function does not remove all files and directories that start with `.` (-1)
+	- function does not sort file names explicitly (-1)
+	- function logic is incorrect (-2)
+	- hardcoding the name of directory inside the function (-1)
+	- paths are hardcoded using slashes (-1)
+
+- q10 (3)
+	- `get_all_paths_in` function is not used to answer (-2)
+	- paths are hardcoded using slashes (-1)
+
+- q11 (3)
+	- `get_all_paths_in` function is not used to answer (-2)
+	- paths are hardcoded using slashes (-1)
+
+- q12 (3)
+	- `get_all_paths_in` function is not used to answer (-2)
+	- paths are hardcoded using slashes (-1)
+
+- q13 (3)
+	- `get_all_paths_in` function is not used to answer (-2)
+
+- `all_planets_list` (5)
+	- data structure is defined incorrectly (-1)
+	- `get_planets` function is not used to answer (-1)
+	- `broken_data` data structure is not used to answer (-1)
+	- paths are hardcoded using slashes (-1)
+	- `planets_list` data structure is modified or redefined (-1)
+
+- `get_surface_gravity` (3)
+	- function did not return `None` for missing data (-1)
+	- function logic is incorrect (-2)
+
+- q14 (3)
+	- `get_surface_gravity` function is not used to answer (-1)
+	- `all_planets_list` data structure is not used to answer (-1)
+	- did not exit loop and instead iterated further after finding the answer (-1)
+
+- `get_distances_to_star` (3)
+	- function did not return `None` for missing data (-1)
+	- function logic is incorrect (-2)
+
+- q15 (3)
+	- `get_distances_to_star` function is not used to answer (-1)
+	- `all_planets_list` data structure is not used to answer (-1)
+	- did not exit loop and instead iterated further after finding the answer (-1)
+
+- `get_liquid_water_distances` (3)
+	- function did not return `None` for missing data (-1)
+	- function logic is incorrect (-2)
+
+- q16 (3)
+	- `get_liquid_water_distances` function is not used to answer (-1)
+	- `all_planets_list` data structure is not used to answer (-1)
+	- did not exit loop and instead iterated further after finding the answer (-1)
+
+- q17 (4)
+	- incorrect logic is used to answer (-1)
+	- `get_liquid_water_distances` function is not used to answer (-1)
+	- `all_planets_list` data structure is not used to answer (-1)
+
+- `get_surface_temperatures` (3)
+	- function did not return `None` for missing data (-1)
+	- function logic is incorrect (-2)
+
+- q18 (3)
+	- `get_surface_temperatures` function is not used to answer (-1)
+	- `all_planets_list` data structure is not used to answer (-1)
+	- did not exit loop and instead iterated further after finding the answer (-1)
+
+- q19 (4)
+	- incorrect comparison operators are used (-1)
+	- `get_surface_temperatures` function is not used to answer (-1)
+	- `all_planets_list` data structure is not used to answer (-1)
+
+- q20 (5)
+	- incorrect logic is used to answer (-2)
+	- `get_surface_gravity`, `get_distances_to_star`, `get_liquid_water_distances`, and `get_surface_temperatures` functions are not used to answer (-1)
+	- `all_planets_list` data structure is not used to answer (-1)