cortexlab103
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
cortexlab103 [2018/03/26 15:24] – [Upload the files on airlock] lcardoso | cortexlab103 [2018/03/30 09:58] (current) – [Example scenario] mimbert | ||
---|---|---|---|
Line 17: | Line 17: | ||
| 8 | tuto8 | node 24 | 6670 | | | 8 | tuto8 | node 24 | 6670 | | ||
| 9 | tuto9 | node 28 | 6671 | | | 9 | tuto9 | node 28 | 6671 | | ||
+ | |||
+ | __Henceforth you'll replace <number of group> by the number of your group read in the table above.__ | ||
##Setup | ##Setup | ||
- | The purpose of this tutorial is to receive an ongoing OFDM transmission on a given USRP node. One transmitter node is set up to the whole groupe | + | The purpose of this tutorial is to receive an ongoing OFDM transmission on a given USRP node. One transmitter node is set up for the whole group and each group will control a receiver node. Instead of starting from an empty project, we are going to use the GNU Radio examples for an OFDM transmitter and receiver. We are also going to change the '' |
### Start you virtual FIT/ | ### Start you virtual FIT/ | ||
Line 127: | Line 129: | ||
# Time after which the experiment is forced to stop | # Time after which the experiment is forced to stop | ||
# | # | ||
- | duration: | + | duration: |
# Node list | # Node list | ||
Line 142: | Line 144: | ||
</ | </ | ||
- | This file uses the yaml syntax and is self-documented. | + | This file uses the yaml syntax and is self-documented. |
### Adapting the example scenario | ### Adapting the example scenario | ||
Line 166: | Line 168: | ||
### Upload the files on airlock | ### Upload the files on airlock | ||
- | Upload the tuto\_ofdm directory on Airlock. For example, on Linux, it will look like this (replace <number of group> below by the number of your group): | + | Upload the tuto\_ofdm directory on Airlock. For example, on Linux, it will look like this: |
< | < | ||
cxlbusr@debian-jessie-cortexlab: | cxlbusr@debian-jessie-cortexlab: | ||
cxlbusr@debian-jessie-cortexlab: | cxlbusr@debian-jessie-cortexlab: | ||
</ | </ | ||
+ | |||
+ | Dont forget to replace <number of group> below by the number of your group! | ||
### Create the task | ### Create the task | ||
Line 192: | Line 196: | ||
### Book the testbed with OAR | ### Book the testbed with OAR | ||
- | As explained [[reserve|here]], | + | As explained [[reserve|here]], |
- | A basic example to submit an OAR interactive job requesting all available nodes, for 30 minutes: | + | For the purposes of this tutorial, a shared reservation has been done in advance. This parent reservation' |
- | < | + | To reserve your nodes in the FIT/ |
+ | |||
+ | < | ||
+ | tuto# | ||
+ | </ | ||
+ | |||
+ | More documentation on oar can be found [[reserve|here]]. Among the reservation messages OAR outputs, the system will give you a reservation ' | ||
+ | |||
+ | You can check if the job was properly created as well as monitor the current jobs in the [gantt web interface](http:// | ||
### Submit the task | ### Submit the task | ||
Now, we have booked the testbed and we have a `.task` file containing our experiment. In order to run it, we need to submit it to the testbed scheduler. | Now, we have booked the testbed and we have a `.task` file containing our experiment. In order to run it, we need to submit it to the testbed scheduler. | ||
- | |||
- | For now, the scheduler is a simple FIFO queue, but a more advanced scheduling mechanism will be implemented in upcoming versions of CorteXlab. | ||
To submit a task to the scheduler, use the Minus CLI: | To submit a task to the scheduler, use the Minus CLI: | ||
< | < | ||
- | you@srvairlock: | + | tuto#@srvairlock: |
</ | </ | ||
Line 216: | Line 226: | ||
You can check the status of your experiment through the testbed scheduler. To do so, use the Minus CLI: | You can check the status of your experiment through the testbed scheduler. To do so, use the Minus CLI: | ||
< | < | ||
- | you@srvairlock: | + | tuto#@srvairlock: |
num total tasks: | num total tasks: | ||
num tasks waiting: 0 | num tasks waiting: 0 | ||
Line 226: | Line 236: | ||
The information given by this command enables you to deduce your experiment status. It's quite self-explanatory. | The information given by this command enables you to deduce your experiment status. It's quite self-explanatory. | ||
+ | __Are you having problems with your task? '' | ||
- | Once it's finished (we have set the duration to 2 minutes), Minus will take care of copying the results and output messages back to your home folder in srvairlock, so that you can analyze it. | + | ## Checking the results |
+ | |||
+ | Once it's finished (we have set the duration to 2 minutes), Minus will take care of copying the results and output messages back to your home folder in srvairlock, so that you can analyze it. | ||
+ | |||
+ | __For readability, | ||
All results are stored by task number in the results folder, inside your home folder. | All results are stored by task number in the results folder, inside your home folder. | ||
Line 233: | Line 248: | ||
Go in this folder : | Go in this folder : | ||
< | < | ||
- | you@srvairlock: | + | tuto#@srvairlock: |
- | you@srvairlock: | + | tuto#@srvairlock: |
task_15 | task_15 | ||
- | you@srvairlock: | + | tuto#@srvairlock: |
- | you@srvairlock: | + | tuto#@srvairlock: |
node4.tgz | node4.tgz | ||
</ | </ | ||
Line 244: | Line 259: | ||
< | < | ||
- | you@srvairlock: | + | tuto#@srvairlock: |
- | you@srvairlock: | + | tuto#@srvairlock: |
node4 node4.tgz | node4 node4.tgz | ||
- | you@srvairlock: | + | tuto#@srvairlock: |
- | you@srvairlock: | + | tuto#@srvairlock: |
rx_ofdm.grc | rx_ofdm.grc | ||
rx_ofdm.py | rx_ofdm.py | ||
Line 261: | Line 276: | ||
< | < | ||
- | you@srvairlock: | + | tuto#@srvairlock: |
</ | </ | ||
Line 327: | Line 342: | ||
</ | </ | ||
- | |||
- | ## What's next ? | ||
- | |||
- | We have seen through this tutorial how to run an experiment in CorteXlab starting from a local example on your computer for USRPs. Now you know all the basics in order to run your own experiment in CorteXlab between two USRP nodes. | ||
- | |||
- | Follow on to the [[from_gnuradio_to_cortxlab_pico|next tutorial]], where we will repeat this procedure for the PicoSDR nodes. |
cortexlab103.1522070676.txt.gz · Last modified: 2018/03/26 15:24 by lcardoso