powstik
Prove
LiveProof-of-Work · Oct–Nov: every verified proof counts. 35 days leftAll outcomes
Skills

Make 3D Graphics with Code

8 weeks · 2 milestones

Computer Graphics (UC San Diego CSE 167), then one project of your own. Part of the Varsity Curriculum: Computer Science.

Milestone map

Milestone map

2 milestones

Do the course work in public

3–6 weeks (12 hrs/week)

Take Computer Graphics for free and do the homework: transformations, a scene viewer and a ray tracer. Keep everything in one public repo or notebook as you go. Certificates cost money. Audit is free; you never need the certificate here.

Proof required

Link your public repo or notebook with the homework: transformations, a scene viewer and a ray tracer, and a screenshot or log showing the self-check passed.

What gets checked

  • Images match the reference.
  • Code builds from the README.
  • The ray tracer handles shadows and reflections.

Common mistakes

  • Copying posted answers: verifiers read the history.
  • Skipping the self-check, then asking for review too early.

Powstik Guide

A public repo or notebook with the homework: transformations, a scene viewer and a ray tracer.

Steps

  1. Make a public repo or notebook first.
  2. Do one unit at a time and commit after each.
  3. Run the self-check: Compare your images with the reference images in each homework.
  4. Write a short README: what is here and how to run it.
  5. Ask three people who know the topic to check it.

Template

README
Course: Computer Graphics (UC San Diego CSE 167)
What is here:
How to run it:
Self-check result:
What was hardest:

What gets sent back

  • No history, just one big upload.
  • Self-check not shown.
  • Code that does not run from the README.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

  • Images match the reference.
  • Code builds from the README.
  • The ray tracer handles shadows and reflections.
  • Ask one question about a choice in the code; the answer should be clear.

You'll sign in first, then come straight back here.

Render a scene of your own

1–3 weeks (5–8 hrs/week)

Use what you learned. Make a scene you designed, rendered by your ray tracer, with timing. Keep it small enough to finish in about two weeks.

Proof required

Link a scene you designed, rendered by your ray tracer, with timing, with a README that says how to run or read it.

What gets checked

  • The scene is your own.
  • The render is correct.
  • One speed-up is measured.

Common mistakes

  • A project too big to finish.
  • A demo that only works on your machine.

Powstik Guide

A scene you designed, rendered by your ray tracer, with timing.

Steps

  1. Write one line: what it does and for whom.
  2. Build the smallest version that works.
  3. Test it on someone else's machine or with someone else reading it.
  4. Write the README.
  5. Ask three people to check it.

Template

README
What it does:
Who it is for:
How to run it:
What I would do next:

What gets sent back

  • Does not run from the README.
  • Not clearly the person's own work.
  • Claims more than it does.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

  • The scene is your own.
  • The render is correct.
  • One speed-up is measured.
  • Check that the work is the person's own.

You'll sign in first, then come straight back here.

Part of