Differences

This shows you the differences between two versions of the page.

--- sharing_the_testbed_with_other_users [2017/12/08 12:05] – lcardoso
+++ sharing_the_testbed_with_other_users [2017/12/08 12:12] (current) – lcardoso
@@ Line 5: / Line 5: @@
 ## Why would you want to do this?
-While CorteXlab was made to allow a single user to operate the testbed at a time, mainly to avoid harmful interference to the experimenter, a few situations might require the sharing of the testbed:
+While CorteXlab was made to allow a single user to operate the testbed at a time, mainly to avoid harmful interference to the experimenter, a few situations might require sharing the testbed:
-  - **GNU Radio or digital communications courses.** For teachers all over the world who would like to use CorteXlab as a teaching platform, using it for practical sessions with their students, sharing CorteXlab is the only way to go. If this is what you want to do, pay attention to the number of radio platforms and the number of students who will use them! Also, pay attention to the interference among students if transmissions are necessary (i.e., choose different frequencies for each student/group).
+  - **GNU Radio or wireless communications courses.** For teachers all over the world who would like to use CorteXlab as a teaching platform, using it for practical sessions with their students, sharing CorteXlab is the only way to go. If this is what you want to do, pay attention to the number of radio platforms and the number of students who will use them! Also, pay attention to the interference among students if transmissions are necessary (i.e., choose different frequencies for each student/group).
   - **Radio challenges.** One interesting use of CorteXlab is to enable radio challenges to be carried out, where several competing groups might need to hack an ongoing communication, decode an  unknown signal, or exploit spectrum holes to transmit. In this case the only way to allow simultaneous usage of the experimentation room is to enable sharing.
 It is important to know that while sharing, there are no guarantees on interference in the room.
+## Reserving the testbed
+First, we need to reserve the CorteXlab room for the shared session. If you're teaching a course or if you're hosting a challenge, in order to guarantee the testbed will be free when you need, the best thing to do is to reserve it prior to the date of usage:
+<code>
+you@srvairlock:~/examples$ oarsub -l nodes=BEST,walltime=4:00:00 -t container -r '2018-07-21 14:00:00'
+</code>
+Beware that the //walltime// parameter has to span the whole session.
 ## Logging into the SSH front-end