Hey Marcus, Thanks for replying.
- I'm aware this is a big and ambitious project, but to me, most of the complexity lies in developing the application window. The signal processing library and OOT modules are definitely significant parts of the project, but I already have solid experience developing with beamforming and DoA estimation algorithms from my work. I've also used GNU Radio extensively, especially with Embedded Python Blocks for quick prototyping. So out of the three main components of the project, I’ve already tackled two before, and I expect those parts to take less time to complete. I haven't exactly developed OOT modules before, but all it takes is a read through the documentation. - Timeline is one of those things I am yet to complete. - Those 4 different visualizations will be part of the plotting lib of the application window. And I am the one who made it, the code is available in repo <https://github.com/Ashborn-SM/GSoC-Proposal/blob/main/plots.ipynb>, including the one at the title page. - I'll try to put in more hours per week. Regards, Rahul On Mon, Apr 7, 2025 at 8:06 PM Marcus Müller <mmuel...@gnuradio.org> wrote: > Hi Rahul! > > Because there's little time to the deadline, a few quick notes: > > - Your project is very big. You sell "a library of DoA estimation > algorithms" as one tiny > gear in the machinery of your overall proposal. If I was to define a GSoC > idea for a > student, that would have been a GSoC proposal on its own. > - You propose a topic not on our ideas list, so we haven't had a chance to > come to an idea > when a certain student should have reached a specific intermediate > objective / milestone. > I've recommended that to other students as well: Please add a weekly / > biweekly breakdown > of what you want to achieve in which time. > We won't be angry when that schedule changes and shifts as you work on > things, but not > starting with a realistically achievable schedule harbors a big risk of > not being able to > finish things. > - Your proposal contains multiple visualizations of radiation patterns > etc. Where do they > come from? If you wrote the code to produce them: very cool! Mention that. > If they're by > someone else: you need to cite them. > - With a project this large in scope and proposed total hours, and with > the uncertainty > that a self-brought topic brings, I'd say it'd be a good idea to not plan > a > low-hours-per-week work schedule for the full grace-period-including 22 > weeks, but instead > aim to work more hours per week, and then have some buffer in the end if > you, for some > reason, needed to take a break. You'll be the one responsible for > *finishing* your > project, after all! > > Best, > Marcus > > On 4/6/25 9:57 PM, rahul pillai wrote: > > Hey, > > > > So, right now I am in a bit of a pickle. Due to personal reasons I > wasn't able to interact > > with the community and properly convey my idea and also I am a bit > behind on my proposal. > > I am confident that I can complete it within April 8 - 18:00 UTC but a > lot of the details > > that I initially wanted to present in the proposal wouldn't be there, I > really hope this > > wouldn't be a problem. > > > > Here's the link to my proposal > https://github.com/Ashborn-SM/GSoC-Proposal <https:// > > github.com/Ashborn-SM/GSoC-Proposal>, the document is located at > _latex>main.pdf._ Please > > note that the proposal is still a work in progress. However, the first > two chapters are > > complete (have to be proof-read), hopefully they will give a clear idea > on what i am > > trying to accomplish. There's also a .ipynb file to prove my coding > capabilities in this > > domain. > > > > Regards, > > Rahul > > >
