search

CityScope / CS_Cooper-Hewitt

meta repo/sandbox repo for keeping everything related to the Cooper Hewitt exhibition
5 stars 2 forks source link

System auto booting #108

Closed yasushisakai closed 5 years ago

yasushisakai commented 5 years ago

  1. self power on when power failure system runs forever, system should reboot by itself when power failure.

  2. auto destruction? we self shutdown the system (not the projectors) at a configured time. (say 8pm) Manual power on. Two button pushes every day.

    1. and 2’,. but power on is scheduled (like 7am using mac’s native power on), should also run programs automatically by manual power on too.

  4. leave it until it dies. We receive a phone call.

we can have different policies for each computer, but for simplicity, we keep it the same as a start.

I’ll start with auto booting programs for the good computer.

agrignard commented 5 years ago

For the autobooting let's also coordinate and populate this page at the same time https://github.com/CityScope/CS_Cooper-Hewitt/wiki/User-Guidelines---Installation-starting

yasushisakai commented 5 years ago

Booting order:

Wait duration may change.

First, The Bad Computer (7:00am)

  1. System starts, auto-logins to badcomputer

  2. Starts Unity.app via ‘’’login items’’’

—- wait at least for 3min if manual rebooting—-

Second, The Good Computer (7:10 am)

  1. System starts, auto-logins to cityscience

  2. Wait for 3 minutes (wait for network connection)

  3. Start Simulation via processing-java command

  4. Wait for 1 minute

  5. Start Scanner/Slider

agrignard commented 5 years ago

@yasushisakai I might be a bit pushy but what about editing directly the wiki?

Then we are done and anyone can validate it by trying to restart the install by following like a sheep the wiki? https://github.com/CityScope/CS_Cooper-Hewitt/wiki/User-Guidelines---Installation-starting

popabczhang commented 5 years ago

I added the instruction for the "The Bad Computer" part.

On Mon, Nov 26, 2018 at 2:02 PM Arnaud Grignard notifications@github.com wrote:

@yasushisakai https://github.com/yasushisakai I might be a bit pushy but what about editing directly the wiki?

Then we are done and anyone can validate it by trying to restart the install by following like a sheep the wiki?

https://github.com/CityScope/CS_Cooper-Hewitt/wiki/User-Guidelines---Installation-starting

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CityScope/CS_Cooper-Hewitt/issues/108#issuecomment-441757100, or mute the thread https://github.com/notifications/unsubscribe-auth/ACrA-KJHUQ_eZ2dWd8a6AQCdGydSxHI0ks5uzDq1gaJpZM4YzUe1 .

--

YAN ZHANG "RYAN"

PH.D. STUDENT, ASSISTANT RESEARCHER MEDIA ARTS & SCIENCES, MEDIA LAB MASSACHUSETTS INSTITUTE OF TECHNOLOGY

M.S. ADVANCED ARCHITECTURE DESIGN COLUMBIA UNIVERSITY IN THE CITY OF NEW YORK

20 AMES STREET, BUILDING E15-368 CAMBRIDGE, MA 02142

1(917)767-3589 POPABCZHANG@GMAIL.COM

yasushisakai commented 5 years ago

https://github.com/CityScope/CS_Cooper-Hewitt/blob/master/good_computer.sh This will trigger the simulation and scanner.

It gives 3min after reboot, triggers simulation and (one minute) than the scanner.

I’ve not yet configured the self destruction and self wake up

yasushisakai commented 5 years ago

Updated the Good Computer part in the wiki.

RELNO commented 5 years ago

@yasushisakai autoboot script does not show the python terminal that helps debugging udp/cam/slider. Can you try to bring it back?

yasushisakai commented 5 years ago

Lates good_computer.sh attaches the scanner session and shows in front. @RELNO a little bit of tmux instructions here:

tmux a -t scanner

Will attach the session to the current terminal. To detach, you will need to press Ctrl-b, then d.

For some reason, if the session was killed, (you can see the list of tmux session by tmux ls) you can make it again by tmux new -s scanner that will take you to the session, and you can run commands like python3 scanner.py

The are three reasons using tmux, 1. Minimal number of windows of terminal instances, 2. Being able to access through ssh(we don’t know if eventually we can though) 3. Easy killing the processes tmux kill-server.

yasushisakai commented 5 years ago

Success of #116 closes this issue.