spectrum_analyser_example
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
spectrum_analyser_example [2016/12/13 17:50] – [Book the testbed with OAR] onicolas | spectrum_analyser_example [2017/11/15 16:25] (current) – [Adapt the scenario file] onicolas | ||
---|---|---|---|
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: ./ |
- | | + | passive: true |
- | | + | |
- | node23: | + | |
- | entry sa.py | + | command: ./benchmark_tx.py --antenna=" |
- | | + | |
+ | node23: | ||
+ | | ||
+ | passive: true | ||
</ | </ | ||
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.1481647801.txt.gz · Last modified: 2016/12/13 17:50 by onicolas