1.1 Schedule - Berkeley-MDes/24f-desinv-202 GitHub Wiki

Schedule detail is subject to change.

Homework, once assigned, is due based on criteria outlined in the relevant day. See below

S01 2024/08/29 w01 Th

Lecture

  • Introduction to the class, expectations, assignments and grading/rubric/respect in the classroom
  • Overview of course entry points and projects
  • Lecture Slides here

Resources

Homework (Project 1 begins) - Due Thursday 2024/09/05

If you get stuck on any particulars of laser cutting or 3D printing, feel free to consult with the Jacobs Design Specialists!

Note that you are only required to experiment with one of these machines for this assignment. If 3D printing, please print with low infill percentage (10-20%) to save on time and materials. Note that some of the Jacobs Design Specialists (Cody Glen, for example) can also help with Rhino/Grasshopper questions.

S02 2024/09/05 w02 Th

Lecture & Follow-along lab

Resources

Homework - Please complete by Monday 2024/09/09 (and log in your weekly report)

  • Make diagrams of the example files shared.
    • You choose what to represent and how to represent it. You will find this easier if you try out a couple of approaches (fail early and often!).
    • Be rigorous, be curious, and know there is not a wrong way to do this.
  • Experiment with the files shared, manipulate the parameters and ‘bake’ some forms.
    • Document your experiments. Capture what drives your thinking for changing the parameters.
  • Experiment with generating your own basic model of a form using Grasshopper.
    • Document your experiments.
    • Try replacing the nested spheres in the provided file set with a box, a cylinder, or your generated form.

S03 2024/09/09 w03 M

Work Session

  • Slide Deck from initial lecture
  • Figma-based collaborative voting session
  • Break-out groups for various topics

Homework - Please complete by Thursday 2024/09/12 (Weekly Report due by 3pm)

  • Make MORE diagrams of the example files shared.
    • You choose what to represent and how to represent it. You will find this easier if you use a couple of approaches.
    • Be rigorous, be curious, and know there is not a wrong way to do this.
  • Experiment again (yes, we have asked you twice now - separate incidents) with the files shared, manipulate the parameters and ‘bake’ some forms.
    • Document your experiments. Capture what drives your thinking for changing the parameters.
  • Experiment with generating your own basic model of a form using Grasshopper.
    • Document your experiments.
    • Try replacing the nested spheres with a box, or a cylinder.

S04 2024/09/12 w03 Th

  • Discussion of deliverables list for Project 1
  • Work Session

Homework

  • Read deliverables document carefully and develop your report and associated video
  • Work towards project 1 deliverables at your chosen challenge level
  • Keep working towards project 1 review session (video due before class on 2024/09/19)

S05 2024/09/16 w04 M

  • Guest lecture - Lining Yao
  • Panel discussion w/ Cody Glen

Homework (Project 1 finalization)

  • Finish project 1 video - Due Thursday 2024/09/19
  • Finalize most of project 1 PDF with the intention of incorporating feedback after critique

S06 2024/09/19 w04 Th

  • In-class review rounds and critique session
  • Students submit feedback

Homework (Project 1 finalization)

  • Submit project 1 report by Monday 2024/09/23 5pm

S07 2024/09/23 w05 M

  • Intro to Project 2: The Digital Ecosystem
  • In-class lecture / demo

Homework: Mapping Your Interaction Ecosystems - Due Thursday 2024/09/26

  • Create a network map that visualizes the systems, platforms, or devices you interact with daily. Add it to your weekly report. Your map should show:
    • Connections: How different elements are connected.
    • Information Flow: What kinds of information or data are shared.
    • Feedback Loops: Where feedback happens, showing how actions or data influence future behaviors.
  • Steps:
    1. Select one or more ecosystems from the categories below, or create your own.
    2. Use a diagram (digital or hand-drawn) to visualize the ecosystem.
    3. Label the connections, information types, and feedback loops clearly.
  • Types of Diagrams to Consider (choose the diagram that works best for your system):
    • Mind Map
    • Concept Map
    • System or Ecosystem Map
    • Flowchart
    • Network Diagram
    • Causal Loop Diagram
    • Data Flow Diagram
    • Service Blueprint
  • Ecosystem Categories (Starting Points):
    • Personal Device Ecosystems
    • Smart Home Ecosystems
    • Work & Productivity Ecosystems
    • Entertainment & Media Ecosystems
    • E-Commerce Ecosystems
    • Health & Fitness Ecosystems
    • Transportation & Mobility Ecosystems
    • Financial & Banking Ecosystems
    • Sustainability & Energy Management Ecosystems
  • To Include in Your Weekly Report:
    • Diagram: A map showing connections, information flow, and feedback.
    • Brief Explanation: A short write-up explaining your map.

S08 2024/09/26 w05 Th

  • Introduction to the TDF technology kit
  • Distribution of kits
  • Workshop/Demo: Connecting to UCB's IoT network
  • Workshop/Demo: Worked examples

Resources

Homework: Building your first system part 1 - Due Monday 2024/09/30

  • Compile and flash at least 3 files out of the set.
    • Document what it took to get you to the point of seeing results from these files.
    • Note that engaging with the electronics component of this demo is optional. There have been many details for configuration in software, so feel free to focus on the code itself.
  • Experiment with changing variables, names, and processes
    • Describe (in your report) what the changes you’re making in the code result in.
    • Example: Can you add a second button? How does that alter the functionality of the circuit, or the overall system? What changes are to be made in the C++ file to account for that?
    • Check the official documentation for information on specific functions and concepts.
    • Consider what you are engaging with
      • there is a
        • timing system,
        • a number of variables you’re interacting with,
        • some output (serial log, LED illumination onboard, outboard LED),
        • the ability to push results to the Particle cloud.
      • How do these elements work together to make a cohesive whole? How can a system like this benefit a new design you might consider? What are the entry points of this system? What kinds of advantages does it have over others?
        • Document your thoughts in your report.
    • What kinds of ecosystems are missing in your daily life?
      • Document your thoughts in your report.
  • Document your failures, successes, and realizations in weekly report
  • Consider how some of the pieces of the ecosystem demo you are engaging in might relate to other systems you come across (as annotated in your prior report)
  • If you are stuck on anything, post in the #tdf-vscode Slack channel

S09 2024/09/30 w06 M

  • Worked examples: Q&A
  • Workshop/Demo: Continuation and development

Resources

Homework: Building your first system part 2 - Due Thursday 2024/10/03

  • Finish 1 more of the introductory demo tutorials, keeping in mind the information we covered in class

    • Try to recall some "ah ha!" moments (exciting moments where something "clicked" for you) from our work session
      • Document in your report
    • If you haven't already, document the process of putting the circuit together in your report
      • *note that the file representing the circuit has been updated and is downloadable above
    • Try to get to the point that we arrived at in class
      • What were the challenges? What is working? What is to be done?
    • Document your findings in your report via text, images, or videos.

  • Work through any 3 of the step-by-step tutorials listed here. Note, as shared in class, that if you choose a tutorial with a servo motor you will need to obtain this from either Sudhu, Fareha, or Baurzhan.

    • Consider the following:
      • how do these demo projects differ from what we've looked at already in the prior examples?
      • What are some similarities?
      • How might the demonstrations be expanded to include a new feature? What is the feature that would be most relevant to your life?
      • How might Machine Learning play a role in the system you are imagining?
      • Can you imagine the examples being combined into a larger ecosystem? What would that system look like?
    • Document in your report

S10 2024/10/03 w06 Th

  • Project 2 details & discussion
  • Homework review, Q&A
  • Worksession: Breakout groups: special topics surrounding the Digital Ecosystem

Resources

Homework: Building your first system part 3: Stemma Modules - Due Monday 2024/10/07

  • Solder the stemma QT interface board, as demonstrated in this video
  • Download the project files and open them in Visual Studio Code (File -> open folder or see here), then in the VS Code command palette, type Particle: Configure Project for Device and follow the prompts. Hit escape when you are prompted to choose the device ID/name.
  • Your assignment is to experiment with the two stemma-based sensor projects above and document your findings.
  • Possible alterations:
    • The demo firmware doesn't do much, aside from outputting log data to the serial port.
    • Can you map these values to other processes in the firmware code? What might that look like? What sort of feasibility experiments are in the way?
      • You might try out using the map() function! What sort of output range would you need if you were going to output values for an LED?
      • If you don't know exactly what range of values you're getting from a sensor, try printing to the serial monitor with Log().
      • Are the values noisy, and possibly lying outside of an expected range? Try using the constrain() to clamp things down a bit before performing your mapping.
      • How might you smooth out the values?
    • Secondary feasibility experiments:
      • How might you send the values from your sensors to other output components?
      • What about sharing those values with a partner in the class, using Particle.publish() and Particle.subscribe() ?
  • Document your design/considerations as a diagram in your report.
  • Notes:
    • If you are stuck in Visual Studio Code with issues surrounding compilation, please reach out to the TDF Teaching team for assistance!
    • Errata: Check out the difference between qwiic and stemma. Can you spot it?

S11 2024/10/07 w07 M

  • Homework Q&A
  • Project 2 details, deliverables, & first assignment
  • Team building exercise
  • Example project proposal
  • Examplary projects

Homework: Due Thursday 2024/10/10 by 3pm

  • Work on your project proposal with your team
  • See this document for a template proposal which fulfills the requirements for the PDF. Use this template for your own proposals.
  • Bring the printed PDF with you to class on Thursday for a desk critique session

S12 2024/10/10 w07 Th

  • Desk Crits: Digital Ecosystem Proposals

Homework: P2 development

  • Fine-tune / develop your project proposal over the weekend
  • Consider resubmitting if you've improved the document
  • Proposal PDF is due in bCourses by Monday at 3p
  • Initiate some feasibility experiments associated with your project
    • what are the questions you need to be asking right now?
    • which experiments have you planned for the future?
    • which experiments have you already carried out?

S13 2024/10/14 w08 M

  • Desk Crits: Digital Ecosystem Feasibility evaluations

Homework: P2 development

  • Continue working on your group project at your chosen challenge level
  • Log your developments in your weekly report
  • Submit weekly report by Thursday 11:59pm
  • Submit weekly personal assessment form by Thursday 3pm

S14 2024/10/17 w08 Th

  • Desk crits
    • Discussions about revisions to proposals
    • Discussions about progress on experiments

Homework: P2 development

  • Continue working on your group project at your chosen challenge level
  • Log your developments in your weekly report
  • Submit weekly report by Thursday 11:59pm
  • Submit weekly personal assessment form by Thursday 3pm

S15 2024/10/21 w09 M

  • Desk Crits involving
    • Discussions about deliverables
    • Discussions about progress on experiments

Homework: P2 development

S16 2024/10/24 w09 Th

  • Project 2 review: In class critique

Homework: P2 PDF

  • Incorporate feedback from your peer group regarding group video into your final PDF report
  • Finalize report and submit via this link by Monday 2pm
  • Submit weekly report by Thursday 11:59pm
  • Submit weekly personal assessment form by Thursday 3pm

S17 2024/10/28 w10 M

Lecture:

  • Introduction to Project 3
  • Introduction to LLMs, Introductory lecture by TJ
    • Key Concepts + Explorable
      • LLM > One word at a time.
      • LLM > Probabilistic paths
      • Tokens and Tokenization
      • RAG > Embeddings > Semantic Similarity
    • On the design of an AI agent
    • Project deliverables
  • Introduction to ZeroWidth by Peter Binggeser
    • Introductory background
    • Introduction to the ZW workbench

Resources:

Homework: P3 (suggested due date 10/31 by 3pm in report)

  • Goals for the week, capture in your weekly report
    • Set up your account [should be available to set up before class]
    • Follow tutorials to at least make your first thing input+LLM+output.
    • It is possible to get through all 4 experiments by the 31st.
    • Have demo links to share with the cohort and friends.
    • Review project deliverables
    • Review project examples
  • Submit weekly report by Thursday 11:59pm
  • Submit weekly personal assessment form by Thursday 3pm

S18 2024/10/31 w10 Th

  • ZW Workbench tutorials - 45 minutes
  • Other examples
  • Work session + Q/A

Homework: P3 (for next week)

S19 2024/11/04 w11 M

  • Work Session involving Project 3
  • Q/A

Homework: P3

S20 2024/11/07 w11 Th

  • Review of Project 3: In class critique
  • Individual Video Presentation (see deliverables)
  • Peer feedback

Homework: P3 / P3 PDF

  • Incorporate feedback from your peer group regarding individual video into your final PDF report
  • Finalize report and submit by Thursday 5pm
  • Submit weekly report by Thursday 11:59pm
  • Submit weekly personal assessment form by Thursday 3pm

S21 2024/11/14 w12 Th

  • no class on Monday this week: Veteran's Day
  • Introduction to Project 4
  • TDF Project 4 examples
  • Break / Q&A
  • Guest Lecture: Leila Madrone

Homework: P4

  • TBD (based on results of vote)

S22 2024/11/18 w13 M

  • Pin-up session

Homework: P4

S23 2024/11/21 w13 Th

  • Desk Crits: Proposal revisions and check-in on experiments

Homework: P4

  • Teams: Finalize your proposal based on discussions in desk crits and submit to bCourses here

S24 2024/11/25 w14 M

  • Team proposals due by 5pm in bCourses here
  • Desk crits [roving]: TDF staff meets team members at their work sites
  • Note: 2024/11/28 Thanksgiving - No class

S25 2024/12/02 w15 M

  • Guest Lecture: Jamie Ikeda (Dubberly Design Office)
  • Desk crits [roving]: Working prototype discussed at your place of activity
  • Note: There is no class on 11/28; Thanksgiving Holiday

S26 2024/12/05 w15 Th

  • Desk crits [roving]: Working prototype discussed at your place of activity

Homework: P4

  • P4 video due by 12/09 5pm. Submit your assignment link here, as well as in the form (form TBA).

S27 2024/12/09 w16 M

  • P4 video due by 5pm. Submit your assignment link here, as well as in the form (form TBA).
  • Practice presentations for Jacobs Design Showcase
  • In-class presentations: Final prototypes

--- 2024/12/12 w16 Th

  • TDF does not meet today
  • MDes Cohort 5 Design Showcase

--- 2024/12/19 w17 Th

  • TDF does not meet today
  • P4 PDF Report Due by 7pm