This week we’ll be learning how to proportionally ‘map’ values from one range to another—a concept typically referred to as ‘interpolation’ or ‘normalization’. It becomes especially useful when attempting to represent numerical values on-screen since every raw value must in some way be transformed before it can be used as a pixel coordinate, color, dimension, or the like.
Complete at least three representations of the current time (ignore days, weeks, moons, etc. for now) that develop on your sketches from last week.
This time everything must be done in code. Use the clock() function to access different attributes of the current time (a listing of its property names is included in the assignment).
Make sure each approach addresses hours, minutes, and seconds in such a way that the representation looks different over the course of a day, hour, and minute.
Start by remixing the Project Template three times and naming them yourname-clock-1, yourname-clock-2, and yourname-clock-3. Once you’ve completed each sketch, rename the Glitch project with a more descriptive suffix (e.g., yourname-clock-1-radial-seconds)
Due date: 10/15 by 6 a.m. EDT
Format: Three Glitch-based p5 sketches
How to submit: Paste the links to your p5 projects into this form
Add three new pencil sketches to your folder in the shared GD355 Activities folder in Google Drive that this time focus on representing at least two of the longer-term calendar variables (and for these you don’t need to worry about incorporating the wall-clock time)
Each sketch should choose two or more calendar-date values to represent (e.g., day-of-week, day-of-month, month, moon, season, or year) and you should use a different retinal variable for each value (i.e., 6 different retinal variables across the 3 sketches)
Since calendar units use much more irregular values than clocks do, pay extra attention to the progress attributes provided by the clock() function and figure out how to map their 0–1 values into an appropriate range to use for drawing
