CorteXlab's Wiki

User Tools

Site Tools

Trace:
spectrum_analyser_example

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
spectrum_analyser_example [2016/12/13 17:49] – [Create the task] onicolasspectrum_analyser_example [2017/11/15 16:25] (current) – [Adapt the scenario file] onicolas
Line 1: Line 1:
-# Spectrum analyser example+# Spectrum analyzer example
  
 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 :
 <code>  <code> 
-you@yourpc:~/examples $ cp -f my_task/ ofdm-sa/+you@yourpc:~/examples $ cp -r my_task/ ofdm-sa/
 you@yourpc:~/examples $ cd ofdm-sa you@yourpc:~/examples $ cd ofdm-sa
 </code> </code>
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, and if we look at the {{exp_room_with_nodes_positions.png?linkonly|Nodes Placement Map}}, we see that for example node 23 is a good candidate to execute the spectrum analyzer script. We need to adapt the scenario file to include the spectrum analyzer. We are using nodes 4 and 6 to do the OFDM transmission, and if we look at the {{exp_room_with_nodes_positions.png?linkonly|Nodes Placement Map}}, we see that for example node 23 is a good candidate to execute the spectrum analyzer script.
  
-Edit ''scenario.desc'' to add the node 23 with 'sa.py' as the entry point. Also increase the number of packets sent by node 6 (option -M). Your file should look like this :+Edit ''scenario.yaml'' to add the node 23 with 'sa.py' as the entry point. Also increase the number of packets sent by node 6 (option -M). Your file should look like this :
 <code># Example scenario description file <code># Example scenario description file
 # #
Line 47: Line 47:
 # Scenario textual description # Scenario textual description
 #   simple string (a one liner) #   simple string (a one liner)
-desc base scenario for CorteXlab+description: fft-web test
  
 # 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 5+duration: 300
  
 # Node list # Node list
Line 58: Line 58:
 #   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)
  
-node4: +nodes:
-   entry benchmark_rx.py +
-   params --antenna="TX/RX" --rx-gain=25 -v -W 2M -f 2.49G +
-   passive true+
  
-node6: +  node4: 
-   entry benchmark_tx.py +    command: ./benchmark_rx.py --antenna="TX/RX" --rx-gain=25 -v -W 2M -f 2.49G 
-   params --antenna="TX/RX" --tx-amplitude=0.2 -v -W 2M -f 2.49G -M 10 +    passive: true 
-    +     
-node23: +  node6: 
-   entry sa.py +   command: ./benchmark_tx.py --antenna="TX/RX" --tx-amplitude=0.2 -v -W 2M -f 2.49G -M 10 
-   passive true+ 
 +  node23: 
 +    command: ./sa.py 
 +    passive: true
 </code> </code>
  
Line 113: Line 113:
 ### Book the testbed with OAR ### Book the testbed with OAR
  
-As it is explain [[reserve|here]], we need to book the testbed with OAR in order to run our experiment. Once you have booked the platform, you will be the exclusive user of the testbed, avoiding experimentation interference.+As explain [[reserve|here]], we need to book the testbed with OAR in order to run our experiment. Once you have booked the platform, you will be the exclusive user of the testbed, avoiding experimentation interference.
  
 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 versions of CorteXlab.
  
 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 a graph describing an OFDM transmission which should look like this :{{ :ofdm-sa.png?direct&200 |}}+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 a graph representing an OFDM transmission which should look like this :{{ :ofdm-sa.png?direct&600 |}}
  
  
 ## What's next ## What's next
  
-You can try to put several spectrum analyser within the testbed on differents nodes in order to see how the signal strength spread. +You can try to put several spectrum analyzers within the testbed on different nodes in order to see how the signal strength spreads. 
  
-You can also put the ''fft web'' block directly in your receiver node if you don't want to use another node.+You can also put the ''FFT Web'' block directly in your receiver node if you don't want to use another node.
spectrum_analyser_example.1481647759.txt.gz · Last modified: by onicolas
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki