add lab-p6 and p6

p6/README.md

+# Project 6 (P6): Investigating Airbnb Data
+
+## Corrections and clarifications:
+
+* None yet.
+
+**Find any issues?** Report to us:
+
+- Yuheng Wu <wu459@wisc.edu>
+- Abhinav Harish <aharish2@wisc.edu>
+- Tunan Wang <tunan.wang@wisc.edu>
+- Shutong Wu <shutong.wu@wisc.edu>
+- Yunfu Deng <yunfu.deng@wisc.edu>
+
+## Note on Academic Misconduct:
+You are **allowed** to work with a partner on your projects. While it is not required that you work with a partner, it is **recommended** that you find a project partner as soon as possible as the projects will get progressively harder. Be careful **not** to work with more than one partner. If you worked with a partner on Lab-P6, you are **not** allowed to finish your project with a different partner. You may either continue to work with the same partner, or work on P6 alone. Now may be a good time to review our [course policies](https://cs220.cs.wisc.edu/f23/syllabus.html).
+
+## Instructions:
+
+This project will focus on **accessing data in csv file** and **string methods**. To start, download [`p6.ipynb`](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projectdesign/-/raw/main/p6/p6.ipynb), [`public_tests.py`](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projectdesign/-/raw/main/p6/public_tests.py) and [`power_generators.csv`](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projectdesign/-/raw/main/p6/power_generators.csv).
+
+**Note:** Please go through [Lab-P6](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/lab-p6) before you start the project. The lab contains some very important information that will be necessary for you to finish the project.
+
+You will work on `p6.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**.
+
+After you've downloaded the file to your `p6` directory, open a terminal window and use `cd` to navigate to that directory. To make sure you're in the correct directory in the terminal, type `pwd`. To make sure you've downloaded the notebook file, type `ls` to ensure that `p6.ipynb`, `public_tests.py`, and `power_generators.csv` are listed. Then run the command `jupyter notebook` to start Jupyter, and get started on the project!
+
+**IMPORTANT**: You should **NOT** terminate/close the session where you run the above command. If you need to use any other Terminal/PowerShell commands, open a new window instead. Keep constantly saving your notebook file, by either clicking the "Save and Checkpoint" button (floppy disk) or using the appropriate keyboard shortcut.
+
+------------------------------
+
+## IMPORTANT Submission instructions:
+- Review the [Grading Rubric](https://git.doit.wisc.edu/cdis/cs/courses/cs220/cs220-f23-projects/-/tree/main/p6/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 P6 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 P6 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 `p6.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.

p6/images/README.md

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

p6/rubric.md

+# Project 6 (P6) 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:
+
+- 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. This deduction will become stricter for future projects. (-3)
+- Used concepts/modules such as dictionaries, or pandas not covered in class yet - built-in functions that you have been introduced to can be used. (-3)
+- Import statements are not all placed at the top of the notebook. (-1)
+- Hardcoded answers. (all points allotted for that question)
+
+### Question specific guidelines:
+
+- `cell` (5)
+	- variables `csv_data`, `csv_header`, and `csv_rows` are not defined as expected (-1)
+	- function does not return `None` when data is missing (-1)
+	- function does not typecast to `int` or `float` when expected (-1)
+	- function logic is incorrect (-1)
+	- `process_csv` function is not used to read `power_generators.csv` (-1)
+
+- q1 (4)
+	- not all rows are looped through (-1)
+	- incorrect logic is used (-1)
+	- `cell` function is not used to read data (-1)
+
+- q2 (3)
+	- not all rows are looped through (-1)
+	- incorrect logic is used (-1)
+	- `cell` function is not used to read data (-1)
+
+- q3 (3)
+	- not all rows are looped through (-1)
+	- incorrect logic is used (-1)
+	- `cell` function is not used to read data (-1)
+
+- `find_entities_with_phrase` (4)
+	- not all rows are looped through (-1)
+	- case insensitive matches are not considered (-1)
+	- duplicates are not removed (-1)
+	- `cell` function is not used to read data (-1)
+
+- q4 (2)
+  - `find_entities_with_phrase` function is not used to answer (-2)
+
+- q5 (4)
+	- incorrect logic is used to answer (-2)
+	- `cell` function is not used to read data (-1)
+
+- q6 (4)
+	- incorrect logic is used to answer (-2)
+	- `cell` function is not used to read data (-1)
+
+- q7 (5)
+	- not all rows are looped through (-1)
+	- the output is not sorted correctly (-1)
+	- incorrect logic is used (-1)
+	- `cell` function is not used to read data (-1)
+
+- q8 (5)
+	- not all rows are looped through (-1)
+	- the output is not sorted correctly (-1)
+	- incorrect comparison operators are used (-1)
+	- incorrect logic is used (-1)
+	- `cell` function is not used to read data (-1)
+
+- `num_generators_by` (3)
+	- not all rows are looped through (-1)
+	- function logic is incorrect (-1)
+	- `cell` function is not used to read data (-1)
+
+- q9 (2)
+	- `num_generators_by` function is not used to answer (-2)
+
+- q10 (3)
+	- incorrect logic is used to answer (-1)
+	- `num_generators_by` function is not used to answer (-1)
+	- `find_entities_with_phrase` function is not used to answer (-1)
+
+- q11 (5)
+  - all entities are looped through instead of just the unique entities (-2)
+	- incorrect logic is used to answer (-1)
+	- `num_generators_by` function is not used to answer (-1)
+
+- `find_indices_within` (4)
+	- not all rows are looped through (-1)
+	- incorrect comparison operators are used (-1)
+	- function logic is incorrect (-1)
+	- `cell` function is not used to read data (-1)
+
+- q12 (3)
+	- length of the list is found by looping through it (-1)
+	- `find_indices_within` function is not used to answer (-2)
+
+- q13 (3)
+	- duplicates are not removed from the list (-1)
+	- incorrect logic is used to answer (-1)
+	- `find_indices_within` function is not used to answer (-1)
+
+- q14 (5)
+	- incorrect logic is used to answer (-2)
+	- `find_indices_within` function is not used to answer (-1)
+	- `cell` function is not used to read data (-1)
+
+- `median` (3)
+	- function modifies the original input list (-1)
+	- function logic is incorrect when inputs are of odd length (-1)
+	- function logic is incorrect when inputs are of even length (-1)
+
+- q15 (4)
+	- incorrect logic is used to answer (-1)
+	- `find_indices_within` function is not used to answer (-1)
+	- `median` function is not used to answer (-1)
+	- `cell` function is not used to read data (-1)
+
+- `total_summer_capacity_of` (4)
+	- not all rows are looped through (-1)
+	- missing data is not ignored (-1)
+	- function logic is incorrect (-1)
+	- `cell` function is not used to read data (-1)
+
+- q16 (2)
+	- `total_summer_capacity_of` function is not used to answer (-2)
+
+- q17 (5)
+  - all power plants are looped through instead of just the unique power plants (-1)
+	- incorrect logic is used to answer (-1)
+	- `total_summer_capacity_of` function is not used to answer (-1)
+	- `median` function is not used to answer (-1)
+
+- `avg_winter_capacity_of` (4)
+	- not all rows are looped through (-1)
+	- missing data is not ignored (-1)
+	- function logic is incorrect (-1)
+	- `cell` function is not used to read data (-1)
+
+- q18 (2)
+  - `avg_winter_capacity_of` function is not used to answer (-2)
+
+- q19 (5)
+	- all technologies are looped through instead of just the unique technologies (-1)
+  - list of unique technologies is recomputed (-1)
+	- incorrect logic is used to answer (-1)
+	- `avg_winter_capacity_of` function is not used to answer (-1)
+
+- q20 (4)
+  - all technologies are looped through instead of just the unique technologies (-1)
+	- incorrect logic is used to answer (-1)
+	- `avg_winter_capacity_of` function is not used to answer (-1)