You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: homeworks/reflect.html
+2-2
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@
25
25
<small>Credit: public domain</small>
26
26
27
27
<h1>Homework 10 - Reflect</h1>
28
-
<divclass="lead">Benjamin Xie & Greg Nelson</div>
28
+
<divclass="lead">Greg Nelson (with material by Benjamin Xie)</div>
29
29
30
30
<p>Individually, write a roughly <strong>500 word statement</strong> covering the following:</p>
31
31
@@ -38,7 +38,7 @@ <h1>Homework 10 - Reflect</h1>
38
38
<li>Do you believe any of your teammates do not deserve full credit for your team's success? Why? What percent of the credit do you think they deserve?</li>
39
39
</ul>
40
40
41
-
<p>You'll submit this report on your <b>personal</b> Google Drive folder..</p>
41
+
<p>You'll submit this report on your <b>personal</b> Google Drive folder. You can write your statement in paragraphs or you can copy-paste the questions and then answer them one by one.</p>
<li>Code: <ahref="https://github.com/Info-370-Winter-2018/class_examples" target="_blank">Bootstrapping and Monte Carlo Simulations</a></li>
<li>Assigned: Project Milestone 5: Project Revision. Due Monday 2/19.</li>
364
+
<li>Assigned: <ahref="https://docs.google.com/document/d/1Yan1Ndfy5kxMhfPkF7fhQMYjyxHBNvL6XllNRW8lGmQ/edit?usp=sharing">Homework 6</a>. Due Friday Feb 23.</li>
<li>Assigned: Project Milestone 7 & 8: <ahref="project/presentation.html">Presentation</a> & <ahref="project/artifact.html">Artifact</a>. Due during finals week or last week of classes.</li>
368
+
<li>Assigned: Project Milestone 7 & 8: <ahref="project/presentation.html">Presentation</a> & <ahref="project/artifact.html">Artifact</a>. Due by end of day on day of finals (March 13).</li>
<li>Code: <ahref="https://github.com/Info-370-Winter-2018/class_examples">see simulating decision for class 8.3 and class 8.2 filled in</a></li>
431
432
</ul>
432
433
</td>
433
434
</tr>
434
435
435
436
<!--<tr><td colspan=3 class="text-uppercase lead">Week 9 — Big Data and Opacity </td></tr>-->
436
-
<tr><tdcolspan=3class="text-uppercase lead">Week 9 — Interpreting Big Data </td></tr>
437
+
<tr><tdcolspan=3class="text-uppercase lead">Week 9 — Debugging and Limitations of Models</td></tr>
437
438
438
439
<tr>
439
440
<!-- QUARTERLY -->
440
441
<td>3/5</td><td>Lecture</td>
441
442
<td>
442
-
443
+
Debugging strategies for R code and Monte Carlo Simulations
443
444
<!--Scaling to "Big Data"-->
444
445
<ul>
445
446
<!--<li>Reading: Excerpt from Fourth Paradigm; Business Articles on Big Data</li>-->
<tdcolspan="4"><ahref="homeworks/reflect.html">Homework 9 (Project and Course Reflection)</a> Due 3/14. <br/> We may hold presentations on the date of finals depending on number of groups.</td>
480
+
<tdcolspan="4"><ahref="homeworks/reflect.html">Homework 9 (Project and Course Reflection)</a> Due 3/14. <br/></td>
Your target audience should know just enough to be more confident they are making a decision that better optimizes what they want.
46
46
They may be confused or misled by excessive detail or make incorrect conclusions with insufficient detail.
47
47
Finding the appropriate balance is dependent on your decision context and target audience.
48
+
Your artifact might be a Shiny app, a web page made from an R markdown document, or another kind of artifact to communicate your results to decision makers.
48
49
</p>
49
50
50
51
<h2>Deliverable 2: Technical Description</h2>
51
52
<p>
52
53
The target audience for the technical description is other data scientists who wish to interpret, critique, and build off of your work.
53
-
It will be a written report in the form of a page on your GitHub wiki and should provide sufficient detail so somebody can understand your analysis and interpret it.
54
+
It will be a written report in the form of an R markdown document; you should link to a compiled html version in your Github repository, from a page on your GitHub wiki and should provide sufficient detail so somebody can understand your analysis and interpret it.
54
55
</p>
55
56
56
57
@@ -87,4 +88,4 @@ <h2>Grading Criteria</h2>
87
88
<!--<p id="ko">Ko, A. J., LaToza, T. D., & Burnett, M. M. (2015). A practical guide to controlled experiments of software engineering tools with human participants. <i>Empirical Software Engineering</i>, <i>20</i>(1), 110-141. <a href="https://doi.org/10.1007/s10664-013-9279-3" target="_blank">https://doi.org/10.1007/s10664-013-9279-3</a></p>-->
Copy file name to clipboardExpand all lines: project/presentation.html
+3-2
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@
25
25
<small>Credit: StockSnap</small>
26
26
27
27
<h1>Milestone 7: Presentation</h1>
28
-
<divclass="lead">Benjamin Xie & Gregory L. Nelson</div>
28
+
<divclass="lead">Gregory L. Nelson (based on material made with Benjamin Xie)</div>
29
29
30
30
<p>
31
31
An important part of any data scientist's job is to share your process and results with your peers and receive feedback.
@@ -74,6 +74,7 @@ <h2>Common Missteps</h2>
74
74
</p>
75
75
<ul>
76
76
<li>Not stating the decision context and question to answer.</li>
77
+
<li>Presenting data or analysis in graphs/charts without interpreting it (describing it like you interpreted in tab 1.2).</li>
77
78
<li>Not connecting your analysis to the decision context and question to answer.</li>
78
79
<li>Running out of time without finishing your presentation.</li>
79
80
<li>Slides are too dense and audience is too fixated on reading slides and stopped listening to presenter. (<ahref="https://en.wikipedia.org/wiki/Split_attention_effect" target="_blank">split attention effect</a>)</li>
<small>While an old video (pre-dates laser pointers!), this is Benji's favorite resource on how to speak. This is an investment in your future.</small></p>
Copy file name to clipboardExpand all lines: project/project-meeting.html
+6-4
Original file line number
Diff line number
Diff line change
@@ -25,18 +25,20 @@
25
25
<small>Credit: Chang Zun Shi</small>
26
26
27
27
<h1>Milestone 6: Project Check-In Meeting</h1>
28
-
<divclass="lead">Benjamin Xie & Gregory L. Nelson</div>
28
+
<divclass="lead">Gregory L. Nelson (based on material made with Benjamin Xie)</div>
29
29
30
30
<p>
31
31
Now that your project proposals are complete and we know what decision you want to inform and how, we'll want to meet with you to clarify questions and ensure you can see your project through.
32
-
We will also provide you with guidelines of our expectations for you and this project.
32
+
We will also provide you with guidelines of our expectations for you and this project, and answer specific questions about how the final deliverables will be graded/evaluated.
33
33
By the end of this meeting, we (the instructors) and you and your team should by on the same page regarding what needs to be done and how.
34
34
</p>
35
35
36
36
<h2>Step 1: Prepare for meeting with instructor</h2>
37
37
<p>
38
38
You'll want to schedule time (we'll send out a Doodle poll or equivalent) with the instructor who will mentor your project.
39
39
Find a time where multiple team members (preferably all) can make.
40
+
41
+
Preferably we will meet on Monday Feb 19 in person, but due to your schedule constraints we may need to meet via Skype during the week.
40
42
</p>
41
43
42
44
<p>
@@ -47,7 +49,7 @@ <h2>Step 1: Prepare for meeting with instructor</h2>
47
49
48
50
<ul>
49
51
<li>question about project or deliverable</li>
50
-
<li>concern about project</li>
52
+
<li>concern about project - for example, how well it will fit into your portfolio</li>
51
53
<li>vision of potential impact</li>
52
54
</ul>
53
55
@@ -86,4 +88,4 @@ <h2>Grading Criteria</h2>
86
88
<!--<p id="ko">Ko, A. J., LaToza, T. D., & Burnett, M. M. (2015). A practical guide to controlled experiments of software engineering tools with human participants. <i>Empirical Software Engineering</i>, <i>20</i>(1), 110-141. <a href="https://doi.org/10.1007/s10664-013-9279-3" target="_blank">https://doi.org/10.1007/s10664-013-9279-3</a></p>-->
<h2>Step 1: Understand how to provide quality feedback</h2>
38
38
39
39
<p>
40
-
The objective of feedback in peer review is to <b>improve the quality of the writing</b>.
40
+
The objective of feedback in peer review is to <b>improve the quality of writing/thinking</b>.
41
41
In this way, you are very much "on the same team" as the authors of the writing you are reviewing.
42
42
The feedback you provide should help other teams further develop their project proposal.
43
43
@@ -53,7 +53,7 @@ <h2>Step 1: Understand how to provide quality feedback</h2>
53
53
</ul>
54
54
55
55
<p>
56
-
Your guiding principle as you provide peer-feedback is this: <b>How can the authors use this feedback to improve their writing</b>?
56
+
Your guiding principle as you provide peer-feedback is this: <b>How can the authors use this feedback to improve their writing/thinking</b>?
57
57
</p>
58
58
59
59
<h2>Step 2: Provide feedback to your peers' project proposals</h2>
@@ -72,7 +72,7 @@ <h2>Step 2: Provide feedback to your peers' project proposals</h2>
72
72
</p>
73
73
74
74
<p>
75
-
The proposals can be found in the wikis of each <ahref="../index.html#teams">project team's GitHub repository</a>.
75
+
The proposals can be found in the wikis of each <ahref="../index.html#teams">project team's GitHub repository</a>. For peer review, look at each team's current data science diagram (should be linked on their “Project Scope and Framing” wiki page) then look at their spreadsheet (also linked on their "Project Scope and Framing” wiki page). <b>Do not go back to earlier spreadsheets or wiki pages - only look at their latest spreadsheet</b>. Read first the rows on the domain and the decision/choices (these are below the 1.1-1.4 and 2.1-2.3 questions). then go to the overall questions on feasibility and impact (1.1-1.4 and 2.1-2.3 questions), then looking at the tabs.
0 commit comments