Re: [Discuss-gnuradio] [GSOC 2018] Ideas please!
Hi Federico, Glad to hear your developments in Uruguai! May be it'll be interesting for your transmitter a MPEG2-TS multiplex. We released (PUC-Rio University) as free software the code of our BTS multiplexer: https://github.com/TeleMidia/tmm Rafael Diniz On 10/16/2017 12:49 PM, Federico 'Larroca' La Rocca wrote: > Hi, > Just a quick comment on our status regarding the transmitter for ISDB-T. > This semester (i.e. beginning last August) a group of students have > started developing it as an end-of-career project (here in Uruguay, the > electrical engineering degree ends with a one-year project) under my > tutoring. > Regarding timing, we should get something that is usable by the > beginning of next year (by then, I should also have more free time and > be able to get more involved in the project). I'm not sure when GSoC > begins, or how to articulate it with the undergrads project, but we'll > be glad to receive feedback and/or help. > As with gr-isdbt, we will publish the code under GPLv3. Our long-term > objective is to donate the complete project to make it part of gr-dtv. > In any case, I'm really glad there are so many people interested in the > project. > best > Federico > > > 2017-10-16 3:20 GMT-03:00 Wunsch, Felix (CEL) <felix.wun...@kit.edu > <mailto:felix.wun...@kit.edu>>: > > Hi Rafael, > > nice idea! Would you be willing to mentor it? > > I just checked the Github Repo for gr-idsb > (https://github.com/git-artes/gr-isdbt > <https://github.com/git-artes/gr-isdbt>) and in their README.md it > says, they are working on the transmitter. Are you in contact with > the author and can you say if this is still actively being pursued? > If it is, this might actually already be done by the time GSoC starts. > > Cheers, > Felix > > Von: Discuss-gnuradio > <discuss-gnuradio-bounces+felix.wunsch=kit@gnu.org > <mailto:kit@gnu.org>> im Auftrag von Rafael Diniz > <raf...@riseup.net <mailto:raf...@riseup.net>> > Gesendet: Montag, 16. Oktober 2017 01:59 > An: discuss-gnuradio@gnu.org <mailto:discuss-gnuradio@gnu.org> > Betreff: Re: [Discuss-gnuradio] [GSOC 2018] Ideas please! > > => GNU Radio ISDB-T DTV Transmitter (ARIB STD-B31). > > > > On 10/14/2017 11:56 AM, Benny Alexandar wrote: > > Hi Felix, > > > > I have couple of Ides for GSOC > > > > 1. DRM digital radio receiver on GNU Radio. We have only DRM > > transmitter but no receivers are available. > > DRM is mainly used in Europe, India and in South America. xHE-AAC > codec > > has recently made license free > > this will be good to add. > > > > 2. Audio Control block: > > This is to synchronize the audio clock of digital radio receiver with > > transmitter clock. Currently there exits no blocks in GNU radio to > > fully support it. > > > > > > -ben > > > > > > > > > > ___ > > Discuss-gnuradio mailing list > > Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > signature.asc Description: OpenPGP digital signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] [GSOC 2018] Ideas please!
Hi Felix, As far as I know, they are starting the development. I'll get in touch. May be some student there could help inside GSoC program. I could help mentor, but as a computer scientist not very good in electrical engineering, it would be needed someone with more knowledge in the lower level OFDM, inverleaving, energy spread, pilot carriers, etc.. On 10/16/2017 04:20 AM, Wunsch, Felix (CEL) wrote: > Hi Rafael, > > nice idea! Would you be willing to mentor it? > > I just checked the Github Repo for gr-idsb > (https://github.com/git-artes/gr-isdbt) and in their README.md it says, they > are working on the transmitter. Are you in contact with the author and can > you say if this is still actively being pursued? If it is, this might > actually already be done by the time GSoC starts. > > Cheers, > Felix > > Von: Discuss-gnuradio <discuss-gnuradio-bounces+felix.wunsch=kit@gnu.org> > im Auftrag von Rafael Diniz <raf...@riseup.net> > Gesendet: Montag, 16. Oktober 2017 01:59 > An: discuss-gnuradio@gnu.org > Betreff: Re: [Discuss-gnuradio] [GSOC 2018] Ideas please! > > => GNU Radio ISDB-T DTV Transmitter (ARIB STD-B31). > > > > On 10/14/2017 11:56 AM, Benny Alexandar wrote: >> Hi Felix, >> >> I have couple of Ides for GSOC >> >> 1. DRM digital radio receiver on GNU Radio. We have only DRM >> transmitter but no receivers are available. >> DRM is mainly used in Europe, India and in South America. xHE-AAC codec >> has recently made license free >> this will be good to add. >> >> 2. Audio Control block: >> This is to synchronize the audio clock of digital radio receiver with >> transmitter clock. Currently there exits no blocks in GNU radio to >> fully support it. >> >> >> -ben >> >> >> >> >> ___ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > > signature.asc Description: OpenPGP digital signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] [GSOC 2018] Ideas please!
Please consider China Digital Radio standard (CDR) -ben From: Benny Alexandar Sent: Saturday, October 14, 2017 8:26 PM To: discuss-gnuradio@gnu.org; felix.wun...@kit.edu Subject: RE: [Discuss-gnuradio] [GSOC 2018] Ideas please! Hi Felix, I have couple of Ides for GSOC 1. DRM digital radio receiver on GNU Radio. We have only DRM transmitter but no receivers are available. DRM is mainly used in Europe, India and in South America. xHE-AAC codec has recently made license free this will be good to add. 2. Audio Control block: This is to synchronize the audio clock of digital radio receiver with transmitter clock. Currently there exits no blocks in GNU radio to fully support it. -ben ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] [GSOC 2018] Ideas please!
Hi, Just a quick comment on our status regarding the transmitter for ISDB-T. This semester (i.e. beginning last August) a group of students have started developing it as an end-of-career project (here in Uruguay, the electrical engineering degree ends with a one-year project) under my tutoring. Regarding timing, we should get something that is usable by the beginning of next year (by then, I should also have more free time and be able to get more involved in the project). I'm not sure when GSoC begins, or how to articulate it with the undergrads project, but we'll be glad to receive feedback and/or help. As with gr-isdbt, we will publish the code under GPLv3. Our long-term objective is to donate the complete project to make it part of gr-dtv. In any case, I'm really glad there are so many people interested in the project. best Federico 2017-10-16 3:20 GMT-03:00 Wunsch, Felix (CEL) <felix.wun...@kit.edu>: > Hi Rafael, > > nice idea! Would you be willing to mentor it? > > I just checked the Github Repo for gr-idsb (https://github.com/git-artes/ > gr-isdbt) and in their README.md it says, they are working on the > transmitter. Are you in contact with the author and can you say if this is > still actively being pursued? If it is, this might actually already be done > by the time GSoC starts. > > Cheers, > Felix > > Von: Discuss-gnuradio <discuss-gnuradio-bounces+felix.wunsch= > kit@gnu.org> im Auftrag von Rafael Diniz <raf...@riseup.net> > Gesendet: Montag, 16. Oktober 2017 01:59 > An: discuss-gnuradio@gnu.org > Betreff: Re: [Discuss-gnuradio] [GSOC 2018] Ideas please! > > => GNU Radio ISDB-T DTV Transmitter (ARIB STD-B31). > > > > On 10/14/2017 11:56 AM, Benny Alexandar wrote: > > Hi Felix, > > > > I have couple of Ides for GSOC > > > > 1. DRM digital radio receiver on GNU Radio. We have only DRM > > transmitter but no receivers are available. > > DRM is mainly used in Europe, India and in South America. xHE-AAC codec > > has recently made license free > > this will be good to add. > > > > 2. Audio Control block: > > This is to synchronize the audio clock of digital radio receiver with > > transmitter clock. Currently there exits no blocks in GNU radio to > > fully support it. > > > > > > -ben > > > > > > > > > > ___ > > 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] [GSOC 2018] Ideas please!
Hi Rafael, nice idea! Would you be willing to mentor it? I just checked the Github Repo for gr-idsb (https://github.com/git-artes/gr-isdbt) and in their README.md it says, they are working on the transmitter. Are you in contact with the author and can you say if this is still actively being pursued? If it is, this might actually already be done by the time GSoC starts. Cheers, Felix Von: Discuss-gnuradio <discuss-gnuradio-bounces+felix.wunsch=kit@gnu.org> im Auftrag von Rafael Diniz <raf...@riseup.net> Gesendet: Montag, 16. Oktober 2017 01:59 An: discuss-gnuradio@gnu.org Betreff: Re: [Discuss-gnuradio] [GSOC 2018] Ideas please! => GNU Radio ISDB-T DTV Transmitter (ARIB STD-B31). On 10/14/2017 11:56 AM, Benny Alexandar wrote: > Hi Felix, > > I have couple of Ides for GSOC > > 1. DRM digital radio receiver on GNU Radio. We have only DRM > transmitter but no receivers are available. > DRM is mainly used in Europe, India and in South America. xHE-AAC codec > has recently made license free > this will be good to add. > > 2. Audio Control block: > This is to synchronize the audio clock of digital radio receiver with > transmitter clock. Currently there exits no blocks in GNU radio to > fully support it. > > > -ben > > > > > ___ > 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] [GSOC 2018] Ideas please!
=> GNU Radio ISDB-T DTV Transmitter (ARIB STD-B31). On 10/14/2017 11:56 AM, Benny Alexandar wrote: > Hi Felix, > > I have couple of Ides for GSOC > > 1. DRM digital radio receiver on GNU Radio. We have only DRM > transmitter but no receivers are available. > DRM is mainly used in Europe, India and in South America. xHE-AAC codec > has recently made license free > this will be good to add. > > 2. Audio Control block: > This is to synchronize the audio clock of digital radio receiver with > transmitter clock. Currently there exits no blocks in GNU radio to > fully support it. > > > -ben > > > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > signature.asc Description: OpenPGP digital signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] [GSOC 2018] Ideas please!
Marcus, these are great suggestions! As far as the packaging task goes, it's important that we keep it within well defined *coding* tasks. For example, GSoC clearly states that documentation changes are not for GSoC. Scripting/maintenance falls into a grey zone, gr_modtool updates are OK. Cheers, Martin On 10/14/2017 03:21 AM, Marcus Müller wrote: > Hi Felix! > > > to get this started: > > I've got some ideas that I'd be willing to mentor (not all of them at > once, and for some I'd like to have a "peer" mentor, or at least input > from someone who's done that kind of software engineering before). I > don't think this list is even exhaustive, but these are the things that > popped into my mind quickest, so I guess that speaks for them: > > * Radar implementations > o MIMO Radar: 1-by-2, 2-by-2 radar? Or a generalized approach? I'm > sure there's a wealth of existing implementations out there, but > we have no "well demonstratable, halfway clean" impl > o passive radar using e.g. DVB-T2 or -S2 as signal donor (we > happen to have demod/mod for that already, anything else would > fly, too)? > That with a distributed approach (i.e. two independent observers > extracting/regenerating the "clean" direct path from the RX, > then crosscorrelating the RX with that to get a PDP, then > combine the two PDPs to find objects on the ℝ²) > * Make Ctrlport good (again): > o We've all been having quite some trouble with the unstable mess > Thrift has turned out to be, and with ZeroMQ in-tree and > low-hanging fruit RPC alternatives (ZeroRPC, which is Msgpack > over ZMQ, for example), and the original idea that the RPC > transport beneath Ctrlport should be switchable, I'd like to see > someone actually implement an RPC transport mechanism that > allows us to get rid of the Thrift dependency > I'm also very open to having someone do e.g. a REST kind of RPC > API, but I do think we need a low-overhead RPC mechanism, so > this is kind of a thing I'd rather see "nearly comes for free > after ZeroRPC works" with a ZWS (ZMQ over websocket transport) > impl (we already have python-based XMLRPC, and it works for slow > things that are variables or function calls in the GRC-generated > Python file) > * Packaging: While that does sound like a core dev team/maintainer's > job, packaging is important, and there's a lot of interesting > footwork to be done that's less of a coordinating and more of a > read-the-docs/implementation thingie: > o Write scripts (CMake, bash, Python?) and add them to the > gr-modtool template that > + automatically generate a good-style Deb, RPM, Arch Pkg, > Whatever-the-brew-we-use on OS X, maybe even an MSI that > works with Geoff's Windows port/ / > + a minimal script/git branch you can merge/diff to add that > functionality to existing modules > + a script to upload the resulting package (source packages) > to the respective build services of major Distros (that > being COPR, Launchpad, build.opensuse.org…) > + maybe even: CGRAN gets an interface that checks whether a > OOT module has native packages, and on which platforms these > build correctly according to above build services > o Make GNU Radio main tree packaging good (again) for people who > aren't on debian(oids): adopt Maitland's great "gnuradio is a > package depending on libgnuradio-runtime, libgnuradio-fft, > libgnuradio-audio, libgnuradio-uhd…" for all distros > + Entails writing RPM specs, arch pkg, and > the-rest-of-what's-realistic-from-above > + benefit: People can install gnuradio-runtime, and exactly > these in-tree modules they need. No need to install UHD and > QT5 on a raspberry pi that doesn't have a USRP nor a screen > + From there on, kind of a maintainer's job to keep in touch > with the distro maintainers to push out the results, XOR > + keep things on our own repos (not that hard with above build > services) and have our own package trees that explicitly > conflict with stock distro packages (not good in the FOSS > community sense, but will work out for users if we also > build the application packages the distros package (mainly: > GQRX, I guess, maybe gr-airmodes)) > * GUI Integration: Looks like we're sticking with Qt5 – so, let's have > an easy way to integrate into Qt5 GUI. > o Idea: Wrap the Qt GUI sinks to appear in QtCreator, including > the GUI aspects of their parameterization > + Export of GUI yields UIC (XML file describing the form) > + Load that UIC in
Re: [Discuss-gnuradio] [GSOC 2018] Ideas please!
Hi Felix, I have couple of Ides for GSOC 1. DRM digital radio receiver on GNU Radio. We have only DRM transmitter but no receivers are available. DRM is mainly used in Europe, India and in South America. xHE-AAC codec has recently made license free this will be good to add. 2. Audio Control block: This is to synchronize the audio clock of digital radio receiver with transmitter clock. Currently there exits no blocks in GNU radio to fully support it. -ben ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] [GSOC 2018] Ideas please!
Hi Felix! to get this started: I've got some ideas that I'd be willing to mentor (not all of them at once, and for some I'd like to have a "peer" mentor, or at least input from someone who's done that kind of software engineering before). I don't think this list is even exhaustive, but these are the things that popped into my mind quickest, so I guess that speaks for them: * Radar implementations o MIMO Radar: 1-by-2, 2-by-2 radar? Or a generalized approach? I'm sure there's a wealth of existing implementations out there, but we have no "well demonstratable, halfway clean" impl o passive radar using e.g. DVB-T2 or -S2 as signal donor (we happen to have demod/mod for that already, anything else would fly, too)? That with a distributed approach (i.e. two independent observers extracting/regenerating the "clean" direct path from the RX, then crosscorrelating the RX with that to get a PDP, then combine the two PDPs to find objects on the ℝ²) * Make Ctrlport good (again): o We've all been having quite some trouble with the unstable mess Thrift has turned out to be, and with ZeroMQ in-tree and low-hanging fruit RPC alternatives (ZeroRPC, which is Msgpack over ZMQ, for example), and the original idea that the RPC transport beneath Ctrlport should be switchable, I'd like to see someone actually implement an RPC transport mechanism that allows us to get rid of the Thrift dependency I'm also very open to having someone do e.g. a REST kind of RPC API, but I do think we need a low-overhead RPC mechanism, so this is kind of a thing I'd rather see "nearly comes for free after ZeroRPC works" with a ZWS (ZMQ over websocket transport) impl (we already have python-based XMLRPC, and it works for slow things that are variables or function calls in the GRC-generated Python file) * Packaging: While that does sound like a core dev team/maintainer's job, packaging is important, and there's a lot of interesting footwork to be done that's less of a coordinating and more of a read-the-docs/implementation thingie: o Write scripts (CMake, bash, Python?) and add them to the gr-modtool template that + automatically generate a good-style Deb, RPM, Arch Pkg, Whatever-the-brew-we-use on OS X, maybe even an MSI that works with Geoff's Windows port/ / + a minimal script/git branch you can merge/diff to add that functionality to existing modules + a script to upload the resulting package (source packages) to the respective build services of major Distros (that being COPR, Launchpad, build.opensuse.org…) + maybe even: CGRAN gets an interface that checks whether a OOT module has native packages, and on which platforms these build correctly according to above build services o Make GNU Radio main tree packaging good (again) for people who aren't on debian(oids): adopt Maitland's great "gnuradio is a package depending on libgnuradio-runtime, libgnuradio-fft, libgnuradio-audio, libgnuradio-uhd…" for all distros + Entails writing RPM specs, arch pkg, and the-rest-of-what's-realistic-from-above + benefit: People can install gnuradio-runtime, and exactly these in-tree modules they need. No need to install UHD and QT5 on a raspberry pi that doesn't have a USRP nor a screen + From there on, kind of a maintainer's job to keep in touch with the distro maintainers to push out the results, XOR + keep things on our own repos (not that hard with above build services) and have our own package trees that explicitly conflict with stock distro packages (not good in the FOSS community sense, but will work out for users if we also build the application packages the distros package (mainly: GQRX, I guess, maybe gr-airmodes)) * GUI Integration: Looks like we're sticking with Qt5 – so, let's have an easy way to integrate into Qt5 GUI. o Idea: Wrap the Qt GUI sinks to appear in QtCreator, including the GUI aspects of their parameterization + Export of GUI yields UIC (XML file describing the form) + Load that UIC in the "Options" Block in GRC + GRC shows dialog to map existing QT Sinks in Flow graph to GUI elements from UIC # Possibly even visually! You can load the UIC and preview, then hook up double click signal slots. + Generates python that loads UIC, places the sink widgets where they belong Cheers, Marcus On 14.10.2017 10:42, Wunsch, Felix (CEL) wrote: > > Hi all, > > > even though GSoC 2017 has ended not too long ago, we already
[Discuss-gnuradio] [GSOC 2018] Ideas please!
Hi all, even though GSoC 2017 has ended not too long ago, we already need to start the preparations for next year! After 5 years of being org admin, Martin has asked for somebody else to take over that task and I'm happy to volunteer for this. Having profited from the GSoC experience myself, this is a great way for me to give back some of the support I received back then. And at this point, we need your support! Do you have a project in mind that could be realized by a student in about 3 months of coding and/or want to mentor? Let's discuss your ideas here on the list and then add them to the wiki so we have a nice range of fleshed-out projects when the org application period starts on January 4. If you are interested but need some inspiration, have a look at the current ideas list and past GSoC projects! Current list: https://wiki.gnuradio.org/index.php/GSoCIdeas Old projects: https://wiki.gnuradio.org/index.php/GSoCPastProjects? Cheers, Felix ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
