{"id":141,"date":"2026-02-06T16:37:52","date_gmt":"2026-02-06T16:37:52","guid":{"rendered":"https:\/\/projects.etc.cmu.edu\/act-vi\/?page_id=141"},"modified":"2026-03-26T18:59:50","modified_gmt":"2026-03-26T18:59:50","slug":"blog-weeek3","status":"publish","type":"post","link":"https:\/\/projects.etc.cmu.edu\/act-vi\/blog-weeek3\/","title":{"rendered":"Week 3 (Jan. 26, 2026 – Jan. 30, 2026)"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\"Frozen\t\t\t\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t\t\t\t
Frozen Pittsburgh River view from ETC 5th floor corridor <\/figcaption>\n\t\t\t\t\t\t\t\t\t\t<\/figure>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Snow, Screens, and Quarters<\/h2>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The start of week three was chilly- literally. A snowstorm over the weekend forced us to hold our Monday instructor meeting over Zoom instead of in person. Because of limited time and the lack of access to physical resources, we presented our concepts primarily as one-liners, briefly outlining each story and direction. Had we been able to meet in the ETC building, we would have presented our storyboards and visuals in a more developed way.<\/p>

By the end of that meeting, we identified a clear set of tasks for each team member, with the goal of having something tangible to build or show during Quarters. These tasks included identifying potential AI models and APIs, researching hardware integration options (such as telephones and Arduino), preparing a TouchDesigner demo, drafting an initial software workflow diagram, and developing an early narrative framework for the performance.<\/p>

Our Quarters took place on January 28th, 2026, from 3:00 PM to 5:00 PM. In preparation, we gathered visual materials and references to help clearly communicate our ideas and research. At this stage, our concept was still broad, but we structured the room into distinct sections: narrative development, hardware research, AI models and software workflow, and a TouchDesigner demo.<\/p>

Quarters went surprisingly well. We had approximately eight instructor groups stop by our room, varying in size. Each session lasted around 20 minutes, with about five minutes dedicated to our presentation and the remaining time focused on questions, feedback, critique, and suggestions. Overall, the team felt encouraged by the engagement and responses we received.<\/p>

For the remainder of the week, we took concrete next steps, including initiating requests for AI API access, refining an initial narrative direction, and researching the various backstage roles involved in theatrical productions to better inform our design thinking.<\/p>

We concluded the week by holding our first team retrospective. During this session, we reflected on what the team should start doing, stop doing, and continue doing, along with open discussion around risks, concerns, and shoutouts. The retrospective proved to be a valuable exercise, helping us assess our progress and identify ways to collaborate more effectively moving forward.<\/p>

And with that, we wrapped up week three.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n \n
\n
\n
\n

'Start doing as a team' notes section for retrospective 1<\/h2><\/a> <\/div>\n <\/div>\n <\/div>\n \n
\n
\n
\n

'Stop doing as a team' notes section for retrospective 1<\/h2><\/a> <\/div>\n <\/div>\n <\/div>\n \n
\n
\n
\n

'Continue doing as a team' notes section for retrospective 1<\/h2><\/a> <\/div>\n <\/div>\n <\/div>\n \n
\n
\n
\n

Miscellaneous notes section for retrospective 1<\/h2><\/a> <\/div>\n <\/div>\n <\/div>\n \n
\n
\n
\n

Linda Wang writing notes for team retrospective 1<\/h2><\/a> <\/div>\n <\/div>\n <\/div>\n <\/div>\n