spectrum_analyser_example
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
spectrum_analyser_example [2016/12/13 17:47] – [Upload your files on airlock] onicolas | spectrum_analyser_example [2017/10/13 09:20] – [Setup] lcardoso | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | # Spectrum | + | # Spectrum |
Sometimes you want to know what's happening in the testbed, and for this you need a spectrum analyzer. Luckily we have done almost all the work for this, thanks to [[fftweb|FFT web]] (all the technical details are explained in the link). | Sometimes you want to know what's happening in the testbed, and for this you need a spectrum analyzer. Luckily we have done almost all the work for this, thanks to [[fftweb|FFT web]] (all the technical details are explained in the link). | ||
Line 17: | Line 17: | ||
Duplicate the folder my\_task and rename it as ofdm-sa : | Duplicate the folder my\_task and rename it as ofdm-sa : | ||
< | < | ||
- | you@yourpc: | + | you@yourpc: |
you@yourpc: | you@yourpc: | ||
</ | </ | ||
Line 39: | Line 39: | ||
We need to adapt the scenario file to include the spectrum analyzer. We are using nodes 4 and 6 to do the OFDM transmission, | We need to adapt the scenario file to include the spectrum analyzer. We are using nodes 4 and 6 to do the OFDM transmission, | ||
- | Edit '' | + | Edit '' |
< | < | ||
# | # | ||
Line 47: | Line 47: | ||
# Scenario textual description | # Scenario textual description | ||
# | # | ||
- | desc base scenario for CorteXlab | + | description: |
# Experiment maximum duration | # Experiment maximum duration | ||
# Time after which the experiment is forced to stop | # Time after which the experiment is forced to stop | ||
- | # | + | # |
- | durat 5 | + | duration: 300 |
# Node list | # Node list | ||
Line 58: | Line 58: | ||
# | # | ||
# | # | ||
- | # | + | # nodes: |
- | # entry (entry point script relative to the task root) | + | # (machine): |
- | # exit (exit point script relative to the task root. Use " | + | # command: |
- | node4: | + | nodes: |
- | entry benchmark_rx.py | + | |
- | | + | |
- | | + | |
- | node6: | + | node4: |
- | entry benchmark_tx.py | + | command: benchmark_rx.py --antenna=" |
- | | + | passive: true |
- | | + | |
- | node23: | + | |
- | entry sa.py | + | command: |
- | | + | |
+ | node23: | ||
+ | | ||
+ | passive: true | ||
</ | </ | ||
Line 94: | Line 94: | ||
### Create the task | ### Create the task | ||
- | Connect to Airlock through ssh as it is describe | + | Connect to Airlock through ssh as described |
< | < | ||
you@yourpc: | you@yourpc: | ||
</ | </ | ||
- | You can find in your home directory the ofdm-sa | + | You can find in your home directory the ofdm-sa previously |
Now, use the Minus CLI to create the task file: | Now, use the Minus CLI to create the task file: | ||
Line 106: | Line 106: | ||
</ | </ | ||
- | The success (or failure) of the creation will be printed on screen. The task file will be created at the same level and name than the targeted experiment folder but with a `.task` suffix, in our case '' | + | The success (or failure) of the creation will be printed on screen. The task file will be created at the same level and with the same name as the targeted experiment folder but with a `.task` suffix, in our case '' |
**Note:** You can get help on the Minus CLI at anytime with `minus -h` | **Note:** You can get help on the Minus CLI at anytime with `minus -h` | ||
Line 113: | Line 113: | ||
### Book the testbed with OAR | ### Book the testbed with OAR | ||
- | As it is explain [[reserve|here]], | + | As explain [[reserve|here]], |
A basic example to submit an OAR interactive job requesting all available nodes, for 30 minutes: | A basic example to submit an OAR interactive job requesting all available nodes, for 30 minutes: | ||
Line 123: | Line 123: | ||
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 next versions of CorteXlab. | + | For now, the scheduler is a simple FIFO queue, but a more advanced scheduling mechanism will be implemented in upcoming |
To submit a task to the scheduler, use the Minus CLI: | To submit a task to the scheduler, use the Minus CLI: | ||
Line 134: | Line 134: | ||
### Observe the result | ### Observe the result | ||
- | Go back to web page where we created the graph. Around twenty seconds after launching the experiment the graph should start to animate with the result and you can oberve | + | Go back to the web page where we created the graph. Around twenty seconds after launching the experiment the graph should start to animate with the result and you can observe |
## What's next | ## What's next | ||
- | You can try to put several spectrum | + | You can try to put several spectrum |
- | You can also put the '' | + | You can also put the '' |
spectrum_analyser_example.txt · Last modified: 2017/11/15 16:25 by onicolas