cortexlab103
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
cortexlab103 [2018/03/26 15:56] – [Book the testbed with OAR] lcardoso | cortexlab103 [2018/03/30 09:57] – [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 | + | 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 144: | Line 144: | ||
</ | </ | ||
- | This file uses the yaml syntax and is self-documented. | + | This file uses the yaml syntax and is self-documented. |
+ | |||
+ | Don't forget to change the node number to the node attributed to your group. | ||
### Adapting the example scenario | ### Adapting the example scenario | ||
Line 216: | Line 219: | ||
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 226: | Line 229: | ||
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 235: | Line 238: | ||
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? '' | ||
## Checking the results | ## Checking the results | ||
Line 246: | Line 251: | ||
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 257: | Line 262: | ||
< | < | ||
- | 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 274: | Line 279: | ||
< | < | ||
- | you@srvairlock: | + | tuto#@srvairlock: |
</ | </ | ||
Line 339: | Line 344: | ||
INFO: Parser returned #f | INFO: Parser returned #f | ||
</ | </ | ||
- | |||
cortexlab103.txt · Last modified: 2018/03/30 09:58 by mimbert