Differences

This shows you the differences between two versions of the page.

--- haas:spring2021:common:projects:wcp [2021/02/04 12:24] – external edit 127.0.0.1
+++ haas:spring2021:common:projects:wcp [2021/02/18 14:21] (current) – [Weekly Point Requirements] wedge
@@ Line 6: / Line 6: @@
 =====Overview=====
-Each week, you have the ability to earn class participation credit by performing any of the following activities (for some amount of points) per week, in order to attain a stated point threshold (likely varying by week or general progression of the semester).
+Each week, you have the ability to earn class participation credit by performing any of the available activities (for some amount of points) per week within any stated constraints, in order to attain a given point threshold (varying from week to week or as a general progression throughout the semester).
 =====Background=====
@@ Line 21: / Line 21: @@
 ^  attribute  ^  description  ^  cap (how many per week)  ^  points  |
-|  discord#  |  textual and relevant interaction on class discord (one per 32 minutes span of time)  |  6  |  2pts  |
+|  discord#  |  textual and relevant interaction on class discord  |  6  |  2pts  |
 |  early  |  started early, submitted for-points deliverable **3 or more** days before due date  |  1  |  2pts  |
 |  repo  |  make **at least** 4 productive (and relevant to that week's deliverables) commits to your Lab46 semester repository  |  1  |  2pts  |
@@ Line 29: / Line 29: @@
 Each week I will require some subset of the above-stated activities to be done for participation, giving you choices on how you'd like to earn this credit. Depending on the combination, I may consider participation activities done in excess of the weekly cap as some form of bonus (applied to the participation component).
-**NOTE:** The eligibility for claiming a **discord** attribute requires the following considerations:
+**NOTE:** The eligibility for claiming a **discord** attribute differs depending on the week and various factors:
-  * on-topic message/question posted to class-specific (NOT generalchat) discord
+  * e-mails and direct messages in discord do not count towards this. AT ALL. Part of your responsibility in the class is to participate in the learning environment with others.
-  * the claiming of an attribute covers a 32 minute span of time. I don't want you posting 4 separate messages one after the other and claiming all four attributes. Think quality over time.
+  * In week 1:
-====Exceptions====
+    * since we are just getting started, generalchat messages will be included in the list of acceptable participation sources (but will only be included for consideration in the first week).
-Certain class configurations may see overrides to some of the requirements stated here, if it enables better symbiosis with the class. Such alterations will be stated on class-specific information sources.
+  * In week 2:
+    * on-topic message/question posted to class-related (NOT generalchat) discords
+    * the claiming of an attribute covers a 32 minute span of time. I don't want you posting 6 separate messages one after the other and claiming all the discord attributes. Think quality over time.
+    * wcp activities are now automated. wcp tool will show you a daily report of what you've attained.
+    * cap on bonus points: one can only earn AT MOST HALF the stated weekly points in bonus form (or 2, if the halfway value is less than 2).
+  * In week 3 and beyond:
+    * wcp activities are automated: The **wcp** tool will show you a daily report of what you've currently accumulated (updated once per day).
+    * like before: only class-related discords are eligible
+    * the time threshold changes to 192 minutes, but will also increment by 192 with each passing earned attribute
+    * only posts (or accumulations of posts) of at least 32 words will be considered eligible. Accumulated triggers will only come to fruition once the necessary time lapse has transpired.
+    * cap on bonus points: one can only earn AT MOST HALF the stated weekly points in bonus form (or 2, if the halfway value is less than 2).
-For example: for **wcp1**, I will also grant ONE **discord** attribute for any introductory interactions as you arrive on the discord. This will NOT be the case for future weeks (where claimed activity must have taken place in the specific class discord channel).
 ====Journal====
 As part of your validation for claiming these attributes, leave a written record on your journal of the nature of your activities; if you asked a question, what was it, what was the gist of the answer, and what new insights did you gain from the experience?
@@ Line 44: / Line 53: @@
 At least, it may offer a writing prompt to help you get started on your weekly journal entries.
-=====wcp# projects=====
+=====wcp# reports=====
-Each week there will be a wcp# project for you to submit your participation activity claim, which is done using a dedicated **wcp** tool.
+Each week there will be a wcp# report started for you to view your accumulated participation credit, which can be viewed using the **wcp** tool (on lab46).
-Failure to submit your claim by the deadline will result in lost credit: remembering and time management are important skills as well!
+Failure to adequately participate under the terms of the available attributes by the deadline will result in lost credit: remembering and time management are important skills as well!
-The project will open up at the start of each week (Thursday), and close by the end of that week (Wednesday). There are **NO** LATE submissions.
+The report will start on Thursday, and close by the end of that week Wednesday. You have between the open and close of a reporting period to perform your recognized participation activities.
 =====Weekly Point Requirements=====
 Following will be a list of participation point tallies you will need to accumulate in a given week to get full credit:
-^  NUM  ^  project name  ^  opens  ^  due by  ^  total points needed  |
+^  NUM  ^  report name  ^  opens  ^  due by  ^  total points needed  |
 |  1  |  wcp1  |  20210128  |  20210203  |  1  |
 |  2  |  wcp2  |  20210204  |  20210210  |  2  |
@@ Line 71: / Line 80: @@
 =====Participation Activity Log=====
-I would highly recommend keeping an activity log of your participation activities for each week (might be a good recap to put as part of your weekly journal entry), as I may ask you to provide additional information to back up your claim.
+I would highly recommend keeping an activity log of your participation activities for each week (might be a good recap to put as part of your weekly journal entry), as it may help reinforce your management of time with respect to accomplishing projects throughout the week.
-If you are unable to substantiate your claim, any claimed credit may be voided for that particular week.
+=====Viewing your current week participation report=====
+The sanctioned participation activities, when performed, leave a digital trail, which I capture.
-=====Submission: Making a participation claim=====
+The spirit of this activity is that you are making genuine and honest contributions to participation each and every week.
-Some of these participation activities, when performed, leave a digital trail, which I endeavor to capture. Others are more analog in nature (ie asking a question in class).
+====Using wcp#====
+If you are within the report window for a particular week (say, week1, so the **wcp1** participation report is active), you can view your report using the **wcp** tool.
-By making a claim, I am assuming you are making a just and honest claim to having performed said activity.
-====Submit wcp#====
-If you are within the submit window for a particular week (say, week1, so the **wcp1** participation project), you can make your claim using the **wcp** tool.
 It takes 2 arguments:
   - the class designation you are making the claim for (c4eng, cprog, unix, data, discrete, comporg, sysprog, hpc0, etc.)
-  - the wcpNUM project name (where NUM is **1** for wcp1/week1, **2** for wcp2/week2, etc.)
+  - the wcpNUM report name (where NUM is **1** for wcp1/week1, **2** for wcp2/week2, etc.)
 And you can do so as follows (replace 'DESIG' with your lowercase class designation, for the appropriate week):
@@ Line 93: / Line 99: @@
 </cli>
-This should bring up an interactive dialog with a list of checkboxes.
+This should bring up the current report, displayed to STDOUT in your lab46 terminal.
-Use the up/down arrow keys, and the **space bar** to toggle selections (it is a checkbox, so you can select 0 or more).
-When done, you can simply hit **ENTER** to submit.
-Your terminal prompt should be returned to you, and you should be greeted with the message "**SUBMISSION COMPLETE**", and hopefully no error messages.
-And that's it! Simply rinse and repeat for each regular week of the semester (I will NOT be collecting participation during break weeks).

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools