task cards for PA2 and PA3

docs/group-activities/week-3/PA3-task-card.html

@@ -7,7 +7,7 @@
 <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
 
 
-<title>Introduction to Statistical Computing in R - Practice Activity 3 Task Card</title>
+<title>Introduction to Statistical Computing in R - PA 3 Task Card – Finding Margaret’s College</title>
 <style>
 code{white-space: pre-wrap;}
 span.smallcaps{font-variant: small-caps;}
@@ -80,7 +80,7 @@
       <button type="button" class="quarto-btn-toggle btn" data-bs-toggle="collapse" data-bs-target=".quarto-sidebar-collapse-item" aria-controls="quarto-sidebar" aria-expanded="false" aria-label="Toggle sidebar navigation" onclick="if (window.quartoToggleHeadroom) { window.quartoToggleHeadroom(); }">
         <i class="bi bi-layout-text-sidebar-reverse"></i>
       </button>
-        <nav class="quarto-page-breadcrumbs" aria-label="breadcrumb"><ol class="breadcrumb"><li class="breadcrumb-item">Practice Activity 3 Task Card</li></ol></nav>
+        <nav class="quarto-page-breadcrumbs" aria-label="breadcrumb"><ol class="breadcrumb"><li class="breadcrumb-item">PA 3 Task Card – Finding Margaret’s College</li></ol></nav>
         <a class="flex-grow-1" role="button" data-bs-toggle="collapse" data-bs-target=".quarto-sidebar-collapse-item" aria-controls="quarto-sidebar" aria-expanded="false" aria-label="Toggle sidebar navigation" onclick="if (window.quartoToggleHeadroom) { window.quartoToggleHeadroom(); }">      
         </a>
       <button type="button" class="btn quarto-search-button" aria-label="" onclick="window.quartoOpenSearch();">
@@ -246,14 +246,23 @@
 <div id="quarto-sidebar-glass" class="quarto-sidebar-collapse-item" data-bs-toggle="collapse" data-bs-target=".quarto-sidebar-collapse-item"></div>
 <!-- margin-sidebar -->
     <div id="quarto-margin-sidebar" class="sidebar margin-sidebar">
-
+        <nav id="TOC" role="doc-toc" class="toc-active">
+    <h2 id="toc-title">On this page</h2>
+
+  <ul>
+  <li><a href="#dealing-with-errors" id="toc-dealing-with-errors" class="nav-link active" data-scroll-target="#dealing-with-errors">Dealing with Errors</a></li>
+  <li><a href="#code-formatting" id="toc-code-formatting" class="nav-link" data-scroll-target="#code-formatting">Code Formatting</a></li>
+  <li><a href="#group-roles" id="toc-group-roles" class="nav-link" data-scroll-target="#group-roles">Group Roles</a></li>
+  <li><a href="#group-norms" id="toc-group-norms" class="nav-link" data-scroll-target="#group-norms">Group Norms</a></li>
+  </ul>
+<div class="toc-actions"><ul><li><a href="https://github.com/atheobold/stat-331-website/issues/new" class="toc-action"><i class="bi bi-github"></i>Report an issue</a></li></ul></div></nav>
     </div>
 <!-- main -->
 <main class="content" id="quarto-document-content">
 
 <header id="title-block-header" class="quarto-title-block default">
 <div class="quarto-title">
-<h1 class="title">Practice Activity 3 Task Card</h1>
+<h1 class="title">PA 3 Task Card – Finding Margaret’s College</h1>
 </div>
 
 
@@ -270,8 +279,55 @@ <h1 class="title">Practice Activity 3 Task Card</h1>
 </header>
 
 
+<p>Today you will use the <code>dplyr</code> package to clean some data. We will then use that cleaned data to figure out what college Margaret has been accepted to.</p>
+<p><strong><em>This task is complex. It requires many different types of abilities. Everyone will be good at some of these abilities but nobody will be good at all of them. In order to produce the best product possible, you will need to use the skills of each member of your group.</em></strong></p>
+<section id="dealing-with-errors" class="level2">
+<h2 class="anchored" data-anchor-id="dealing-with-errors">Dealing with Errors</h2>
+<p>As you work through this PA, you will encounter some code that does not work as you want it to. Don’t despair! <strong>Errors</strong> (when R is unable to run your code) and <strong>bugs</strong> (when the code doesn’t do what you hoped) are a natural part of coding. Even the best of the best deal with these problems regularly - learning to track down the issue is a skill that you can learn and practice.</p>
+<p><strong>Errors can be sneaky - check results <em>often</em>!</strong></p>
+<p>If a chunk of code runs smoothly without giving you an error or warning this <strong>does not</strong> necessarily mean it accomplished the desired task.</p>
+<p>It is a good habit to check the results of your code <strong>every time</strong> you finish a task. In general, I would recommend completing the following tasks <strong>every time</strong> you write a code chunk.</p>
+<ul>
+<li><p>Include a comment at the beginning of the code chunk that briefly states the purpose of the chunk. Comments in the code chunks come after <code>#</code> signs. These comments will remind later readers—which might be your future self!—what the desired output of the code chunk is.</p></li>
+<li><p>If you created a new object, take a look at it! You can inspect the object by either clicking its name in your <em>Environment</em> tab or by typing its name into the console. Make sure it looks about how you expect. <strong>Do not</strong> type code to inspect the object in your Quarto file, as that <strong>is not</strong> code that needs to be saved!</p></li>
+<li><p>If you created or updated a data frame, make sure your edits did what you hoped. Use the <em>Environment</em> or the <code>head()</code> function to investigate your changes.</p></li>
+</ul>
+</section>
+<section id="code-formatting" class="level2">
+<h2 class="anchored" data-anchor-id="code-formatting">Code Formatting</h2>
+<p>Don’t forget, writing “tidy” and “well documented” code are two of the learning targets for this course. As such, I would strongly encourage you to use every opportunity to practice these skills.</p>
+<p>As you are writing code for this assignment, make sure your code follows the <a href="https://style.tidyverse.org/pipes.html">tidyverse style guide for dplyr code</a>. Specifically, your code should:</p>
+<ul>
+<li>use whitespace liberally
+<ul>
+<li>before &amp; after every <code>=</code> sign</li>
+<li>after every <code>,</code></li>
+<li>before every <code>|&gt;</code></li>
+</ul></li>
+<li>use new lines liberally
+<ul>
+<li>after every <code>|&gt;</code></li>
+<li>after <code>,</code> when needed (if code is more than 80 characters in length)</li>
+</ul></li>
+</ul>
+</section>
+<section id="group-roles" class="level2">
+<h2 class="anchored" data-anchor-id="group-roles">Group Roles</h2>
+<p>When you are the <strong>Listener</strong>, you will type into the Quarto document in RStudio. However, you <strong>do not</strong> type your own ideas. Instead, you type what the Problem Solver tells you to type. You are permitted to ask the Problem Solver clarifying questions, and, if both of you have a question, you are permitted to ask the professor.</p>
+<p>When you are the <strong>Problem Solver</strong>, you are responsible for reading the instructions / prompts and directing the Listener what to type in the Quarto document. You are also responsible for instructing the Listener what comments to insert in the Quarto document to help the group understand the code later.</p>
+</section>
+<section id="group-norms" class="level2">
+<h2 class="anchored" data-anchor-id="group-norms">Group Norms</h2>
+<p>Remember, your group is expected to adhere to the following norms:</p>
+<ol type="1">
+<li>Think and work together. Do not divide the work.</li>
+<li>You are smarter together.</li>
+<li>No cross-talk with other groups.</li>
+</ol>
+<!-- Add more norms from collaborative list -->
 
 
+</section>
 
 </main> <!-- /main -->
 <script id="quarto-html-after-body" type="application/javascript">
@@ -808,7 +864,7 @@ <h1 class="title">Practice Activity 3 Task Card</h1>
 </div>   
     <div class="nav-footer-center">
       &nbsp;
-    <div class="toc-actions"><ul><li><a href="https://github.com/atheobold/stat-331-website/issues/new" class="toc-action"><i class="bi bi-github"></i>Report an issue</a></li></ul></div></div>
+    <div class="toc-actions d-sm-block d-md-none"><ul><li><a href="https://github.com/atheobold/stat-331-website/issues/new" class="toc-action"><i class="bi bi-github"></i>Report an issue</a></li></ul></div></div>
     <div class="nav-footer-right">
 <p>This page is built with ❤️ and <a href="https://quarto.org/">Quarto</a>.</p>
 </div>

docs/search.json

@@ -2947,5 +2947,68 @@
     "title": "PA 3: Identify the Mystery College 🏫",
     "section": "Dealing with Errors",
     "text": "Dealing with Errors\nAs you work through this PA, you will encounter some code that does not work as you want it to. Don’t despair! Errors (when R is unable to run your code) and bugs (when the code doesn’t do what you hoped) are a natural part of coding. Even the best of the best deal with these problems regularly - learning to track down the issue is a skill that you can learn and practice.\nErrors can be sneaky - check results often!\nIf a chunk of code runs smoothly without giving you an error or warning this does not necessarily mean it accomplished the desired task.\nIt is a good habit to check the results of your code every time you finish a task. In general, I would recommend completing the following tasks every time you write a code chunk.\n\nInclude a comment at the beginning of the code chunk that briefly states the purpose of the chunk. Comments in the code chunks come after # signs. These comments will remind later readers—which might be your future self!—what the desired output of the code chunk is.\nIf you created a new object, take a look at it! You can inspect the object by either clicking its name in your Environment tab or by typing its name into the console. Make sure it looks about how you expect. Do not type code to inspect the object in your Quarto file, as that is not code that needs to be saved!\nIf you created or updated a data frame, make sure your edits did what you hoped. Use the Environment or the head() function to investigate your changes.\n\nGoogle is your friend!\nThe whole of the internet is at your disposal! Use it early, use it often.\nSome tricks:\n\nCopy-paste the exact error message into Google. Chances are, somebody else had a similar problem and got a similar message.\nInclude package names in your search terms. For example, “bar plot in ggplot” is a better search than “bar plot in R”."
+  },
+  {
+    "objectID": "group-activities/week-2/PA2-task-card.html",
+    "href": "group-activities/week-2/PA2-task-card.html",
+    "title": "PA2 Task Card - Using Data Visualization to Find the Penguins",
+    "section": "",
+    "text": "Today you will be exploring different types of visualizations to uncover which species of penguins reside on different islands.\nThis task is complex. It requires many different types of abilities. Everyone will be good at some of these abilities but nobody will be good at all of them. In order to produce the best product possible, you will need to use the skills of each member of your group."
+  },
+  {
+    "objectID": "group-activities/week-2/PA2-task-card.html#group-roles",
+    "href": "group-activities/week-2/PA2-task-card.html#group-roles",
+    "title": "PA2 Task Card - Using Data Visualization to Find the Penguins",
+    "section": "Group Roles",
+    "text": "Group Roles\nWhen you are the Listener, you will type into the Quarto document in RStudio. However, you do not type your own ideas. Instead, you type what the Problem Solver tells you to type. You are permitted to ask the Problem Solver clarifying questions, and, if both of you have a question, you are permitted to ask the professor.\nWhen you are the Problem Solver, you are responsible for reading the instructions / prompts and directing the Listener what to type in the Quarto document. You are also responsible for instructing the Listener what comments to insert in the Quarto document to help the group understand the code later."
+  },
+  {
+    "objectID": "group-activities/week-2/PA2-task-card.html#writing-code",
+    "href": "group-activities/week-2/PA2-task-card.html#writing-code",
+    "title": "PA2 Task Card - Using Data Visualization to Find the Penguins",
+    "section": "Writing Code",
+    "text": "Writing Code\nWriting “tidy” and “well documented” code are two of the learning targets for this course. As such, I would strongly encourage you to use every opportunity to practice these skills.\nTidy Code As you are writing code for this assignment, make sure your code follows the tidyverse style guide for ggplot code. Specifically, your code should:\n\nuse whitespace liberally\n\nbefore & after every = sign\nafter every ,\nbefore every +\n\nuse new lines liberally\n\nafter every +\nafter , when needed (if code is more than 80 characters in length)\n\n\nWell Documented Code – Include a comment at the beginning of the code chunk that briefly states the purpose of the chunk (comments come after # signs). In addition, if your code involves many steps or steps you needed to look up / get help on, I would encourage you to write a code comment on what is happening in these lines.\n\nggplot(data = penguins, \n       mapping = aes(x = species, \n                     fill = species\n       ) +\n# use fill instead of color to get the bars filled entirely with color (instead of just on the outside)\n  \n  geom_bar() +\n  labs(x = \"\", \n       y = \"\", \n       title = \"Number of Penguins Captured in the Palmer Archipelago\") +\n# remove axis titles and put that information in the title where it is easier to read\n  \n  theme(legend.position = \"none\")\n# to remove the legend position, since the fill information is already included on the x-axis"
+  },
+  {
+    "objectID": "group-activities/week-3/PA3-task-card.html",
+    "href": "group-activities/week-3/PA3-task-card.html",
+    "title": "PA 3 Task Card – Finding Margaret’s College",
+    "section": "",
+    "text": "Today you will use the dplyr package to clean some data. We will then use that cleaned data to figure out what college Margaret has been accepted to.\nThis task is complex. It requires many different types of abilities. Everyone will be good at some of these abilities but nobody will be good at all of them. In order to produce the best product possible, you will need to use the skills of each member of your group."
+  },
+  {
+    "objectID": "group-activities/week-3/PA3-task-card.html#dealing-with-errors",
+    "href": "group-activities/week-3/PA3-task-card.html#dealing-with-errors",
+    "title": "PA 3 Task Card – Finding Margaret’s College",
+    "section": "Dealing with Errors",
+    "text": "Dealing with Errors\nAs you work through this PA, you will encounter some code that does not work as you want it to. Don’t despair! Errors (when R is unable to run your code) and bugs (when the code doesn’t do what you hoped) are a natural part of coding. Even the best of the best deal with these problems regularly - learning to track down the issue is a skill that you can learn and practice.\nErrors can be sneaky - check results often!\nIf a chunk of code runs smoothly without giving you an error or warning this does not necessarily mean it accomplished the desired task.\nIt is a good habit to check the results of your code every time you finish a task. In general, I would recommend completing the following tasks every time you write a code chunk.\n\nInclude a comment at the beginning of the code chunk that briefly states the purpose of the chunk. Comments in the code chunks come after # signs. These comments will remind later readers—which might be your future self!—what the desired output of the code chunk is.\nIf you created a new object, take a look at it! You can inspect the object by either clicking its name in your Environment tab or by typing its name into the console. Make sure it looks about how you expect. Do not type code to inspect the object in your Quarto file, as that is not code that needs to be saved!\nIf you created or updated a data frame, make sure your edits did what you hoped. Use the Environment or the head() function to investigate your changes."
+  },
+  {
+    "objectID": "group-activities/week-3/PA3-task-card.html#group-roles",
+    "href": "group-activities/week-3/PA3-task-card.html#group-roles",
+    "title": "PA 3 Task Card – Finding Margaret’s College",
+    "section": "Group Roles",
+    "text": "Group Roles\nWhen you are the Listener, you will type into the Quarto document in RStudio. However, you do not type your own ideas. Instead, you type what the Problem Solver tells you to type. You are permitted to ask the Problem Solver clarifying questions, and, if both of you have a question, you are permitted to ask the professor.\nWhen you are the Problem Solver, you are responsible for reading the instructions / prompts and directing the Listener what to type in the Quarto document. You are also responsible for instructing the Listener what comments to insert in the Quarto document to help the group understand the code later."
+  },
+  {
+    "objectID": "group-activities/week-3/PA3-task-card.html#code-formatting",
+    "href": "group-activities/week-3/PA3-task-card.html#code-formatting",
+    "title": "PA 3 Task Card – Finding Margaret’s College",
+    "section": "Code Formatting",
+    "text": "Code Formatting\nDon’t forget, writing “tidy” and “well documented” code are two of the learning targets for this course. As such, I would strongly encourage you to use every opportunity to practice these skills.\nAs you are writing code for this assignment, make sure your code follows the tidyverse style guide for dplyr code. Specifically, your code should:\n\nuse whitespace liberally\n\nbefore & after every = sign\nafter every ,\nbefore every |>\n\nuse new lines liberally\n\nafter every |>\nafter , when needed (if code is more than 80 characters in length)"
+  },
+  {
+    "objectID": "group-activities/week-3/PA3-task-card.html#group-norms",
+    "href": "group-activities/week-3/PA3-task-card.html#group-norms",
+    "title": "PA 3 Task Card – Finding Margaret’s College",
+    "section": "Group Norms",
+    "text": "Group Norms\nRemember, your group is expected to adhere to the following norms:\n\nThink and work together. Do not divide the work.\nYou are smarter together.\nNo cross-talk with other groups."
+  },
+  {
+    "objectID": "group-activities/week-2/PA2-task-card.html#group-norms",
+    "href": "group-activities/week-2/PA2-task-card.html#group-norms",
+    "title": "PA2 Task Card - Using Data Visualization to Find the Penguins",
+    "section": "Group Norms",
+    "text": "Group Norms\nRemember, your group is expected to adhere to the following norms:\n\nThink and work together. Do not divide the work.\nYou are smarter together.\nNo cross-talk with other groups."
   }
 ]

docs/sitemap.xml

@@ -50,7 +50,7 @@
   </url>
   <url>
     <loc>https://atheobold.github.io/stat-331-website/group-activities/week-2/PA2-task-card.html</loc>
-    <lastmod>2024-09-04T16:58:17.732Z</lastmod>
+    <lastmod>2024-09-06T21:12:19.507Z</lastmod>
   </url>
   <url>
     <loc>https://atheobold.github.io/stat-331-website/group-activities/week-2/PA2-ggplot-solution.html</loc>
@@ -110,7 +110,7 @@
   </url>
   <url>
     <loc>https://atheobold.github.io/stat-331-website/group-activities/week-3/PA3-task-card.html</loc>
-    <lastmod>2024-09-04T16:58:41.177Z</lastmod>
+    <lastmod>2024-09-06T21:12:02.484Z</lastmod>
   </url>
   <url>
     <loc>https://atheobold.github.io/stat-331-website/labs/instructions/challenge-2-instructions.html</loc>