Skip to content

Getting Started OSA

John Gamboa edited this page Sep 18, 2017 · 5 revisions

IMPORTANT INFORMATION

Machine Identification

Each machine in OSA is identified with a number. You'll see many orange stickers in the tables with writings like mg1 or mg7 (or, also, on the top of the CPUs, you'll find a number). This is how we intend to call each machine in this event. IGNORE ANY OTHER NAME/IDENTIFICATION YOU MAY FIND IN THE MACHINE (the other names are generally used in MindGarage in Kaiserslautern, and may strongly conflict with the names in OSA)

Islands

Islands are numbered from 1-3. Each island has two groups and one machine that is shared in that island. You will find white stickers indicating what is the machine of the group. Machine 7 is shared among all groups.

Extra LAN cables and energy "distributors" are available in each table (in case you want to charge phones or plug your own computers)

Island Group Machine
1 1 1
1 2 2
1 1,2 3
2 3 4
2 3,4 5
2 4 6
3 5 8
3 6 9
3 5,6 10

Ignore the telephones in some of the islands.

Additionally, if you need more cables, ask Andreas, Ayushman or John.

Accounts in the machines

Each machine has already an account with a name like mg# (where # is a number). For example, the machine mg3 already has an account mg3, and the machine mg7 already has an account named mg7 in it. The password for the accounts depends on the number of the machine. It is always like !mg#@123 (where # is a number). For example, in machine mg3 the username and password that you should look for are:

  • Username: mg3
  • Password: !mg3@123

And for machine mg5 the username and password are:

  • Username: mg5
  • Password: !mg5@123

Accessing other machines through ssh

All machines have a ssh_config file that allows easy access to any machine. For example, to access the machine mg3, just do

ssh mg3

Wifi

Name of the Wifi: MindGarage Password for Wifi: !ns!ders@33490809

Contributions to Ovation

DO READ THE CONTRIBUTION GUIDELINES BEFORE STARTING ANYTHING!

They are here.

Things already present in the Computers

After you log into the relevant account in your machine, you will see that the Ovation framework is already set in ~/projects/Ovation. This code was cloned directly from the Ovation repository in https://github.com/mindgarage/Ovation.git. You'll have to change some configurations to be able to use the code there to refer to your own fork (see below).

You will also find a virtual environment in ~/venvs/osa.

All the data we could provide you will be present in /scratch.

Using tensorflow

DO NOT FORGET TO ACTIVATE YOUR VIRTUAL ENVIRONMENT!

That is, you want to run source ~/venvs/osa/activate before anything.

Forking your new repository

This is super easy. Just

  1. log into Github
  2. go to the Ovation repository in Github
  3. in the top right of the screen, click in Fork

Done. Now you'll find a new repository in your account.

Using the repositories already present in the machines

The code present in ~/projects/Ovation was cloned directly from the Ovation repository. But we expect you to create your own fork (see above) in Github and make Pull Requests to the develop branch when you. Therefore, you'll need to add a new repository to the git configuration:

# Change directory to the Ovation code
cd ~/projects/Ovation

# Rename the `origin` repository to your new fork
git remote set-url origin <link-to-your-repository>

The link to your repository is the link you use to clone your repository. It is the link you get when you click in the green button "Clone or download" in the right of the screen in Github when you go to your repository. So, for example, if your username were myuser, it would probably be something like https://github.com/myuser/Ovation. In that case, you'd have to do:

# Rename the `origin` repository to your new fork
git remote set-url origin https://github.com/myuser/Ovation

Before proceeding with your coding, DON'T FORGET TO PULL THE LATEST CHANGES. I.e., do

# Gets the latest version of master
git pull origin master