gnu_radio_benchmark_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 | ||
gnu_radio_benchmark_example [2016/12/12 17:44] – [Submitting the task] onicolas | gnu_radio_benchmark_example [2017/11/15 16:05] – [Inspecting the example task] onicolas | ||
---|---|---|---|
Line 33: | Line 33: | ||
you@srvairlock: | you@srvairlock: | ||
benchmark_rx.py | benchmark_rx.py | ||
- | benchmark_tx.py | + | benchmark_tx.py |
</ | </ | ||
Line 41: | Line 41: | ||
* '' | * '' | ||
* '' | * '' | ||
- | * '' | + | * '' |
Now, let's inspect the scenario description file, to understand what will happen during this experiment: | Now, let's inspect the scenario description file, to understand what will happen during this experiment: | ||
< | < | ||
- | you@srvairlock: | + | you@srvairlock: |
</ | </ | ||
Line 53: | Line 53: | ||
< | < | ||
# | # | ||
- | # All lines starting with "#" | + | # All lines starting with "#" |
# 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 69: | Line 69: | ||
# | # | ||
# | # | ||
- | # | + | # 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 |
+ | |||
+ | | ||
+ | | ||
</ | </ | ||
Line 88: | Line 88: | ||
* '' | * '' | ||
- | * '' | + | * '' |
- | * '' | + | |
* '' | * '' | ||
* '' | * '' | ||
Line 95: | Line 94: | ||
* '' | * '' | ||
* '' | * '' | ||
- | * '' | + | * '' |
Same reasoning follows for the section on node6. So this is the scenario at hand: | Same reasoning follows for the section on node6. So this is the scenario at hand: | ||
Line 140: | Line 139: | ||
you@srvairlock: | you@srvairlock: | ||
</ | </ | ||
+ | |||
+ | (If you're running your reservation in a container reservation): | ||
+ | < | ||
+ | you@srvairlock: | ||
+ | </ | ||
+ | |||
+ | (Be sure that no one else is using the same node as you) | ||
This will run a 30 minute job and open a subshell in which you can run minus tasks. This subshell will be killed after 30 minutes, and if you leave the shell earlier, it will terminate the corresponding oar job. More documentation on oar can be found [[reserve|here]]. You can also monitor the current jobs in the [gantt web interface](http:// | This will run a 30 minute job and open a subshell in which you can run minus tasks. This subshell will be killed after 30 minutes, and if you leave the shell earlier, it will terminate the corresponding oar job. More documentation on oar can be found [[reserve|here]]. You can also monitor the current jobs in the [gantt web interface](http:// | ||
Line 158: | Line 164: | ||
< | < | ||
you@srvairlock: | you@srvairlock: | ||
- | Testbed status: | + | num total tasks: 2540 |
- | ID count so far: 15 | + | num tasks waiting: 0 |
- | Number of awaiting jobs: 0 | + | num tasks running: 0 |
- | ID of the running | + | tasks currently |
+ | | ||
</ | </ | ||
- | Three pieces of information are returned: | + | These information are returned: |
- | * '' | + | * '' |
- | * '' | + | * '' |
- | * '' | + | * '' |
+ | * '' | ||
- | ## Collecting and analysing | + | ## Collecting and analyzing |
- | Generally the OFDM example task will take a few minutes to run. Once its finished, Minus will take care of copying the results and output messages back to your home folder in srvairlock, | + | Generally the OFDM example task will take a few minutes to run. Once it is finished, Minus will take care of copying the results and output messages back to your home folder in srvairlock, |
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. | ||
- | Lets go look for them: | + | Let' |
< | < | ||
Line 197: | Line 206: | ||
you@srvairlock: | you@srvairlock: | ||
benchmark_rx.py | benchmark_rx.py | ||
- | benchmark_tx.py | + | benchmark_tx.py |
receive_path.py | receive_path.py | ||
</ | </ | ||
Line 206: | Line 215: | ||
* '' | * '' | ||
- | Lets take a look inside both, starting with the '' | + | Let' |
< | < | ||
Line 264: | Line 273: | ||
</ | </ | ||
- | Lets try to understand it: | + | Let' |
* The first 9 lines correspond to the UHD messages | * The first 9 lines correspond to the UHD messages | ||
* The next 16 lines correspond to the GNU Radio messages and radio configuration parameters | * The next 16 lines correspond to the GNU Radio messages and radio configuration parameters | ||
* There might be a warning message about realtime scheduling that can be safely ignored | * There might be a warning message about realtime scheduling that can be safely ignored | ||
- | * The lines starting with '' | + | * The lines starting with '' |
* '' | * '' | ||
* '' | * '' | ||
Line 274: | Line 283: | ||
* '' | * '' | ||
- | As it can be seen, there' | + | As can be seen, there' |
You can also look into the stderr.txt: | You can also look into the stderr.txt: |
gnu_radio_benchmark_example.txt · Last modified: 2018/10/24 12:01 by lcardoso