[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog Post Update

[swapnil negi]

Hello everyone, the final blog
<https://grmodtool.wordpress.com/2018/08/04/week-12-add-api-support-to-the-gui/>
post for the website <https://grmodtool.wordpress.com/> has been updated.
GSoC'18 was an ultra awesome experience.
Thank You!



Regards
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog Post Update

[swapnil negi]

Hello everyone, the blog
<https://grmodtool.wordpress.com/2018/07/28/week-11-updated-gui/> post for
the week 11 has been updated with the tasks for the upcoming week.




Regards
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog Post Update

[swapnil negi]

Hello everyone, the blog
<https://grmodtool.wordpress.com/2018/07/21/week-10-mock-gui/> post for the
week 10 has been updated with the tasks for the upcoming week. The GitHub
project <https://github.com/swap-nil7/gnuradio/projects/1> has also been
updated.




Regards
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog Post Update

[swapnil negi]

Hello everyone, the blog
<https://grmodtool.wordpress.com/2018/07/14/week-9-xml-to-yaml-converter/> post
for the week 9 has been updated with the tasks for the upcoming week. The
GitHub project <https://github.com/swap-nil7/gnuradio/projects/1> has also
been updated.



Regards
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog Post

[swapnil negi]

Hello everyone, the blog
<https://grmodtool.wordpress.com/2018/07/06/week-8-add-yaml-generator/> post
for the week 8 has been updated with the tasks for the upcoming week. The
GitHub project <https://github.com/swap-nil7/gnuradio/projects/1> has also
been updated.




Regards
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Change in the base branch

[swapnil negi]

Hello everyone, the base branch of the project, *gr-modtool overhaul*, has
been changed from *python3* to *next* and now the working branch in the
forked repository is swapnil_next
<https://github.com/swap-nil7/gnuradio/tree/swapnil_next>.



Regards
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog Post Update

[swapnil negi]

Hello everyone, the blog
<https://grmodtool.wordpress.com/2018/06/30/week-7-logger-colors-and-pylint-tests/>
post
for the week 7 has been updated with the tasks for the upcoming week. The
GitHub project <https://github.com/swap-nil7/gnuradio/projects/1> has also
been updated.




Regards
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog Update

[swapnil negi]

Hello everyone, the blog
 post
for the week 6 has been updated with the tasks for the upcoming week. The
GitHub project  has also
been updated.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog Post for the Week

[swapnil negi]

Hello everyone, the blog
<https://grmodtool.wordpress.com/2018/06/16/week-5-expose-api-and-api-tests/>
 post for the week 5 has been updated with the tasks for the upcoming week.
Here <https://github.com/swap-nil7/gnuradio/projects/1> is the link to the
updated Github project.




Thank You
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog Post for the week

[swapnil negi]

Hello everyone, the blog
<https://grmodtool.wordpress.com/2018/06/09/week-4-core-cli-split/> post
for the week 4 has been updated with the tasks for the upcoming week. Here
<https://github.com/swap-nil7/gnuradio/projects/1> is the link to the
updated Github project.



Thanks,
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoc18] gr-modtool overhaul: Blog Update for the week

[swapnil negi]

Hello everyone, the blog
<https://grmodtool.wordpress.com/2018/06/02/week-3-enhancement-documentation-separation-of-modules-started/>
post for the week 3 has been updated with the tasks for the upcoming week.
Here <https://github.com/swap-nil7/gnuradio/projects/1> is the link to the
updated Github project.
The week was really a learning experience.



Thanks,
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog Update

[swapnil negi]

Hello everyone,
I have updated the blog
<https://grmodtool.wordpress.com/2018/05/26/week-2-plug-in-architecture-for-modtool/>
for the Week 2 updates and the tasks for week 3. Here
<https://github.com/swap-nil7/gnuradio/projects/1> is the link to the
updated Github project.
There were several errors and hindrances, so this week was highly learning
experience.



Thanks,
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog update

[swapnil negi]

Hello everyone,
I have updated the blog
<https://grmodtool.wordpress.com/2018/05/19/week-1-move-from-argparse-to-click/>
for the Week 1 updates and the tasks for week 2. Here
<https://github.com/swap-nil7/gnuradio/projects/1> is the link to the
updated Github project.
The coding period is really fun.


Thanks,
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul: Blog updates

[swapnil negi]

Hi everyone,
I have updated the blog <https://grmodtool.wordpress.com/> for the Week 0
updates and the tasks for week 1. Here
<https://github.com/swap-nil7/gnuradio/projects/1> is the link to the
project with week 1 milestones.

I am highly excited about the coding period. Please help me out with this
issue <https://github.com/gnuradio/gnuradio/issues/1771> regarding the
compilation error of GNU Radio.



Thanks,
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC18] gr-modtool overhaul

[swapnil negi]

Hi everyone,
I have created a blog <https://grmodtool.wordpress.com/> for updating the
progress and the milestones of the GSoC'18 project *gr-modtool overhaul. *The
blog will be posted every Saturday to maintain thorough transparency of the
project. The next blog will contain the updated timeline for the upcoming
weeks and the milestones for the first week of the coding period.
For viewing the exact code, you can go through my forked repository
<https://github.com/swap-nil7/gnuradio/branches> of the gnuradio project. I
have also created a project
<https://github.com/swap-nil7/gnuradio/projects>with
major tasks on the to-do list. The to-do list will be further modified for
finer details after discussion with the mentors.

I am highly excited to work on this project. So, if you have any queries or
suggestions on the project, please update us on the mailing list or
create issues on the forked repository.


Thanks,
Swapnil Negi
Indian Institute of Technology Roorkee
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [GSoC18] Student projects announced!

[swapnil negi]

Hello everyone,
I really look forward to doing some awesome work with GNU Radio this
summer. And yes, I'll be posting the weekly blogs about the status of the
project in contrast to the specified deadline. I will also remain in
frequent touch with the mentors throughout the program.

Thank you, everyone, for your constant support throughout the selection
procedure.

Congratulations Luca for second consecutive GSoC with GNU Radio!



Regards,
Swapnil Negi
Indian Institute of Technology Roorkee


On Wed, Apr 25, 2018 at 9:43 PM, Ben Hilburn  wrote:

> Congratulations, Swapnil and Luca! I'm really excited about your topics,
> and look forward to seeing your work over the Summer.
>
> Good luck, have fun, and happy hacking =)
>
> Cheers,
> Ben
>
> On Tue, Apr 24, 2018 at 7:43 AM, Nicolas Cuervo 
> wrote:
>
>> Hi all!
>>
>> congratulations to Luca and Swapnil for being accepted for this year's
>> GSoC! Both had very good proposals but also have been active in the
>> community which is fantastic.
>>
>> I am very excited to be part of the mentors this year. I'm looking
>> forward working with Swapnil on this project :)
>>
>> All in all, thanks to all the other candidates that didn't make it this
>> year into GSoC. But if you are reading, we do thank your interest and hope
>> to see you around next year or, even better, to see that you are interested
>> in contributing to the project along the way!
>>
>> Cheers!
>> - Nicolas
>>
>>
>>
>>
>>
>>
>> On Tue, Apr 24, 2018 at 12:41 PM, Moritz Luca Schmid <
>> luca.moritz.sch...@gmail.com> wrote:
>>
>>> Hi everyone,
>>>
>>> I am really excited to work on a great GSoC project, again with GNU
>>> Radio, in the upcoming summer and I hope that
>>> my work will be a nice extension to the GNU Radio project.
>>>
>>> Thanks in advance to Marcus Müller and Felix Wunsch for mentoring me
>>> during GSoC.
>>> I am really looking forward to communicate and shape this project with
>>> you.
>>>
>>> Also, congratulations to Swapnil for the selection in GSoC! I wish you
>>> all the best for your respective tasks.
>>>
>>> As Felix mentioned, I am going to keep you all up to date by weekly
>>> posts about the current state of my project.
>>> Therefore, I am going to launch a blog in the next few days.
>>>
>>> Best
>>> Luca
>>>
>>>
>>> On 23.04.2018 19:26, Felix Wunsch wrote:
>>>
>>>> Hi all,
>>>>
>>>> an hour ago, Google has announced the accepted students for this year's
>>>> Google Summer of Code and we are happy to have two of them working on
>>>> GNU Radio! Swapnil Negi will improve gr-modtool, and Luca Schmid, who
>>>> some of you surely know from last year's GSoC or GRCon17, will bring
>>>> basic MIMO functionality to GNU Radio.
>>>>
>>>> Both of them will provide weekly updates on their progress, so please
>>>> support them by welcoming them in the community and contributing to
>>>> discussions about their projects!
>>>>
>>>> Swapnil and Luca, I'm really excited to work with you and looking
>>>> forward to the improvements you will bring to GNU Radio!
>>>>
>>>> Cheers,
>>>> Felix
>>>>
>>>>
>>>
>>> ___
>>> Discuss-gnuradio mailing list
>>> Discuss-gnuradio@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] gr-modtool overhaul: Proposal draft

[swapnil negi]

Hello everyone,
A brief clarification regarding GitLab profile: We use our own GitLab
hosted in our own local server.
Thanks!

Regards,
Swapnil Negi
Indian Institute of Technology Roorkee

On Tue, 27 Mar 2018, 01:57 swapnil negi,  wrote:

> Hello everyone, I have incorporated the changes mentioned by Nicolas.
> Regarding GitLab profile: As per my group's policy, the code has not been
> made open source. Hence, due to the copyright issues, the code cannot be
> published in the proposal.
>
> Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
> Code Link: https://github.com/swap-nil7/GSoC-Proposal
>
> Regards,
> Swapnil Negi
> Indian Institute of Technology Roorkee
>
> On Mon, Mar 26, 2018 at 6:41 PM, Nicolas Cuervo 
> wrote:
>
>> Hello Swapnil,
>>
>> thanks for updating your draft! I'm really excited about your
>> application. Please don't forget to officially apply and upload your
>> proposal through the program website.
>>
>> I have very, very small comments in regard of code practices,
>>
>>- Keep in mind the coding guidelines in all your code snippets.
>>- Having the functional programming as an objective, keep in mind the
>>correct syntax is used in your functions and methods. For example: the
>>__import__() function used in your plugin loader will work just fine, but
>>this usage is recommended for the interpreter. For implementations as the
>>one you are proposing, import_module() should be used (unless you are
>>expecting to load a package).
>>- Your string formatting uses the old convention. I suggest having a
>>look at 'str'.format()
>>
>> Additionally, you mention in your background that you work regularly in
>> GitLab, but you shared your Github profile instead. Do you have code in
>> there that is not in your Github profile? If so, would you mind adding a
>> link to your GitLab profile?
>>
>> All in all, I think that your proposal is well structured, and the
>> examples that you provide on how to deal with the problem at hand are on
>> point. My comments are being very picky ;) but that's because the rest of
>> your proposal seems ready! Again, dont forget to officially apply and
>> upload your proposal.
>>
>> Cheers,
>> - Nicolas
>>
>> On Sun, Mar 25, 2018 at 10:53 PM, swapnil negi 
>> wrote:
>>
>>> Hello everyone,
>>> I have incorporated all the mentioned improvements to the best of my
>>> knowledge. Please review the *almost final* draft of the proposal.
>>> Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
>>> Code Link: https://github.com/swap-nil7/GSoC-Proposal
>>> Thank you!
>>>
>>> Regards,
>>> Swapnil Negi
>>> Indian Institute of Technology Roorkee
>>>
>>>
>>> On Sun, Mar 25, 2018 at 4:55 PM, swapnil negi 
>>> wrote:
>>>
>>>> Hello everyone,
>>>> Thanks for the detailed review.
>>>> I have made changes to my proposal to incorporate review/merge cycle,
>>>> build Python API for the modtool, briefly explain the UI enhancements and
>>>> fix typos.
>>>> I am still quite unsure about the automated testing part. But as of
>>>> now, thorough testing will be done locally.
>>>> Please review the updated version of my proposal.
>>>> Thanks! :)
>>>> Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
>>>> Code Link: https://github.com/swap-nil7/GSoC-Proposal
>>>>
>>>> On Tue, Mar 20, 2018 at 12:33 AM, swapnil negi <
>>>> swapnil.neg...@gmail.com> wrote:
>>>>
>>>>> Hello everyone!
>>>>> I have uploaded my proposal to the GitHub pages. So, please review and
>>>>> provide me suggestions to improve the same.
>>>>> Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
>>>>> Code Link: https://github.com/swap-nil7/GSoC-Proposal
>>>>> Thank You!
>>>>>
>>>>> Regards,
>>>>> Swapnil Negi
>>>>> Indian Institute of Technology Roorkee
>>>>> India
>>>>>
>>>>>
>>>>> On Sat, Mar 17, 2018 at 3:09 AM, swapnil negi <
>>>>> swapnil.neg...@gmail.com> wrote:
>>>>>
>>>>>> Hi Nicoloas!
>>>>>> Thanks for your valuable response.
>>>>>> Regarding Python compatibility - I will work upon version independent
>>>>>> compatibility using informat

Re: [Discuss-gnuradio] gr-modtool overhaul: Proposal draft

[swapnil negi]

Hello everyone, I have incorporated the changes mentioned by Nicolas.
Regarding GitLab profile: As per my group's policy, the code has not been
made open source. Hence, due to the copyright issues, the code cannot be
published in the proposal.

Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
Code Link: https://github.com/swap-nil7/GSoC-Proposal

Regards,
Swapnil Negi
Indian Institute of Technology Roorkee

On Mon, Mar 26, 2018 at 6:41 PM, Nicolas Cuervo 
wrote:

> Hello Swapnil,
>
> thanks for updating your draft! I'm really excited about your application.
> Please don't forget to officially apply and upload your proposal through
> the program website.
>
> I have very, very small comments in regard of code practices,
>
>- Keep in mind the coding guidelines in all your code snippets.
>- Having the functional programming as an objective, keep in mind the
>correct syntax is used in your functions and methods. For example: the
>__import__() function used in your plugin loader will work just fine, but
>this usage is recommended for the interpreter. For implementations as the
>one you are proposing, import_module() should be used (unless you are
>expecting to load a package).
>- Your string formatting uses the old convention. I suggest having a
>look at 'str'.format()
>
> Additionally, you mention in your background that you work regularly in
> GitLab, but you shared your Github profile instead. Do you have code in
> there that is not in your Github profile? If so, would you mind adding a
> link to your GitLab profile?
>
> All in all, I think that your proposal is well structured, and the
> examples that you provide on how to deal with the problem at hand are on
> point. My comments are being very picky ;) but that's because the rest of
> your proposal seems ready! Again, dont forget to officially apply and
> upload your proposal.
>
> Cheers,
> - Nicolas
>
> On Sun, Mar 25, 2018 at 10:53 PM, swapnil negi 
> wrote:
>
>> Hello everyone,
>> I have incorporated all the mentioned improvements to the best of my
>> knowledge. Please review the *almost final* draft of the proposal.
>> Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
>> Code Link: https://github.com/swap-nil7/GSoC-Proposal
>> Thank you!
>>
>> Regards,
>> Swapnil Negi
>> Indian Institute of Technology Roorkee
>>
>>
>> On Sun, Mar 25, 2018 at 4:55 PM, swapnil negi 
>> wrote:
>>
>>> Hello everyone,
>>> Thanks for the detailed review.
>>> I have made changes to my proposal to incorporate review/merge cycle,
>>> build Python API for the modtool, briefly explain the UI enhancements and
>>> fix typos.
>>> I am still quite unsure about the automated testing part. But as of now,
>>> thorough testing will be done locally.
>>> Please review the updated version of my proposal.
>>> Thanks! :)
>>> Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
>>> Code Link: https://github.com/swap-nil7/GSoC-Proposal
>>>
>>> On Tue, Mar 20, 2018 at 12:33 AM, swapnil negi >> > wrote:
>>>
>>>> Hello everyone!
>>>> I have uploaded my proposal to the GitHub pages. So, please review and
>>>> provide me suggestions to improve the same.
>>>> Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
>>>> Code Link: https://github.com/swap-nil7/GSoC-Proposal
>>>> Thank You!
>>>>
>>>> Regards,
>>>> Swapnil Negi
>>>> Indian Institute of Technology Roorkee
>>>> India
>>>>
>>>>
>>>> On Sat, Mar 17, 2018 at 3:09 AM, swapnil negi >>> > wrote:
>>>>
>>>>> Hi Nicoloas!
>>>>> Thanks for your valuable response.
>>>>> Regarding Python compatibility - I will work upon version independent
>>>>> compatibility using information from the following links:
>>>>> Link[1] <http://python3porting.com/noconv.html> Link[2]
>>>>> <http://python-future.org/compatible_idioms.html>
>>>>> Regarding specific milestones - I have now listed the work that can be
>>>>> assessed after the completion of various phases.
>>>>> Regarding CV: I have removed the section of such personal details from
>>>>> the CV as well as proposal.
>>>>>
>>>>> Cheers,
>>>>> Swapnil Negi
>>>>>
>>>>> On Fri, Mar 16, 2018 at 5:45 PM, Nicolas Cuervo <
>>>>> nicolas.cue...@ettus.c

Re: [Discuss-gnuradio] gr-modtool overhaul: Proposal draft

[swapnil negi]

Hello everyone,
I have incorporated all the mentioned improvements to the best of my
knowledge. Please review the *almost final* draft of the proposal.
Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
Code Link: https://github.com/swap-nil7/GSoC-Proposal
Thank you!

Regards,
Swapnil Negi
Indian Institute of Technology Roorkee


On Sun, Mar 25, 2018 at 4:55 PM, swapnil negi 
wrote:

> Hello everyone,
> Thanks for the detailed review.
> I have made changes to my proposal to incorporate review/merge cycle,
> build Python API for the modtool, briefly explain the UI enhancements and
> fix typos.
> I am still quite unsure about the automated testing part. But as of now,
> thorough testing will be done locally.
> Please review the updated version of my proposal.
> Thanks! :)
> Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
> Code Link: https://github.com/swap-nil7/GSoC-Proposal
>
> On Tue, Mar 20, 2018 at 12:33 AM, swapnil negi 
> wrote:
>
>> Hello everyone!
>> I have uploaded my proposal to the GitHub pages. So, please review and
>> provide me suggestions to improve the same.
>> Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
>> Code Link: https://github.com/swap-nil7/GSoC-Proposal
>> Thank You!
>>
>> Regards,
>> Swapnil Negi
>> Indian Institute of Technology Roorkee
>> India
>>
>>
>> On Sat, Mar 17, 2018 at 3:09 AM, swapnil negi 
>> wrote:
>>
>>> Hi Nicoloas!
>>> Thanks for your valuable response.
>>> Regarding Python compatibility - I will work upon version independent
>>> compatibility using information from the following links:
>>> Link[1] <http://python3porting.com/noconv.html> Link[2]
>>> <http://python-future.org/compatible_idioms.html>
>>> Regarding specific milestones - I have now listed the work that can be
>>> assessed after the completion of various phases.
>>> Regarding CV: I have removed the section of such personal details from
>>> the CV as well as proposal.
>>>
>>> Cheers,
>>> Swapnil Negi
>>>
>>> On Fri, Mar 16, 2018 at 5:45 PM, Nicolas Cuervo <
>>> nicolas.cue...@ettus.com> wrote:
>>>
>>>> Hello Swapnil Negi,
>>>>
>>>> Thank you for your proposal! This project has been in the pipeline for
>>>> long and I'm very excited to see your interest in working on it. I have
>>>> very few comments for now, but the discussion can definitely continue open:
>>>>
>>>> So the timeline that you are proposing is:
>>>> 1) Python3 Compatible
>>>> 2) Implement Plugin Architecture
>>>> 3) Restructure code in favor of functional behavior
>>>> 4) work on UI if time allows
>>>>
>>>> And I agree with this timeline, as it puts core focus on the
>>>> architectural overhaul without disregarding other details aside.
>>>>
>>>>- If I understand correctly, your first task to tackle is the Py3k
>>>>compatibility, which is great. This is definitely something that needs 
>>>> to
>>>>be done, as there is a continuous effort on making the whole GNURadio
>>>>Python3 compatible. But Python2 is not EOL for little less than 2 years
>>>>more, so continuous compatibility is something that has to be kept in 
>>>> mind.
>>>>Let's take your proposed code for raiseException, whose implementation
>>>>won't work on Python2. There are ways to ensure compatibility (using
>>>>wrappers from 'six' for example, which adds a dependency - which can be
>>>>discussed)
>>>>I, however, see that the Python3 branch from GNU Radio already
>>>>implements the syntax that you are proposing, so I might being just too
>>>>picky on this. I expect comments on the matter from the list.
>>>>
>>>>- I see that you have put efforts in contributing already to the
>>>>project by fixing some issues on the tool, and there is hardly a better 
>>>> way
>>>>to get used to it and contribute to the project. No comment here apart 
>>>> from
>>>>saying that we do appreciate you took that path as it puts you into 
>>>> context
>>>>and improves the project. Win-Win!
>>>>
>>>>- I would work on the format of the proposal as well to help you
>>>>    make a better impression and increases your chances of this being 
>>>> accepted.
>>>

Re: [Discuss-gnuradio] gr-modtool overhaul: Proposal draft

[swapnil negi]

Hello everyone,
Thanks for the detailed review.
I have made changes to my proposal to incorporate review/merge cycle, build
Python API for the modtool, briefly explain the UI enhancements and fix
typos.
I am still quite unsure about the automated testing part. But as of now,
thorough testing will be done locally.
Please review the updated version of my proposal.
Thanks! :)
Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
Code Link: https://github.com/swap-nil7/GSoC-Proposal

On Tue, Mar 20, 2018 at 12:33 AM, swapnil negi 
wrote:

> Hello everyone!
> I have uploaded my proposal to the GitHub pages. So, please review and
> provide me suggestions to improve the same.
> Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
> Code Link: https://github.com/swap-nil7/GSoC-Proposal
> Thank You!
>
> Regards,
> Swapnil Negi
> Indian Institute of Technology Roorkee
> India
>
>
> On Sat, Mar 17, 2018 at 3:09 AM, swapnil negi 
> wrote:
>
>> Hi Nicoloas!
>> Thanks for your valuable response.
>> Regarding Python compatibility - I will work upon version independent
>> compatibility using information from the following links:
>> Link[1] <http://python3porting.com/noconv.html> Link[2]
>> <http://python-future.org/compatible_idioms.html>
>> Regarding specific milestones - I have now listed the work that can be
>> assessed after the completion of various phases.
>> Regarding CV: I have removed the section of such personal details from
>> the CV as well as proposal.
>>
>> Cheers,
>> Swapnil Negi
>>
>> On Fri, Mar 16, 2018 at 5:45 PM, Nicolas Cuervo > > wrote:
>>
>>> Hello Swapnil Negi,
>>>
>>> Thank you for your proposal! This project has been in the pipeline for
>>> long and I'm very excited to see your interest in working on it. I have
>>> very few comments for now, but the discussion can definitely continue open:
>>>
>>> So the timeline that you are proposing is:
>>> 1) Python3 Compatible
>>> 2) Implement Plugin Architecture
>>> 3) Restructure code in favor of functional behavior
>>> 4) work on UI if time allows
>>>
>>> And I agree with this timeline, as it puts core focus on the
>>> architectural overhaul without disregarding other details aside.
>>>
>>>- If I understand correctly, your first task to tackle is the Py3k
>>>compatibility, which is great. This is definitely something that needs to
>>>be done, as there is a continuous effort on making the whole GNURadio
>>>Python3 compatible. But Python2 is not EOL for little less than 2 years
>>>more, so continuous compatibility is something that has to be kept in 
>>> mind.
>>>Let's take your proposed code for raiseException, whose implementation
>>>won't work on Python2. There are ways to ensure compatibility (using
>>>wrappers from 'six' for example, which adds a dependency - which can be
>>>discussed)
>>>I, however, see that the Python3 branch from GNU Radio already
>>>implements the syntax that you are proposing, so I might being just too
>>>picky on this. I expect comments on the matter from the list.
>>>
>>>- I see that you have put efforts in contributing already to the
>>>project by fixing some issues on the tool, and there is hardly a better 
>>> way
>>>to get used to it and contribute to the project. No comment here apart 
>>> from
>>>saying that we do appreciate you took that path as it puts you into 
>>> context
>>>and improves the project. Win-Win!
>>>
>>>- I would work on the format of the proposal as well to help you
>>>make a better impression and increases your chances of this being 
>>> accepted.
>>>In your timeline, be sure to explicitly say what deliverable can be
>>>expected when. It's good to know when you are going to start working on
>>>something, but it is also important to know when you are expected to have
>>>it finished. Words like "Milestone" or even "Deliverable" might make this
>>>clear, maybe around the evaluation dates.
>>>
>>>- I see that you included your CV, which is nice to have, but do you
>>>_really_ want your personal data (like phone and address) out in the 
>>> open?
>>>
>>>
>>> I might come back with more comments, but for now this is looking
>>> promising!
>>>
>>> Cheers,
>>> - Nicolas
>

Re: [Discuss-gnuradio] gr-modtool overhaul: Proposal draft

[swapnil negi]

Hello everyone!
I have uploaded my proposal to the GitHub pages. So, please review and
provide me suggestions to improve the same.
Proposal Link: https://swap-nil7.github.io/gsoc-proposal.pdf
Code Link: https://github.com/swap-nil7/GSoC-Proposal
Thank You!

Regards,
Swapnil Negi
Indian Institute of Technology Roorkee
India


On Sat, Mar 17, 2018 at 3:09 AM, swapnil negi 
wrote:

> Hi Nicoloas!
> Thanks for your valuable response.
> Regarding Python compatibility - I will work upon version independent
> compatibility using information from the following links:
> Link[1] <http://python3porting.com/noconv.html> Link[2]
> <http://python-future.org/compatible_idioms.html>
> Regarding specific milestones - I have now listed the work that can be
> assessed after the completion of various phases.
> Regarding CV: I have removed the section of such personal details from the
> CV as well as proposal.
>
> Cheers,
> Swapnil Negi
>
> On Fri, Mar 16, 2018 at 5:45 PM, Nicolas Cuervo 
> wrote:
>
>> Hello Swapnil Negi,
>>
>> Thank you for your proposal! This project has been in the pipeline for
>> long and I'm very excited to see your interest in working on it. I have
>> very few comments for now, but the discussion can definitely continue open:
>>
>> So the timeline that you are proposing is:
>> 1) Python3 Compatible
>> 2) Implement Plugin Architecture
>> 3) Restructure code in favor of functional behavior
>> 4) work on UI if time allows
>>
>> And I agree with this timeline, as it puts core focus on the
>> architectural overhaul without disregarding other details aside.
>>
>>- If I understand correctly, your first task to tackle is the Py3k
>>compatibility, which is great. This is definitely something that needs to
>>be done, as there is a continuous effort on making the whole GNURadio
>>Python3 compatible. But Python2 is not EOL for little less than 2 years
>>more, so continuous compatibility is something that has to be kept in 
>> mind.
>>Let's take your proposed code for raiseException, whose implementation
>>won't work on Python2. There are ways to ensure compatibility (using
>>wrappers from 'six' for example, which adds a dependency - which can be
>>discussed)
>>I, however, see that the Python3 branch from GNU Radio already
>>implements the syntax that you are proposing, so I might being just too
>>picky on this. I expect comments on the matter from the list.
>>
>>- I see that you have put efforts in contributing already to the
>>project by fixing some issues on the tool, and there is hardly a better 
>> way
>>to get used to it and contribute to the project. No comment here apart 
>> from
>>saying that we do appreciate you took that path as it puts you into 
>> context
>>and improves the project. Win-Win!
>>
>>- I would work on the format of the proposal as well to help you make
>>a better impression and increases your chances of this being accepted. In
>>your timeline, be sure to explicitly say what deliverable can be expected
>>when. It's good to know when you are going to start working on something,
>>but it is also important to know when you are expected to have it 
>> finished.
>>Words like "Milestone" or even "Deliverable" might make this clear, maybe
>>around the evaluation dates.
>>
>>- I see that you included your CV, which is nice to have, but do you
>>_really_ want your personal data (like phone and address) out in the open?
>>
>>
>> I might come back with more comments, but for now this is looking
>> promising!
>>
>> Cheers,
>> - Nicolas
>>
>>
>> On Fri, Mar 16, 2018 at 3:57 AM, swapnil negi 
>> wrote:
>>
>>> Hello everyone, I am Swapnil Negi, an undergraduate from Indian
>>> Institute of Technology Roorkee, India. I wish to contribute to the project
>>> idea "gr-modtool overhaul". Here
>>> <https://docs.google.com/document/d/10Nx0tWRlSP43GOCrdSoCVHmcStsZWiKJHNmsdc07MPo/edit?usp=sharing>
>>> is the draft of my proposal. Kindly review it and give your valuable
>>> suggestins.
>>> This is something that I expected from the discussion. If there's
>>> something that I am missing out, please do inform me.
>>> Thanks!
>>>
>>> Regards, Swapnil Negi
>>>
>>>
>>> ___
>>> Discuss-gnuradio mailing list
>>> Discuss-gnuradio@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>
>>>
>>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] gr-modtool overhaul: Proposal draft

[swapnil negi]

Hi Nicoloas!
Thanks for your valuable response.
Regarding Python compatibility - I will work upon version independent
compatibility using information from the following links:
Link[1] <http://python3porting.com/noconv.html> Link[2]
<http://python-future.org/compatible_idioms.html>
Regarding specific milestones - I have now listed the work that can be
assessed after the completion of various phases.
Regarding CV: I have removed the section of such personal details from the
CV as well as proposal.

Cheers,
Swapnil Negi

On Fri, Mar 16, 2018 at 5:45 PM, Nicolas Cuervo 
wrote:

> Hello Swapnil Negi,
>
> Thank you for your proposal! This project has been in the pipeline for
> long and I'm very excited to see your interest in working on it. I have
> very few comments for now, but the discussion can definitely continue open:
>
> So the timeline that you are proposing is:
> 1) Python3 Compatible
> 2) Implement Plugin Architecture
> 3) Restructure code in favor of functional behavior
> 4) work on UI if time allows
>
> And I agree with this timeline, as it puts core focus on the architectural
> overhaul without disregarding other details aside.
>
>- If I understand correctly, your first task to tackle is the Py3k
>compatibility, which is great. This is definitely something that needs to
>be done, as there is a continuous effort on making the whole GNURadio
>Python3 compatible. But Python2 is not EOL for little less than 2 years
>more, so continuous compatibility is something that has to be kept in mind.
>Let's take your proposed code for raiseException, whose implementation
>won't work on Python2. There are ways to ensure compatibility (using
>wrappers from 'six' for example, which adds a dependency - which can be
>discussed)
>I, however, see that the Python3 branch from GNU Radio already
>implements the syntax that you are proposing, so I might being just too
>picky on this. I expect comments on the matter from the list.
>
>- I see that you have put efforts in contributing already to the
>project by fixing some issues on the tool, and there is hardly a better way
>to get used to it and contribute to the project. No comment here apart from
>saying that we do appreciate you took that path as it puts you into context
>and improves the project. Win-Win!
>
>- I would work on the format of the proposal as well to help you make
>a better impression and increases your chances of this being accepted. In
>your timeline, be sure to explicitly say what deliverable can be expected
>when. It's good to know when you are going to start working on something,
>but it is also important to know when you are expected to have it finished.
>Words like "Milestone" or even "Deliverable" might make this clear, maybe
>around the evaluation dates.
>
>- I see that you included your CV, which is nice to have, but do you
>_really_ want your personal data (like phone and address) out in the open?
>
>
> I might come back with more comments, but for now this is looking
> promising!
>
> Cheers,
> - Nicolas
>
>
> On Fri, Mar 16, 2018 at 3:57 AM, swapnil negi 
> wrote:
>
>> Hello everyone, I am Swapnil Negi, an undergraduate from Indian Institute
>> of Technology Roorkee, India. I wish to contribute to the project idea
>> "gr-modtool overhaul". Here
>> <https://docs.google.com/document/d/10Nx0tWRlSP43GOCrdSoCVHmcStsZWiKJHNmsdc07MPo/edit?usp=sharing>
>> is the draft of my proposal. Kindly review it and give your valuable
>> suggestins.
>> This is something that I expected from the discussion. If there's
>> something that I am missing out, please do inform me.
>> Thanks!
>>
>> Regards, Swapnil Negi
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] gr-modtool overhaul: Proposal draft

[swapnil negi]

Hello everyone, I am Swapnil Negi, an undergraduate from Indian Institute
of Technology Roorkee, India. I wish to contribute to the project idea
"gr-modtool overhaul". Here
<https://docs.google.com/document/d/10Nx0tWRlSP43GOCrdSoCVHmcStsZWiKJHNmsdc07MPo/edit?usp=sharing>
is the draft of my proposal. Kindly review it and give your valuable
suggestins.
This is something that I expected from the discussion. If there's something
that I am missing out, please do inform me.
Thanks!

Regards, Swapnil Negi
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Introduction for GSoC participation

[swapnil negi]

Hello everyone!
Happy holi! (holi is an Indian festival of colors)
I am done with the tutorial on out of tree modules. I experimented with the
same and am amazed with the beauty of gr-modtool.
But while running make test, I found out that 'make test' gave two
different results on the same test files and C++ files, i.e. I ran the same
command twice and got two different outputs. And sir if you can please
guide me with what to do next, I will be highly thankful.

PS: Thanks for such informative responses. They were highly beneficial.

On Mon, Feb 26, 2018 at 9:21 PM, Nicolas Cuervo 
wrote:

> Hi there!
>
> We are very glad that you find interest in contributing to GNU Radio and
> GSoC! You are definitely on the right road by getting familiarized with the
> software and its perks by installing it and following the guided tutorials.
> If you have any question regarding functionality that you want to clear out
> before starting writing a proposal, please do not hesitate on letting the
> mailing list know, and we certainly will help you around it.
>
> Now, the ideas that you chose are tasks that are essential behind the
> scenes of GNU Radio's functionality and improvement on any of them will be
> immensely appreciated by the whole community. As you noticed, proficiency
> in both c++ and python is key to getting the ctrl port and the gr-modtool
> to the next level. There are a couple of weeks before the application date,
> so I would suggest you to start choosing which task seems more interesting
> for you and give it a bit more focus on getting hands-on experience. You
> can post your progress on this thread, or ask the mentors (me included)
> about aspects that help you refine the scope of your proposal.
>
> As I'm listed as mentor for the gr-modtool idea, here a bit more about it:
> you mention the if-then-else rules in some of the options of the tool, and
> definitely, that is something that needs work on. However, the intention of
> this as a GSoC project goes beyond that and here, given the whole lot of
> tasks that are part of the "wish-list" of the tool, a strictly definite
> scope is a *must* for a student that wants to take this task. As the idea
> title says, we are facing a "complete makeover". But fear not! you will be
> not needed to make miracles in record time, and you won't be alone! The
> first step in this process is knowing the tool, so go ahead and create a
> couple of dummy blocks as per [1], check the code to understand what is
> going on in the background and determine if you see the stuff that can be
> done better. Regarding the bullet that says "rewrite as a plugin
> architecture", you can also have a quick overview how rfnocmodtool [2] and
> volk_modtool [3] work, just to have a feeling of what kind of plugins are
> expected in the future (writing the rfnocmodtool and volk_modtool plugins
> is not part of the project idea, by the way). And again, questions are very
> welcome!
>
> +*Marcus *might have some short insights on the CtrlPort project that
> might help you make your choice.
>
> Cheers!
> - Nicolas
>
>
>
> [1] https://wiki.gnuradio.org/index.php/OutOfTreeModules
> [2] https://kb.ettus.com/Getting_Started_with_RFNoC_
> Development#Starting_a_custom_RFNoC_block_using_RFNoC_Modtool
> [3] http://manpages.ubuntu.com/manpages/artful/man1/volk_modtool.1.html
>
> On Mon, Feb 26, 2018 at 3:53 PM, swapnil negi 
> wrote:
>
>> Hi,
>> I am Swapnil Negi, an Electronics and Communication undergraduate at
>> Indian Institute of Technology Roorkee, India. I am highly interested in
>> contributing towards GNU Radio as my GSoC project.
>> I am done with setting up the project and have gone through the guided
>> tutorial on gnuradio-companion. Right now, I am learning to program GNU
>> Radio in python and C++.
>> I am a member Information Management Group, a student group responsible
>> for maintaining institute's website and intranet applications; Programming
>> and Algorithms Group, a student group aimed at spreading culture for
>> programming and mathematical algorithms among students. So, I am moderately
>> fluent in python and C++.
>> I have had courses on "Signals and Systems" and "Principles of digital
>> communication" in my academic curriculum which I found pretty interesting,
>> so I am highly enthusiastic about working with GNU Radio this summer.
>> I have checked out the ideas list. Two of the ideas suit me:
>> 1. CtrlPort backend implementation: I, myself faced issues with the
>> thrift version so I really wish to improvise this. I have started reading
>> about remote procedural calls, message queues, etc, the differences and
>>

[Discuss-gnuradio] Introduction for GSoC participation

[swapnil negi]

Hi,
I am Swapnil Negi, an Electronics and Communication undergraduate at Indian
Institute of Technology Roorkee, India. I am highly interested in
contributing towards GNU Radio as my GSoC project.
I am done with setting up the project and have gone through the guided
tutorial on gnuradio-companion. Right now, I am learning to program GNU
Radio in python and C++.
I am a member Information Management Group, a student group responsible for
maintaining institute's website and intranet applications; Programming and
Algorithms Group, a student group aimed at spreading culture for
programming and mathematical algorithms among students. So, I am moderately
fluent in python and C++.
I have had courses on "Signals and Systems" and "Principles of digital
communication" in my academic curriculum which I found pretty interesting,
so I am highly enthusiastic about working with GNU Radio this summer.
I have checked out the ideas list. Two of the ideas suit me:
1. CtrlPort backend implementation: I, myself faced issues with the thrift
version so I really wish to improvise this. I have started reading about
remote procedural calls, message queues, etc, the differences and benefits
of different message queues like level of abstraction, ease of
implementation, etc. It seems interesting to me.
2. gr-modtool overhaul: I haven't gone through the code structure of
gr-modtool but the concept is really interesting. It will also help me get
the real feeling of GNU Radio. I saw the present series of if's and else's
and would like to work on improvising this.

I am not very sure of how to start contributing to the project, so it will
very helpful if I can get your guidance. I will be highly obliged.
Thanks.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio