---
title: MDEF 20/21 - TAUMs Daily
description: Learning two week class convining Unpacking Intelligent Machines and The Almost Useful Artifacts
Autors:
---
###### tags: `MDEF` `FLU` `Future Learning Unit` `Fab Lab Barcelona`
**Syllabus:** https://hackmd.io/TdLbzvcbTrm8HG6xkYFNeg
# TAUMs
[TOC]
## DAY 1 - UNPACKING
### Presentation
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQz-VHLMT0WI3EKrCQ5N9v95mbqNWALZpHpdmqm5MAJnVZ3HgkeWfYG3G2L6_MUDquqNL2n2s3jTspd/embed?start=false&loop=false&delayms=3000" frameborder="0" width="700" height="425" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
### Micro Assignment
:::info
Complete the forencic report canvas
:::

**Board:** https://miro.com/app/board/o9J_leyn0go=/
**Pass:** UNPACKING
## DAY 2 - HACKING
### Presentation
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vTvDyg1DUUpSYi3Y1PPJBVAsFeOPHrbJ27vghsicCv_4CrLR4jvvmO7MyyVSWeb_7po-s2lYvmA4_zY/embed?start=false&loop=false&delayms=3000" frameborder="0" width="700" height="425" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
### Micro Assignment
:::info
**1. CONCEPT CANVAS:**
- Discuss with the group to decide to useless ideas you would like to conceptualize.
- Add FAB-HAIKU description
- Add a sketch (Think how you could bring it down to earth, make it real)
- Add References (images, videos, links... )
.
**2. INVENTORY**
* Select the most interesting components out of the forensic report activity.
* Mark is it an Input or an Output
* Add Useful info (how to use, based in your experience)
* Add Technical info (datasheet)
* Add the source (machine it comes from)
:::

**Board:** https://miro.com/app/board/o9J_leyn0go=/
**Pass:** UNPACKING
### Resources & References
* [Data set for CO2 emissions saved from repair activities](https://docs.google.com/spreadsheets/d/1MMkPsyrI6ulWkyz6tJbXONUXiOqKWj2v-2cSPJEzuEo/edit?usp=sharing)
## DAY 3 & 4 - CONCEPTS TO PROTOYPE
### Interfacing the Real World
[From physics to information](https://fablabbcn-projects.gitlab.io/learning/precourse/#electronics_coding/information_theory/)
[Programming with the Arduino IDE](https://fablabbcn-projects.gitlab.io/learning/precourse/#electronics_coding/from_ideas_to_code/#arduino-programming)
[Sensors and Actuators](https://hackmd.io/xAjS5n_ASTOmX9EhacRRhw?both)

### Micro Assignment
:::info
**1. BAZZAR:**
* Place on a big table all the component reports, in a way that everybody can see them.
* After everybody checks and gets familiar with all the components, 1 group will explain the idea of the Artifact and what are the needs to cover (linear movement, triggers, sound sensors….)
* The rest of the class will select and give to them the item of the inventory that mostly solves the needs that the group has.
* Repite the process with the rest of the groups, at least 2 times.
* After that each group can choose 2 more items.
:::
**Board:** https://miro.com/app/board/o9J_leyn0go=/
**Pass:** UNPACKING
### Resources & References
* [Project impact report](https://docs.google.com/spreadsheets/d/1e_-gx9A9upbinwrfL5san7AbmY7svLnIhWutE2bsHng/edit#gid=1451489466)
## DAY 5 - ARTIFACTS
### Roadmap
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vSotdPbpOFVWF2dkrwb5kY9q4ceWMOPfntVZcP1Cs11aFtepeNg0Jjlzt9FR4flZ7kVfIuyrbT9zqGx/embed?start=false&loop=false&delayms=3000" frameborder="0" width="700" height="425" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
### Continous review
We will setup **checkpoints meeting** every 2h, with a group of instructors to evaluate risks, needs and status of each project development.
#### Check point 1
**Location: 301 MDEF Classroom**
**Time: 12:00PM to 13:00M**
* Group 1 - From 12:00 to 12:15
* Group 2 - From 12:15 to 12:30
* Group 3 - From 12:30 to 12:45
* Group 4 - From 12:45 to 13:00
#### Check point 2
**Location: 301 MDEF Classroom**
**Time: 15:00PM to 16:00M**
* Group 1 - From 15:00 to 15:15
* Group 2 - From 15:15 to 15:30
* Group 3 - From 15:30 to 15:45
* Group 4 - From 15:45 to 16:00
## DAY 6 - CONNECTION
### Presetnations (Some thoughts on the internet)
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vTmUxL9ZhHY8xN9ZH_BK11pHehCGEOJKK-RrlpXx6tMaWtAhEQAw2M4s7TzVmYOng/embed?start=false&loop=false&delayms=3000" frameborder="0" width="100%" height="600px" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
### Resources & References
- [**The cloud that wasn’t**](https://hackmd.io/v5JR5EtTSqCizcL7f2lcoA?view)
## DAY 8 - INTEGRATION, DOCUMENT & REFLECT
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vT408NMSXQE04juIIfVjHc5lkSvgJqlCA4LJ-6un1wvq40tBk9fgO5AzmRUo0fhE_czH6eVMswz3PIk/embed?start=false&loop=false&delayms=3000" frameborder="0" width="100%" height="450px" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
## DAY 9 - FINAL SUBISSION
### Submissions
All the students have to document their work for the course:
- **Personal reflexions and learning outcome post** (personal MDEF webpage)
- **Video and Slides of the machine** (Google drive)
The deadline for the students to submit their work for your seminar is **Sunday the 6th of December.**
### Presentation Requirements
#### Video
- Video at minimun 1080p stabilized (not hand held recordings, use a tripod if you don´t know how to stabilize by software)
- Black, gray or white background.
- Open source music matching the artifacts(properly acknowledged).
- Ideally the sound produced by the machine will be also recorded in the video.
- Entry and finish titles with Team names, name of the artifact and Iaac/FablabBCN .
#### Slides
Min 10 slides presentation on:
* Concept/s of the machine
* How you designed it
* What is supposed to do or not to do?
* How did you fabricate it (fabrication processes and materials)
* System diagram (illustration explaining function, parts, and relations)
* The coding Logic (Algorithms and flow charts, pseudocoding )
* Photographies of the end artifacts at high res.
* Iteration Process - Learning by Accomplishments and failures
* *Hybrid teams feedback (reflection out methodology workflows)
## PROJECTS
### The Subjective Machine
Our machine embodies the concept of subjectivity. Challenging the idea of machine’s supposed objectivity in the achievement of a concrete goal or purpose, we propose to work with uncertainty in an outcome that is non linear in relation to the inputs.
The feelings we want to promote through this exercise were surprise, playfulness and the joy of the unexpected.
- [Documentation](https://drive.google.com/drive/u/0/folders/1JLjMGfwdVd8W_NRHzDd-fRnwytV94KWp)
### THE TEARS OF ICECREAM
I’m so useless. Don’t believe me? I’m the reason why you’ll end up being frustrated, why you’ll question your actions - over and over. I’m the reason for your nightmares, for crying children’s eyes and annoyed parents. I am the black swan, your black swan. Making sure you will also lose the last bit of hope.
Activated by human beings’ lust, I start powering my two reassembled motors. I’m partly printer, partly toaster. By manipulating you as a user, I try everything that you won’t be able to place the ball of ice cream into the cone nearby. But I do definitely not work without the human desire as an input.
- [Documentation](https://drive.google.com/drive/folders/1ggzBKCqneXgzpw4ZYgodVmIHCE0ENoiJ))
### The Validation machine
This machine gives you validation when you need it in the form of a push start high five.
- [Documentation](https://drive.google.com/drive/folders/1wYaKS_RyOwifANzTEyrnaMBpsNHdzITj)
### DISTRESS vs relief
We wanted to create a digital animal that shows signs of life—responding to the world in a limited but impossible to ignore way.
- [Documentation](https://drive.google.com/drive/u/0/folders/1JLjMGfwdVd8W_NRHzDd-fRnwytV94KWp)
## PROCESS PHOTO COLLECTION

https://photos.app.goo.gl/JZ9ZTgxsHfwPBM1Y6