Here you'll find all information regarding the hands on tutorials for the ISP-IoT Winter school.

In order to be able to start, you'll need to verify your system is compliant with the course material. You can proceed by either installing the FIT/CorteXlab toolchain, or downloading our virtual machine image Please refer to the instructions below on how to get your system ready for the tutorial.

All the information needed for the toolchain installation is here

We provide a virtual machine image which contains a ready to use instance of gnuradio, the same version as the one in the FIT/CorteXlab platform.

This VM image is provided in .ova format (open virtualization archive), which theorically makes it runnable on various virtualization software, but we only support virtualbox 5.2 or greater.

Thus, to be able to use this VM, you need to have:

• A computer
• An internet connection to be able to connect to the FIT/CorteXlab platform in particular:
  • We use port 22 for ssh connection
  • The Tutorial will work from anywhere in the world, however launching GNURadio on the CorteXlab server might result in slow execution due to the latency of X window protocol.
• Virtualbox version 5.2 or greater
  • Warning, precedent version of virtual box will probably not work

You can get the VM image from http://xp.cortexlab.fr/downloads/debian-jessie-cortexlab.ova (or on provided usb keys).

Once you have copied the ova to your laptop, follow these steps:

• execute: $ VBoxManage hostonlyif create (this will ensure that additional virtual network interface(s) are created before importing the VM)
• import the ova in virtualbox. Note that if the import fails with error Seeking within the archive failed (VERRTARUNEXPECTED_EOS), this can be a bug of some versions of virtualbox. A solution is then to manually extract the files of the .ova (which is actually a tar) with the following command: $ tar xf debian-jessie-cortexlab.ova. It should then be possible to import the extracted ovf without error.

From there you can start the VM. You can connect to accounts cxlbusr (recommended) or root, without any password. You can also connect to the VM with ssh. The network address to connect to depends on the operating system (use your OS interface managing commands or gui to get the IP address). On Linux, it will most likely be 192.168.56.101, so once the VM is started you should be able to $ ssh cxlbusr@192.168.56.101 or ssh root@192.168.56.101 (change the IP address accordingly, if it's different on your laptop).

You should use the cxlbusr account since the GNU Radio FIT/CorteXlab toolchain is preconfigured in this account (it is installed in /home/cxlbusr/opt/cxlb-toolchain).

The SSH is not configured in this VM, so you will have to install the SSH key linked to your FIT/CorteXlab account

Since we're all going to be using FIT/CorteXlab at the same time, a division of the resources is necessary. This will allow all groups to access the testbed without any conflicts.

First of all, all tutorial attendees will arrange themselves in groups of two (or three, depending on the number of participants). For each group, a list of resources is given at the beginning of each tutorial. If you're unsure of what resources to use, or if you weren't able to find a group, please refer to the tutorial personnel.

In this hands-on tutorial we will introduce the very basics of using FIT/CorteXlab, based on a very simple experiment. The step-by-step guide will introduce you to:

• Accessing the testbed
• Making and managing reservations
• Creating an experiment task
• Submitting the task
• Following the task's execution
• Retrieving the results

The tutorial can be found under this link: FIT/CorteXlab 101

Test your GNU Radio & FIT/CorteXlab skills and have fun here : isp-iot-challenge !

Meanwhile, if you feel that you are not ready yet, you can have a look at some of our cool tutorials

Reminder : Even if a job is running during this winter school, it is deployed as a container mode (more information here) and you can still use the testbed. However, be sure to add the right options while booking nodes.
Here is an example of job reservation with the following options :

• inside the container job n°2018
• duration 30 minutes
• book node 4 and 6

you@srvairlock:~$ oarsub -t inner=2018 -l {"network_address in ('mnode4.cortexlab.fr', 'mnode6.cortexlab.fr')"}/nodes=2,walltime=0:30:00 -I