Talk:Tutorials: Difference between revisions

From GNU Radio
Jump to navigation Jump to search
No edit summary
(11 intermediate revisions by 5 users not shown)
Line 1: Line 1:
Please leave feedback here, just create a new subsection.
Please leave feedback here, just create a new subsection by clicking the "Add topic" tab above.  You don't even have to log in, although the edit may take a day to get approved.


== Example Feedback ==
== OOTs and C++ ==


Your tutorials suck!
"Out of Tree Modules (OOTs)" and "Writing blocks in C++" clearly have some overlap that needs to be sorted out, if someone wants to tackle that it would be awesome
 
== Types of Blocks ==
 
There should be a new or existing beginner tutorial that includes the different types of blocks, like source/sink/sync/general
 
== Where to Find Example Code ==
 
Throughout the tutorials, it is seemingly possible to build the examples yourself until you get into higher level blocks such as "symbol_sampling.grc" in the QPSK Mod and Demod Tutorial. This text could easily be linked to the .grc file used in the tutorial.
 
* It would also be a very cool feature to have an open repository where people could post their own completed tutorial code, similarly to how Instructables.com allows users to show that they also have made the project and comment on it (example: https://www.instructables.com/Raspberry-Pi-Amateur-Radio-Digital-Clock/)
 
== Tutorial Organization ==
 
Throughout much of the documentation "GNU Radio" and "GRC" are used (conceptually) interchangeably. While GRC is a nifty tool for creating flowgraphs, GNU Radio is the magic behind the individual blocks. For example, when I search <code>gnuradio python hier_block</code>, I get [https://wiki.gnuradio.org/index.php?title=Hier_Blocks_and_Parameters|Hier Blocks and Parameters], which is a tutorial on creating a <code>hier_block</code> using GRC. There is no Python code in the page at all.
 
All the GRC tutorials are great, but when I need a lower-level guide (like a Python API), there is little there.
 
== navigation between sections ==
 
Would be great if I could go to the next section by just following a link at the bottom of the section. Going back to the tutorials main page every time I want to go to a new section is time consuming.

Revision as of 09:25, 18 January 2023

Please leave feedback here, just create a new subsection by clicking the "Add topic" tab above. You don't even have to log in, although the edit may take a day to get approved.

OOTs and C++

"Out of Tree Modules (OOTs)" and "Writing blocks in C++" clearly have some overlap that needs to be sorted out, if someone wants to tackle that it would be awesome

Types of Blocks

There should be a new or existing beginner tutorial that includes the different types of blocks, like source/sink/sync/general

Where to Find Example Code

Throughout the tutorials, it is seemingly possible to build the examples yourself until you get into higher level blocks such as "symbol_sampling.grc" in the QPSK Mod and Demod Tutorial. This text could easily be linked to the .grc file used in the tutorial.

Tutorial Organization

Throughout much of the documentation "GNU Radio" and "GRC" are used (conceptually) interchangeably. While GRC is a nifty tool for creating flowgraphs, GNU Radio is the magic behind the individual blocks. For example, when I search gnuradio python hier_block, I get Blocks and Parameters, which is a tutorial on creating a hier_block using GRC. There is no Python code in the page at all.

All the GRC tutorials are great, but when I need a lower-level guide (like a Python API), there is little there.

navigation between sections

Would be great if I could go to the next section by just following a link at the bottom of the section. Going back to the tutorials main page every time I want to go to a new section is time consuming.