User Tools

Site Tools


cortexlab103

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
cortexlab103 [2018/03/26 15:48] – [Observe the result] lcardosocortexlab103 [2018/03/30 09:58] (current) – [Example scenario] mimbert
Line 22: Line 22:
 ##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 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 ''channel estimation'' block such that it produces frequency channel estimations able to be seen in the fft-web interface.+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 ''channel estimation'' block such that it produces frequency channel estimations that can be seen in the fft-web interface.
  
 ### Start you virtual FIT/CorteXlab work environment ### Start you virtual FIT/CorteXlab work environment
Line 144: Line 144:
 </code> </code>
  
-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 200: Line 200:
 For the purposes of this tutorial, a shared reservation has been done in advance. This parent reservation's 'id' will be given to you by the tutorial instructors. We will need to create a child reservation inside of the parent one. For the purposes of this tutorial, a shared reservation has been done in advance. This parent reservation's 'id' will be given to you by the tutorial instructors. We will need to create a child reservation inside of the parent one.
  
-To reserve your nodes in the FIT/CorteXlab room, use this following command. Please replace ''mnode4'' and ''mnode6'' with the node numbers assigned to your group. Bear in mind that the preceding letter 'm' should be kept! Also, replace the ''<id of container>'' by the number of the parent reservation.+To reserve your nodes in the FIT/CorteXlab room, use this following command. Please replace ''mnode4'' with the node number assigned to your group. Bear in mind that the preceding letter 'm' should be kept! Also, replace the ''<id of container>'' by the number of the parent reservation.
  
 <code> <code>
-tuto#@srvairlock:~/examples$ oarsub -t inner=<id of container> -l {"network_address in ('mnode4.cortexlab.fr', 'mnode6.cortexlab.fr')"}/nodes=2,walltime=1:00:00 -I+tuto#@srvairlock:~/examples$ oarsub -t inner=<id of container> -l {"network_address in ('mnode4.cortexlab.fr')"}/nodes=1,walltime=1:00:00 -I
 </code> </code>
  
Line 216: Line 216:
 To submit a task to the scheduler, use the Minus CLI: To submit a task to the scheduler, use the Minus CLI:
 <code> <code>
-you@srvairlock:~$ minus task submit tuto_ofdm.task+tuto#@srvairlock:~$ minus task submit tuto_ofdm.task
 </code> </code>
  
Line 226: 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:
 <code> <code>
-you@srvairlock:~$ minus testbed status+tuto#@srvairlock:~$ minus testbed status
 num total tasks:   2540 num total tasks:   2540
 num tasks waiting: 0 num tasks waiting: 0
Line 236: 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.
  
-### Checking the results+__Are you having problems with your task? ''minus log'' might help you debug your scenario and GNU Radio problems.__
  
-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 examples below consider task 15 with nodes node4 and node6. Please consider the values assigned to your group in the following.__
  
 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 244: Line 248:
 Go in this folder : Go in this folder :
 <code> <code>
-you@srvairlock:~/tuto_ofdm$ cd ~/results +tuto#@srvairlock:~/tuto_ofdm$ cd ~/results 
-you@srvairlock:~/results$ ls+tuto#@srvairlock:~/results$ ls
 task_15 task_15
-you@srvairlock:~/results$ cd task_15 +tuto#@srvairlock:~/results$ cd task_15 
-you@srvairlock:~/results/task_15$ ls+tuto#@srvairlock:~/results/task_15$ ls
 node4.tgz  node6.tgz node4.tgz  node6.tgz
 </code> </code>
Line 255: Line 259:
  
 <code> <code>
-you@srvairlock:~/results/task_15$ tar -zxf node4.tgz +tuto#@srvairlock:~/results/task_15$ tar -zxf node4.tgz 
-you@srvairlock:~/results/task_15$ ls +tuto#@srvairlock:~/results/task_15$ ls 
 node4  node4.tgz  node6.tgz node4  node4.tgz  node6.tgz
-you@srvairlock:~/results/task_15$ cd node4 +tuto#@srvairlock:~/results/task_15$ cd node4 
-you@srvairlock:~/results/task_15/node4$ ls+tuto#@srvairlock:~/results/task_15/node4$ ls
 rx_ofdm.grc  scenario.yaml  stdout.txt   tx_ofdm.py rx_ofdm.grc  scenario.yaml  stdout.txt   tx_ofdm.py
 rx_ofdm.py   stderr.txt     tx_ofdm.grc rx_ofdm.py   stderr.txt     tx_ofdm.grc
Line 272: Line 276:
  
 <code> <code>
-you@srvairlock:~/results/task_15/node4$ less stdout.txt+tuto#@srvairlock:~/results/task_15/node4$ less stdout.txt
 </code> </code>
  
Line 337: Line 341:
 INFO: Parser returned #f INFO: Parser returned #f
 </code> </code>
- 
  
cortexlab103.1522072095.txt.gz · Last modified: 2018/03/26 15:48 by lcardoso

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki