User Tools

Site Tools


from_gnuradio_to_cortxlab_pico

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
from_gnuradio_to_cortxlab_pico [2017/02/06 15:15] lcardosofrom_gnuradio_to_cortxlab_pico [2017/08/22 14:18] – migrate from scenario.desc to scenario.yaml mimbert
Line 169: Line 169:
 ## Create the scenario ## Create the scenario
  
-The experiment description file called `scenario.desc` will be looked for and read by the experiment scheduler to get which nodes and what software will be used during the experiment. It also gives the necessary startup scripts and parameters that the user provides for his experiment.+The experiment description file called `scenario.yaml` will be looked for and read by the experiment scheduler to get which nodes and what software will be used during the experiment. It also gives the necessary startup scripts and parameters that the user provides for his experiment.
  
-Here is a simple example of a `scenario.desc` file:+Here is a simple example of a `scenario.yaml` file:
 <code> <code>
 # Example scenario description file # Example scenario description file
Line 180: Line 180:
 # Scenario textual description # Scenario textual description
 #   simple string (a one liner) #   simple string (a one liner)
-desc OFDM tx-rx example scenario for CorteXlab+description: OFDM tx-rx example scenario for CorteXlab
  
 # Experiment maximum duration # Experiment maximum duration
 #   Time after which the experiment is forced to stop #   Time after which the experiment is forced to stop
-#   integer (minutes+#   integer (seconds
-durat 2+duration: 120
  
 # Node list # Node list
Line 191: Line 191:
 #   format: #   format:
 # #
-#   (machine): +#   nodes: 
-  entry (entry point script relative to the task root+#     (machine): 
-#   exit (exit point script relative to the task root. Use "none" for none)+      command: (entry point script relative to the task root)
  
-node29: +nodes: 
-   entry rx_ofdm.py +  node29: 
- +    command: rx_ofdm.py 
-node31: +  node31: 
-   entry tx_ofdm.py+    command: tx_ofdm.py
 </code> </code>
  
-This file uses its own syntax and is self-documented. Here the params line is mandatory even if it is not used (This will be changed in a future version). Adapt this example to suit your needs.+This file uses the yaml syntax and is self-documented. Adapt this example to suit your needs.
  
  
Line 213: Line 213:
 │   ├── tx_ofdm.py │   ├── tx_ofdm.py
 │   ├── rx_ofdm.py │   ├── rx_ofdm.py
-│   ├── scenario.desc+│   ├── scenario.yaml
 │   ├── tx_ofdm.grc │   ├── tx_ofdm.grc
 │   └── rx_ofdm.grc │   └── rx_ofdm.grc
Line 276: Line 276:
 <code> <code>
 you@srvairlock:~$ minus testbed status you@srvairlock:~$ minus testbed status
-Testbed status+num total tasks  2540 
-ID count so far6 +num tasks waiting0 
-Number of awaiting jobs: 0 +num tasks running: 0 
-ID of the running jobNone (None means server is idle)+tasks currently running: 
 +  (none)
 </code> </code>
  
Line 307: Line 308:
 you@srvairlock:~/results/task_15$ cd node29 you@srvairlock:~/results/task_15$ cd node29
 you@srvairlock:~/results/task_15/node29$ ls you@srvairlock:~/results/task_15/node29$ ls
-rx_ofdm.grc  scenario.desc  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
 </code> </code>
from_gnuradio_to_cortxlab_pico.txt · Last modified: 2017/11/15 16:19 by onicolas

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki