The primary purpose of your Presentations  at NuVu is to describe the creative and technical journey you undertook in developing your project. In this post you will write what you are going to say, slide by slide, for your Final Post.   During your presentation you will not read from this script. It is here to help you frame your presentation and give insight to website visitors. 

Remember, you are encouraged to make your narrative as compelling as possible. All of the content below should be included, but if you would like to rearrange the material in order to tell your story differently, work with your coach.

Feel free to organize the post by slides in the presentation. The example below if for a build studio but the concept holds for a film/animation studio.

Slide 1: Write out your title and tagline.
Slide 2: Describe why your project exists, who it is for, and how that relates to the evocative image.
Slide 3: Write out your thesis.
Slides 4-15: Walk through each iteration, from initial concept to penultimate design

• Discuss how each precedent inspired/informed your design.
• Discuss your  sketches - how they arose from your brainstorming and how they informed the start of your design process, and how they changed and your design changed
• Discuss each prototype - Briefly describe major design changes and how they effected the overall project arc and design.

Slide 16: Explain your use diagram - how is your your project used or function in the world.
Slide 17: Explain your mechanical diagram. Walk through how your project is put together and functions mechanically.
Slides 18-20: Walk through each of the final images and describe the overall use/design of project. Discuss the final prototype, what was a success, and where your project might go from here.

Your Presentation will:

• Introduce the general context of your project
• Present the thesis or design problem and how you approached the solution
• Using precedents, begin to tell the story of the genesis and development of your actual design.
• Describe the overall design concept.
• Delve deeply into the heart of the design process through a description of major design iterations.
• Thoroughly describe the final design technically and functionally through the reference to your diagrams.
• Walk through the final images, discussing how everything came together.
• Discuss the conceptual and technical challenges you faced. These should be broad view issues, not hyper-specific technical issues.
• Your vision for where your project can go.

THE PRESENTATION POST

This post's privacy is set to Everyone. This post showcases your final design by telling the comprehensive story of how your idea was born, developed, and manifested. The arc of the story should encompass the, How of your project in a compelling narrative. It showcases your design process including your brainstorming, each of your iterations, and your final prototype. It allows the viewer to delve deeply into your process.

• Every Slide should have a Title and Caption.
  The body of this post is The Brief. You should include a version of the Brief for each collaborator in the project.
• This post will be used in your review presentation at the end of the session.

You are encouraged to make your narrative as compelling as possible. All of the content below should be included, but if you would like to rearrange the material in order to tell your story differently, work with your coach.

INTRODUCTION PORTION

Your presentation is a narrative, and the introduction sets up the scene for that story. Here you introduce the project, say why it is important, and summarize what you did.

TITLE WITH TAGLINE: This slides shows a crisp, clear final image and the title of your project. with a pithy blurb describing the project. The image, name, and tagline should draw a viewer in. 

Examples:

• The Fruit - A line following, light tracking robot
• Segmented Vehicle - A vehicle that conforms to the landscape
• Cacoon - Wearable sculpture exploring the concept of transformation and death

EVOCATIVE  IMAGE: This is a single image that shows a clear image that evokes the soul of your project. This image helps set up the why in a compelling way, sets the stage for your narrative, and will help frame the entire presentation. The caption of this slide (set with the Edit Captions button when editing your post) should discuss the context of your project. No Text on the slide.

THESIS STATEMENT: This is a TEXT ONLY slide for which briefly describes the Soul and Body of your project. You can use the project description from your Brief or write something new. This statement ties together your narrative.

Examples:

• The Cocoon:  A wearable sculpture that explores the concept of transformations and death. The Cocoon explores the spiritual journey beyond the human experience; what it means to be human, how wonder effects us, and the concept of what happens after death.
• Body Accordion: A musical prosthetic that translates the wearer’s body movements into a dynamic multimedia performance. The Body Accordion converts flex sensor input to sound through Arduino, MaxMSP, and Ableton Live. 
• Seed to Soup Animation: A whimsical animation about the slow food movement. Seed to Soup showcases a holistic method of cooking. From garden, to kitchen, to dinner table.
• Antlers: A wearable sculpture inspired by antlers found in the deer and antelope family. "Antlers" explores the comparison between armor and attraction. 

PROCESS PORTION

The Process Portion of your presentation tells the story of how you iteratively developed your project. Somewhere in that story you should include conceptual and technical precedents that guided you at each stage as well as brainstorming and process sketches and clear photo booth imagery for 3-4 stages of your process.

This portion is made up of three types of slides repeated 3-4 times. Each iteration in your process should include:

• PRECEDENTS:  Precedents are any projects that inspired you creatively or gave you technical guidance. These can include conceptual precedents and technical precedents. No Text.
• SKETCHES/SKETCH CONCEPT DIAGRAMS: These slides show your generative ideas in sketch form. These should clean, clear drawings. A sketch should show a clear idea. Do not simply scan a messy sketchbook page and expect that people will understand. If you do not have a clear concept or working sketches it is fine to make them after the fact. No Text.
• PROTOTYPE IMAGES:  These are actual images of the prototypes  you documented in your daily posts. These images illustrate your design decisions and how your project changed at each step. No Text.

FINAL PORTION

The Final stage of your presentation is the resolution of your narrative and shows your completed work. The use diagram shows how your project works and the construction diagram shows how it is assembled. Final photos show the project both in action and at rest. The imagery captures your final built design.

USE DIAGRAM: A diagram showing some aspect of the functionality. These can include:

• How one uses or interacts with the project
• The overall behavior of the project over time
• For a complex interactive project, this can be a clear diagram of the software behavior

MECHANICAL DIAGRAM:  A diagram offering insight on how the project is put together and functions technically.

• Ideally, this will be an exploded axonometric
• At minimum this can be a labeled disassembled photo  

ELECTRONICS or OTHER DIAGRAM: Additional diagrams showing some important aspect of your design. 

IMAGERY: The last slides should have an images of the final project. These images should be taken in the photo booth, cropped, and adjusted for contrast, brightness, etc. Images should include:

• An image of the project in use (taken in the booth or at large). This should include a human interacting with the project.
• Images of project alone. Include at least one overall image and one detail image.
• You can also use an image In-Use. 
• Consider using a GIF to show how the project works. 

The primary purpose of your Presentations  at NuVu is to describe the creative and technical journey you undertook in developing your project. In this post you will write what you are going to say, slide by slide, for your Final Post.   During your presentation you will not read from this script. It is here to help you frame your presentation and give insight to website visitors.

Feel free to organize the post by slides in the presentation. The example below if for a build studio but the concept holds for a film/animation studio.

Slide 1: Write out your title and tagline.
Slide 2: Describe your Problem/Solution or Thesis
Slide 3: SAY NOTHING!
Slide(s) 4: Discuss how each precedent inspired/informed your design.
Slide 5: Discuss your initial sketches - how they arose from your brainstorming and how they informed the start of your design process.
Slide(s) 6: Discuss each iteration - Briefly describe major design changes and how they effected the overall project arc and design.
Slide 7: Walk through the construction diagram to describe the technical aspects of the final design fabrication and underlying structure or electronics functionality.
Slide 8: Explain your functional diagram - how is your your project used or function in the world.
Slide(s) 5: Walk through each of the final images and describe the overall use/design of project.
Slide(s) 10: Discuss the final prototype, what was a success, and where your project might go from here.

Your post will:

• Introduce the general context of your project
• Present the thesis or design problem and how you approached the solution
• Using precedents, begin to tell the story of the genesis of your actual design.
• Describe the overall design concept.
• Delve deeply into the heart of the design process through a description of major design iterations.
• Thoroughly describe the final design technically and functionally through the reference to your diagrams.
• Walk through the final images, discussing how everything came together.
• Discuss the conceptual and technical challenges you faced. These should be broad view issues, not hyper-specific technical issues.
• Your vision for where your project can go.

    In this studio, we were challenged to make an art piece that kept people busy while they waited for the bus. The first solution we came up with, was making a pedal box under the bus stop seats, that would allow commuters to pedal and generate electricity. This could be used for charging electronics or powering a sign that tells you when the bus is coming. We later pivoted because this was kind of a solitary idea. Although it encouraged you to charge and use your phone, it wasn't really a form of art. So, we wanted to make something that was interactive, communal, and is a piece of art. We split up to come up with ideas, and we all decided on a large cylindrical music box that you could spin around a pole making music.

Our goal was to create a device to let kids see above their normal field of vision into the natural space of treetops, so that their experience of sight is changed and transformed into a personal adventure. We did this by making a looking device that can be used to see above the treetops.

We made a device that will give children a different experience, inspiring them to think outside of the box, and igniting their imaginations as they see the world from above the trees.  This device can also be rotated and moved up and down with motors to adjust and broaden their field of vision. As a kid I was always shorter than my parents, and up until a about a year ago, that remained true.  I feel that the fact that parents are generally tall gives them a certain sense of authority that kids just can’t seem to muster up.  The day that I became taller than my mom, everything changed.  That day I became a grown up, well not really, but it would have been nice.  Kids associate height with maturity.  They think that people who are really tall, are really grown up. This device that we created evokes that feeling of maturity and equality to adults in children anytime they want.

Our project brings back your memories of climbing trees and being young/younger again. We wanted to make a periscope that could move. Our periscope is adjustable in height, using a rack and pinion and motor.  The device also swivels at its top most part with two gears and a motor.  The top of the periscope is mounted on a ball bearing, so that it swivels, and can still maintain the shape of a rectangular box.  The two motors are hooked up to an Arduino that we programmed to adjust the direction of the motors based on the turning of potentiometers.  There are also two mirrors mounted at 45-degree angles in either end of the periscope.

After coming up with the feeling we wanted to convey from using our object, we got to work sketching the designs for our periscope. From our sketches, we decided that we primarily wanted our periscope to move up and down in height, rotate 360 degrees, and to be mounted on a tree. We first began the construction of our periscope using PVC, but soon realized that the shape of the PVC would be hard to mount onto a tree. We then moved on to a more rectangular shaped periscope with two rectangular pieces that made the scope but ran into the problem that rectangular boxes do not swivel very easily within each other. We then came up with our final design for the periscope, in which we now have three rectangular boxes that are all connected. We added the final touches to our periscope by attaching a rack and pinion with a motor; to adjust the height, and adding a motor and ball bearing to the top, which helps the top piece of the scope swivel.

One of the main design challenges in this project was enabling the periscope to move up and down, but also rotate.  The reason that this proved to be so difficult was because we wanted a rectangular design for the periscope for sturdiness and so that the scope could be easily attached to a tree.  We also are still faced with a challenge regarding the mirrors.  If someone looks into the periscope and the scope rotates without the viewer moving their head, then the image that the viewer is seeing slowly starts to flip upside down.

For the first iteration of the periscope we decided to make the body of the scope out of PVC Pipe.  The problem with this was that we did not have the correct size PVC pipe to make the scope, so we had to make it very small, which meant that the mirrors would be small.  In the first iteration, we were going to cut circular mirrors, but a coach suggested that we use oval mirrors instead.  This worked a lot better because the viewer could see more through the scope and due to the larger size of the mirror.  We also wanted the periscope to move up and down.  The scope was made using two PVC pipes, with the bottom PVC pipe cut in half.  The reason we did this was because we wanted to make a slot for handles to put on the top piece so that it could be moved up and down.  The problems with this method were: the slots on the side let in too much light, the handles of the scope could be seen when the viewer looked through, and the top part of the scope was unstable due to the diameter of the bottom piece being too large.  The next iteration fixed this issue.

Our second iteration we decided to laser cut cardboard so that we could have better fitting components. We made two large rectangles, one was smaller than the other so we could fit inside without letting in any light. We also made it a lot bigger so that we could have bigger mirrors. One of the main problems was that it could not turn side to side. Because of the weight of the upper part, it was hard to move up and down.

For our third iteration we  talked to coaches, and we decided to make a smaller version so that we could focus more on the mechanics. We decided we wanted to move it up and down with a gear, but we were not sure about how to move it side to side. We made this iteration out of laser cut thin wood. We made two rectangles, one smaller than the other. Both rectangles had a side that was cut diagonally for the mirror and a hole to see through. A problem with this iteration was that we didn't account for the width of the wood, and the smaller rectangle did not fit inside the bigger rectangle.

For our final Iteration we needed some way for the periscope to rotate while keeping the user’s head stationary.  After talking with a coach, he came up with the idea of having a ball bearing at the top of the periscope, on which the top most part of the scope would be mounted.  The reason it would have been so hard to do this with one piece of the scope inside a larger piece is because one cannot rotate a square inside another square with a similar side length.  He also said that we could have a middle part of the periscope that would be smaller that the bottom so that it could travel up and down with a rack and pinion