From ac93464581a3314ac4146d29be8e4ef97c58c1d5 Mon Sep 17 00:00:00 2001
From: Kevin Du <109395354+kevinwd2401@users.noreply.github.com>
Date: Wed, 12 Nov 2025 11:48:10 -0500
Subject: [PATCH 1/2] Update README.md
---
README.md | 27 +++++++++------------------
1 file changed, 9 insertions(+), 18 deletions(-)
diff --git a/README.md b/README.md
index c9c012d..4ae0fd4 100644
--- a/README.md
+++ b/README.md
@@ -1,26 +1,17 @@
# lab06-proceduralFace
-Let's practice parameterization! We'll be starting with an oh-so-beautiful gingerbread man face that looks like this:
-
+For this procedural SDF face, I add the two parameters SURPRISE and JUDGEMENTAL, taking in values from 0 to 1 and modifying the resulting face to express the intended emotions.
-## Setup
-Start by forking [this shadertoy](https://www.shadertoy.com/view/XftyR8)
+## Link
-## Task 1
-In the faceSDF function, add a new float parameter called SUPRISE a value between 0 and 1. Copying the way EYE_SEPARATION is used, modify the face such that the gingerbread face looks more or less surprised based on the value of SURPRISE. SURPRISE = 0 should be not very surprised, and SUPRISE = 1.0 should look very surprised. Note that the face shouldn't look broken for any value in that range!
-Changing this parameter should change at least 3 geometic attributes of the face and more than one facial feature (just eyebrows are NOT SUFFICIENT).
+https://www.shadertoy.com/view/332BWK
-
+## Images
-## Task 2
-Your own parameter! Create a new attribute of your choice that maps to a procedural face characteristic in the domain of [0,1]. It SHOULD NOT be a literal attribute, eg. eye-separation or mouth size, but instead a more qualitative, subjective quality that you tie to specific geometic parameters using your design sense. Have fun!
+Here are the results.
-## Extra Credit
-In the faceSDF function, create a new float parameter called SADNESS. Follow the same guidelines as outlined in Task 1.
-
-## Submission
-- Create a pull request to this repository
-- In the README, include the names of both your team members
-- In the README, create a link to your shader toy solutions
-- Make sure your shadertoy is set to UNLISTED or PUBLIC (so we can see them!)
+|
|
|
+| *SURPRISE: 0, JUDGEMENTAL: 0* | *SURPRISE: 1, JUDGEMENTAL: 0* |
+|
|
|
+| *SURPRISE: 0, JUDGEMENTAL: 1* | *SURPRISE: 1, JUDGEMENTAL: 1* |
From df73b0d29fbda217db7a37ff869ca7943054f89c Mon Sep 17 00:00:00 2001
From: Kevin Du <109395354+kevinwd2401@users.noreply.github.com>
Date: Wed, 12 Nov 2025 11:49:49 -0500
Subject: [PATCH 2/2] Update README.md
---
README.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 4ae0fd4..43b9d4e 100644
--- a/README.md
+++ b/README.md
@@ -10,8 +10,9 @@ https://www.shadertoy.com/view/332BWK
Here are the results.
-|
|
|
+|
|
|
+|:--:|:--:|
| *SURPRISE: 0, JUDGEMENTAL: 0* | *SURPRISE: 1, JUDGEMENTAL: 0* |
-|
|
|
+|
|
|
| *SURPRISE: 0, JUDGEMENTAL: 1* | *SURPRISE: 1, JUDGEMENTAL: 1* |