| Programs | 50% |
| Homeworks | 15% |
| Quizzes | 30% |
| Att/Part | 5% |
THERE WILL BE NO INCOMPLETES GIVEN IN THE CLASS.
Office Hour:A note about office hours:office hours end if/when there is no one else waiting to talk to me unless you let me know inadvance that you need to come later.Send me an email to schedule something else if you can't make it duringmy regular office hours.
General Policies:All course work are intended as individual effort(unless explicitly mentioned otherwise) and are graded as such.It is okay to discuss general approaches and algorithms withother students, but this should be done without writing, looking,or sharing code.Cheating or plagiarism in any form will not be tolerated.You are responsible for protecting your solutions and programsfrom being copied by others.Refer to the Academic Misconduct Policy for Undergraduates.If anything is not clear, ask me.
Getting ready for Quizzes:We will be using gradescope for quizzes, etc.Please create a gradescope account as soon as possible -- our first quizwill be 1st Friday of the quarter.Make sure you use the same canvas info for your gradescope account tominimize problems with getting your accounts linked properly.From what I can see on my end, your canvas enrollment in the class isvisible on gradescope.
Also familiarize yourself with Using Gradescope with Canvas as a Student
Protecting your work:Because WebGL is run off a browser, it is important that you developyour code "offline" by pointing the browser to a local file as opposed to a publiclyaccessible url.
Submitting your work:In general, you will be submitting your program on Canvas.Put all the required materials for each programming assignment into its own folderi.e. prog0, prog1, ...Each folder should contain at least 4 files:
- features.html file -- this is the landing page for your assignment.It should contain your name, login ID,programming assignment number, date, etc.It should have a high-level description of your implementation including what wasimplemented, what was not, any special features, a user-guide if appropriate, etc.It should have at least one output image,a link to your javascript code,and a link to the driver.html file for the user (grader) to test your code.
- driver.html file -- this "runs" your code.
- your javascript code including the lib folder (with your extended cuon-matrix-cse160.jsmatrix library), and
- screen shot of your output.
All references in both html files should be local i.e.relative to your submit folder.
Your javascript code should have proper documentationincluding comment blocks for each function, and inline comments as appropriate.Code should be formatted so that it is easy for humans to read.
You can re-submit as often as you want.We will only grade the most recent submission.
Zipping your submission folder.Assume you have the following folder: progN.
$ ls -F progNcode/ driver.html features.html README screenshot1.jpg screenshot2.jpg$ ls -F progN/codelib/ prettyPix.js$ ls -F progN/code/libcuon-matrix-cse160.jscuon-utils.jswebgl-debug.jswebgl-utils.js$ cd progN$ zip -r progN.zip * adding: code/ adding: code/prettyPix.js adding: code/lib/ adding: code/lib/cuon-matrix-cse160.js adding: code/lib/cuon-utils.js adding: code/lib/webgl-debug.js adding: code/lib/webgl-utils.js adding: driver.html adding: features.html adding: README adding: screenshot1.jpg adding: screenshot2.jpg$ _Make sure that your driver.html file refer to the appropriate js file within the progN folder.
Contests:In assignments where there's room for expressing personal creativity, etc.i.e. prog2 onwards, we encourage everyone to participate.Participation involves:(a) letting the graders know that you would like to enter the contest,(b) giving your consent to let your peers view and vote on your submission.We encourage everyone to participate by voting to select the winner(s) ofeach programming contest.
Exception to copying policy:Because programs are built on top of each other, running contests actuallyserves two purpose:(a) make the class more fun by sharing/showing off your work to your peers,(b) learning from your peers -- if you decide that you want to switch yourcode base to your peer's code for the remaining programming assignments,you are allowed to do on the following conditions:(i) you acknowledge/credit your peer's work in your code and documentation, and(ii) proceed from there with your own work/effort as before.This can be done only after a programming assignment has been graded.For example, we run a contest after the prog2 due date,you can decide to use your peer's prog2 code to build your prog3.However, you cannot use your peer's prog3 code to build your prog3 as that wouldbe considered cheating.<! -------------------------------------------------------- >
Last modifiedMonday, 24-May-2021 09:55:47 PDT.
