Corning Community College
CSCS1320 C/C++ Programming
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).
Measuring participation fulfills a vital role of gauging individual involvement and interactivity in on-going class activities, not just their ability to perform assigned projects.
Being exposed to and interacting with the subject matter helps to improve understanding, and eventually fluency, yet the trends these days seem to involve more and more people only putting forth effort for a class DURING said class (often at the expense of the actual in-class activity going on).
Some may think it is time well spent, but when I find myself constantly repeating myself days, weeks, even months later, it is clear that something needs to be done in order to improve individual participation in the course.
The following are a list of available activities, along with current weekly claim caps, and point values that you can perform for participation credit in a given week.
Watch this space, as new activities may be added, or old ones obsoleted (either conditionally or entirely), along with tweaks to claim caps and point values.
attribute | description | cap (how many per week) | points per | week available |
---|---|---|---|---|
discord# | textual and relevant interaction on class discord | 6 | 2pts | 1+ |
early | started early, submitted for-points deliverable 3 or more days before due date | 1 | 2pts | 1+ |
repo | make at least 4 productive (and relevant to that week's deliverables) commits to your Lab46 semester repository | 1 | 2pts | 1+ |
edit | made requisite amount of edits of at least threshold size on project documentation page | 1 | 4pts | 1+, varies |
present# | physically present (and logged into lab46 shell) during any in-person scheduled class meetings | 2 | 1pts | 7+ |
You will see that, in a normal week a TOTAL of 16-22 points are currently possible (depending on particular attribute criteria)
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 is based on:
wcp activity analysis is automated: the wcp tool will show you a daily report of what you've currently accumulated (updated once per day, sometime around midnight).
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?
If you submitted early, what project and how early? And how did your advance work on it (well before the deadline) help you (not rushing, less anxiety, luxury of time to think, etc.)
At least, it may offer a writing prompt to help you get started on your weekly journal entries.
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 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 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.
Following will be a list of participation point tallies you will need to accumulate in a given week to get full credit:
NUM | report name | opens | due by | total points needed |
---|---|---|---|---|
1 | wcp1 | 20230817 | 20230823 | 2 |
2 | wcp2 | 20230824 | 20230830 | 2 |
3 | wcp3 | 20230831 | 20230906 | 4 |
4 | wcp4 | 20230907 | 20230913 | 4 |
5 | wcp5 | 20230914 | 20230920 | 4 |
6 | wcp6 | 20230921 | 20230927 | 4 |
7 | wcp7 | 20230928 | 20231004 | 8 |
8 | wcp8 | 20231005 | 20231018 | 8 |
9 | wcp9 | 20231019 | 20231025 | 8 |
A | wcpA | 20231026 | 20231101 | 8 |
B | wcpB | 20231102 | 20231108 | 8 |
C | wcpC | 20231109 | 20231115 | 8 |
D | wcpD | 20231116 | 20231129 | 8 |
E | wcpE | 20231130 | 20231206 | 8 |
There are no make-ups. If you miss performing an activity, you can either make up the credit by other participation activities, or even make up for lost credit with bonus points in other weeks.
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.
The sanctioned participation activities, when performed, leave a digital trail, which I capture.
The spirit of this activity is that you are making genuine and honest contributions to participation each and every week.
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.
It takes 2 arguments:
And you can do so as follows (replace 'DESIG' with your lowercase class designation, for the appropriate week):
lab46:~$ wcp DESIG wcpNUM
This should bring up the current report, displayed to STDOUT in your lab46 terminal.