Re: GSoC Student Introduction

2024-06-01 Thread Marcus Müller

Hey Zaky,

great to have you here! I saw you on chat, and it's really going to be fun learning with 
you! This is a really good time to work on standalone GRC; I'm sure you can always reach 
out to the community and we'll be very interested in helping you!


Best,
Marcus

On 30.05.24 13:23, Zaky Hermawan wrote:
I am Zaky Hermawan, an Electrical Engineering student from Indonesia. I am participating 
in Google Summer of Code with a project titled "GRC: Standalone Application and Pluggable 
Workflows." My work primarily focuses on GRC separation and code generation, I may also 
touch on some GUI code on GRC. I hope my project will significantly benefit the GNU Radio 
community.


You can follow my weekly progress report on https://zakyhermawan.github.io 
 and see the source code on 
https://github.com/ZakyHermawan/gnuradio .


Regards,

Zaky Hermawan




saving script with cpp instead py

2024-06-01 Thread robin ivetic
Hello,

I can't save any script to run as cpp, because block that I'm using 
(gr-osmosdr) not support cpp. Searching I found this 
example, need to turn flag 
cpp and alo include cpp_template, means that I need to compile from the source, 
but than I realize that almost all hardware sink/wrappers and sources blocks 
inside gnuradio installed from package, don't offer also cpp support.
[https://opengraph.githubassets.com/b497b3ebddd9aa5aff8351f67115a25df926544b97524db74f0119557cd5eb37/gnuradio/gnuradio/issues/2297]
Add C++ generation support in GRC to all blocks · Issue #2297 · 
gnuradio/gnuradio
The checklists below indicate which blocks have C++ support in master. 
gr-analog 25/34 ✔️ analog_agc2_xx analog_agc3_xx analog_agc_xx 
analog_am_demod_cf analog_const_source_x analog_cpfsk_bc analog...
github.com

Now I don't know if I need to turn this feature on the gnuradio level, when I'm 
compiling or just block per block, and if second option true, what would be 
correct procedure to include cpp saving script when compiling gr-osmosdr.

Robin


GRC separation and workflow modularization weekly update

2024-06-01 Thread Zaky Hermawan
Hi GNU Radio folks,

There is a little bit of adjustment on the project from my initial
proposal, the option block modularization and workflow separation will be
done first, before the grc separation.

There are three major highlights of the first week:
1. Option block modularization is finished, now the option block is already
converted/implemented in python, this will enable grc to read and store
information about code generations from workflow files, instead of being
hard coded.
2. The workflow separation is also finished, now you can define your own
workflow by making your own template, code generation class, and workflow
YAML file and put them in the grc/workflows folder.
3. I am also already creating the tests, which consist of 9 GRC files, one
for each workflow. The test code is in test_generator.py.

I probably need to do some cleanup first, deleting some useless stuff from
the code base before moving on to the next big milestone (GRC Separation).

You can read the full progress report on my week 1 progress report

.

Regards,

Zaky