Skip to content

Instantly share code, notes, and snippets.

@sanjivyash
Last active December 26, 2020 22:48
Show Gist options
  • Save sanjivyash/97a8d0866619f0f2ee071fd4418ec1b3 to your computer and use it in GitHub Desktop.
Save sanjivyash/97a8d0866619f0f2ee071fd4418ec1b3 to your computer and use it in GitHub Desktop.
EE338 Digital Signal Processing : Voluntary Participation Policy 2020-21

DSP Participation Policy

Please keep in mind that this policy has been designed assuming honest involvement from students.

Challenges by Students

  • Students chosen for lecture presentation are requested to prepare two challenge questions (per lecture) available for all teams apart from the team of the problem creator.
  • Problems shall be reviewed and approved by the professor before publishing or presenting.
  • Every valid submission within a certain timeframe is worth 7 points, and as explained below aims at providing a fair chance to everyone to score and also improve their understanding of the subject in the process.

Lecture Presentation

  • One week may have two or three lectures. In case of three lectures, three students from the same group will be alloted one lecture each, otherwise one person may have to solve tutorial problems or wait for their turn the next week.
  • One student will present one lecture within 5-10 minutes accompanied with a summary presentation to aid them.
  • Grading will be individual, but the same team will be given lectures together so that they can collaborate when creating presentations. It will help in the identification of silly errors.
  • We expect one or two challenge problems from each student, and the professor can review and decide what challenges are good enough to be published. Such challenges are worth more grades!!

Lecture Notes

  • To allow more teams to participate in a week, we have come up with the concept of lecture notes.
  • The notes from the professor are only meant for aiding his explanation in the video and are in no way exhaustive.
  • So one team (one person per lecture) can be allotted the role of creating innovative notes with interesting information and examples.
  • Grading will again be individual, although teams may collaborate to review each other's notes for input.
  • Please note that this arrangement has been made especially for students with low internet connectivity as it is not possible for them to provide live presentations. As such, preference would be given to such students.

Tutorial Problems

  • One person gets to solve one problem for each tutorial problem.
  • The solution explanation should not be too detailed and should be typically finished in 5 minutes.
  • Just a brief overview with a good presentation is enough.

Challenge Solutions

  • Challenges are of two types - those posed by students and the challenges from video lectures. For both these types, we think that the first 5 teams to provide a correct solution should be credited as in EE 225.
  • The valid submissions will start after a certain period of time after the lecture to dissuade the students from attempting them while attending the lecture, and the exact time slots shall be decided by the professor.
  • Obviously, a team cannot attempt a challenge created by one of their members.
  • One team is graded for atmost two successful submissions in two weeks to give everyone a fair chance of attempting these problems.
  • Problems unsolved after a week are free for all to solve.
  • Grading individually may result in skewed result as the solution can be shared among team members and just one team may take up all spots.
  • For challenges from the videos, the first team to answer the challenge can name the member who actually came up with the majority of the solution. This person can present his solution the next week for extra credits, allotted only to that person and not the team.
  • Due to lack of time, such presentation will not be feasible for the numerous challenge problems created by the students.
  • Suitable actions shall be taken in case of suspected plagiarism in accordance with the decision of the professor.

Special Teams

Teams which have members from both B. Tech and Dual will have to choose one batch to stick to. If there are three members in the team, two of them would belong to the same batch and the third one has to also join the batch. In case of two students, one from B. Tech and other from Dual, we leave it upto the team to decide which batch to join. Based on the final allotments, a Google Sheet shall be prepared to remove all confusion.

Final Thoughts

It is hard to give a chance to everyone and still provide some individual incentive for the course. Thus, the challenges posted by a team are integral to this policy. We hope that the teams maintain honesty and not share their challenge solutions with other teams. The participation of any person is completely voluntary as the policy name suggests, and the grading is also individual, although we try our best to allot team members their roles in the same week so that some collaboration is possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment