Editing GSoCIdeas

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
Note- also check out [[Grant Ideas]] for additional ideas that are more suited towards grant money than GSoC.
 
 
 
== Summer of Code 2021: Project ideas list ==
 
== Summer of Code 2021: Project ideas list ==
  
Line 47: Line 45:
  
 
* Familiarity with QT is essential.
 
* Familiarity with QT is essential.
* Widgets are written in C++, so some C++ knowledge is also required.
+
* Widgets are written in C+'', so some C''+ knowledge is also required.
 
* Python skills are highly useful.
 
* Python skills are highly useful.
  
Line 53: Line 51:
  
 
Andrej Rode
 
Andrej Rode
 +
  
 
=== Standardized High Throughput FEC Codes ===
 
=== Standardized High Throughput FEC Codes ===
Line 110: Line 109:
 
To facilitate development of a more modern GNU Radio runtime and scheduler, we need a tool to measure its performance (in terms of delay and throughput). This data is required to compare alternate approaches and to become aware of performance regressions early in the process.
 
To facilitate development of a more modern GNU Radio runtime and scheduler, we need a tool to measure its performance (in terms of delay and throughput). This data is required to compare alternate approaches and to become aware of performance regressions early in the process.
  
The goal of the project is to provide a tool to benchmark the GNU Radio runtime. Since we are interested in the performance on many platforms and architectures, it should provide an option to submit performance data to our server, allowing us to crowdsource data. (Similar to our online stats for SIMD performance.)
+
The goal of the project is to provide a tool to benchmark the GNU Radio runtime. Since we are interested in the performance on many platforms and architectures, it should provide an option to submit performance data to our sever, allowing us to crowdsource data. (Similar to our online stats for SIMD performance.)
  
 
'''Outcome'''
 
'''Outcome'''
Line 116: Line 115:
 
* Come up with interesting metrics and, if needed, implement blocks to extract them.
 
* Come up with interesting metrics and, if needed, implement blocks to extract them.
 
* Come up with interesting flowgraph topologies that should be benchmarked.
 
* Come up with interesting flowgraph topologies that should be benchmarked.
* Set up automated experiments that iterate over a given parameter space (repetitions, number of samples, size of the flowgraph).
+
* Setup automated experiments that iterate over a given parameter space (repetitions, number of samples, size of the flowgraph).
 
* Parse, evaluate, and visualize the data.
 
* Parse, evaluate, and visualize the data.
* Add an option to upload the performance data to our web server.
+
* Add an option to upload the performance data to our web sever.
  
 
'''Prerequisites'''
 
'''Prerequisites'''

Please note that all contributions to GNU Radio are considered to be released under the Creative Commons Attribution-ShareAlike (see GNU Radio:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)