IRIS: Difference between revisions

From XPUB & Lens-Based wiki
Line 1: Line 1:
= X Theses (Ten Theses) on Life Hack=
= X Theses (Ten Theses) on Life Hack=
'''OVERVIEW'''
'''OVERVIEW''' <br>
"Ten Theses on Life Hacks" is the first publication of Special Issue #07. It attempts to acquire a widened perspective on how Life Hacks can be defined and how they relate to our collective experiences and reflections.  
"Ten Theses on Life Hacks" is the first publication of Special Issue #07. It attempts to acquire a widened perspective on how Life Hacks can be defined and how they relate to our collective experiences and reflections.  
Life Hacks are small improvisational interventions to the immediate environment; spontaneous actions that aim to improve or adapt materials to specific needs. A simple example, such as tying a knot in a earphone cable to determine easily which is for the left ear or the right without having to look, can be considered a Life Hack. They are diasporic, shared within communities both on- and offline in ever-increasing processes of self-optimisation.
Life Hacks are small improvisational interventions to the immediate environment; spontaneous actions that aim to improve or adapt materials to specific needs. A simple example, such as tying a knot in a earphone cable to determine easily which is for the left ear or the right without having to look, can be considered a Life Hack. They are diasporic, shared within communities both on- and offline in ever-increasing processes of self-optimisation.

Revision as of 16:04, 12 December 2018

X Theses (Ten Theses) on Life Hack

OVERVIEW
"Ten Theses on Life Hacks" is the first publication of Special Issue #07. It attempts to acquire a widened perspective on how Life Hacks can be defined and how they relate to our collective experiences and reflections. Life Hacks are small improvisational interventions to the immediate environment; spontaneous actions that aim to improve or adapt materials to specific needs. A simple example, such as tying a knot in a earphone cable to determine easily which is for the left ear or the right without having to look, can be considered a Life Hack. They are diasporic, shared within communities both on- and offline in ever-increasing processes of self-optimisation.

The text consists of ten theses, the first of which is a selection of criteria that allow us to test whether something is a Life Hack or not. The remaining theses present extended arguments supported by examples, on how to identify specific features of Life Hacks, in which environment (and space) they exist and what kind of culture they foster.

Understanding Life Hacks in the context of an advanced capitalist society raises the question of the ambiguity of a system in which the entrepreneurial routine of the self is internalized to perform an ever-working life. In actuality, Life Hacks bring about the possibility of reappropriating everyday life in a creative and practical response, managing precarity and complexity.

This publication includes a Life Hack in its format. With the addition of a series of holes, each loose page can be seen as a “hackable surface”. The publication aims to depart from the traditional form of a finished book, inviting readers to bind it using an eclectic choice from a range of unorthodox materials included with the publication. This strategy incentives the reader to rethink their personal ideal form of the book, transforming it into a hand-made object. As such, the publication is completed by the reader, who is left to improvise a make-shift solution to bind the publication. The goal is not only to share the text, but to also provide an experience in which a life-hacked binding transforms the reader into an active subject, rather than a passive consumer. This small conceit illustrates that the process is even more noticeable than the outcome.

Life Hack Agent: IRIS

How to run IRIS

WHAT IS IRIS

Iris 0.5 is a smart machine that interacts with you via audio, camera and visual effects. It aims to be installed in a workplace environment. Iris has 3 characters: guru, pirate and announcer. The files follow this nomination.

Banner for Iris launch Special Issue 7


















THE FILES

  • The .json files (“guru.json”, “rebel.json” and “announcer.json”) are the files where all the sentences the characters say are stored.
  • The script “guru-pirate.py” is the script that combines content of guru and pirate (from json files) to play their messages. It also integrates LEDs when the characters speak. When characters speak the LEDs light up and perform effects. This script runs when the camera detects motion.
  • The script "motion_detector_2.py" is used to detect motion from camera connected to raspberry pi.
  • The script "announcements.py" plays the messages of the Announcer (from json file)
  • The credits for this project are under the script “colophon.py”, they are read out loud with espeak when covering the camera with a finger for a few seconds.
  • “Motion.sh” is the script from where you bring everything to life. Just run ./motion.sh on your terminal.

INSTALL DEPENDENCIES

Early testings for Iris with LED's and motion detection

Last Updated on: 2018-12-12
Performed in linux Debian
Raspberry Pi 3 B+
Pi Camera v2.1
LEDs — WS2801B RGB LED Streifen Farbeffekte

  1. Install Pip sudo apt-get update sudo apt-get install python-pip
  2. Check python2 version python --version
  3. Check pip version pip --version
  4. Properly install Setuptools module sudo apt-get install python-dev python-setuptools
  5. Install opencv dependencies with pip sudo pip install opencv-python
  6. Install imutils dependencies with pip sudo pip install imutils
  7. Install Pillow dependencies with pip sudo pip install Pillow
  8. Install espeak (to play the pirate) sudo apt-get install espeak
  9. Install aplay (to play the colophon) sudo apt-get install aplay
  10. Install sox (to play the colophon) sudo apt-get install sox
Experimenting with opencv
Experimenting an option for the movement detection (with optical flow) https://docs.opencv.org/3.4/d7/d8b/tutorial_py_lucas_kanade.html
experiment on motion

HOW TO AUTOMATICALLY RUN THE IRIS ON RASPBERRY PI AT STARTUP

Tutorial on how to run a program on your Raspberry Pi at startup:
https://www.dexterindustries.com/howto/run-a-program-on-your-raspberry-pi-at-startup/

The fourth method to run a program on your Raspberry Pi at startup is to use the systemd files. systemd provides a standard process for controlling what programs run when a Linux system boots up. Note that systemd is available only from the Jessie versions of Raspbian OS.

Step 1: Create A Unit File

Open a sample unit file using the command as shown below:
sudo nano /lib/systemd/system/sample.service

Add in the following text:
[Unit] Description=My Sample Service After=multi-user.target

[Service] Type=idle ExecStart=/usr/bin/python /home/pi/sample.py

[Install] WantedBy=multi-user.target

You should save and exit the nano editor. This defines a new service called “Sample Service” and we are requesting that it is launched once the multi-user environment is available. The “ExecStart” parameter is used to specify the command we want to run. The “Type” is set to “idle” to ensure that the ExecStart command is run only when everything else has loaded. Note that the paths are absolute and define the complete location of Python as well as the location of our Python script.

In order to store the script’s text output in a log file you can change the ExecStart line to:
ExecStart=/usr/bin/python /home/pi/sample.py > /home/pi/sample.log 2>&1
The permission on the unit file needs to be set to 644:
sudo chmod 644 /lib/systemd/system/sample.service

You should save and exit the nano editor. This defines a new service called “Sample Service” and we are requesting that it is launched once the multi-user environment is available. The “ExecStart” parameter is used to specify the command we want to run. The “Type” is set to “idle” to ensure that the ExecStart command is run only when everything else has loaded. Note that the paths are absolute and define the complete location of Python as well as the location of our Python script.
In order to store the script’s text output in a log file you can change the ExecStart line to:

ExecStart=/usr/bin/python /home/pi/sample.py > /home/pi/sample.log 2>&1

The permission on the unit file needs to be set to 644:
sudo chmod 644 /lib/systemd/system/sample.service

Step 2: Configure systemd

Now the unit file has been defined we can tell systemd to start it during the boot sequence:
sudo systemctl daemon-reload sudo systemctl enable sample.service

Reboot the Pi and your custom service should run:
sudo reboot

THE BODY OF IRIS

3D printing of Iris

HACK THE PAD LIFE

COLOPHON

Iris Version 0.5 Contributors: Gill Baldwin, Simon ΆΡΤΕΜΙΣ B O B O B O B O B O B O B O B O B O B O B O B O B O B O B O Paloma Tancredi PEDRO SÁ COUTO Rita )biyibiyibiyi(, Silvio Lorusso, Aymeric Mansoux, André Castro, Steve Rushton, Michael Murtaugh, Leslie Robbins. Produced and published by the Experimental Publishing (XPUB) program of the Piet Zwart Institute, Rotterdam, December 2018. A collaboration between the Research Department of Het Nieuwe Instituut and XPUB.

You can find IRIS launching:https://burnout.hetnieuweinstituut.nl/en/activities/life-hacks-introducing-iris

Retrieved from "https://pzwiki.wdka.nl/mw-mediadesign/index.php?title=IRIS&oldid=137755"