discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] gr-lte updated to GNU Radio 3.7 API


From: Ralph A. Schmid, dk5ras
Subject: Re: [Discuss-gnuradio] gr-lte updated to GNU Radio 3.7 API
Date: Fri, 20 Dec 2013 10:25:07 +0100

Do you have the possibility to upload the file to my server? It is on a
VDSL50 line (50Mbps in, 10 Mbps out), so upload from the university (DFN)
network should be fast enough. Then I could post a link for direct download
(well, only 10 Mbps) and provide the file via bittorrent...

Ralph.



> -----Original Message-----
> From: Johannes Demel [mailto:address@hidden
> Sent: Thursday, December 19, 2013 5:07 PM
> To: Philip Balister; Ralph A. Schmid, dk5ras
> Cc: Demel, Johannes; 'Mike Cornelius'; 'discuss-gnuradio'
> Subject: Re: [Discuss-gnuradio] gr-lte updated to GNU Radio 3.7 API
> 
> That would be cool anyway.
> 
> On 19.12.2013 06:47, Philip Balister wrote:
> > On 12/19/2013 03:24 AM, Ralph A. Schmid, dk5ras wrote:
> >> I'd be happy putting it onto my ftp server, if it could be useful to
> >> the public. Only a 10 Mbps uplink, but better than nothing :)
> >
> > Any chance we could setup a torrent tracker for large data sets?
> >
> > Philip
> >
> >>
> >> Ralph.
> >>
> >>> -----Original Message-----
> >>> From: address@hidden
> >>> [mailto:address@hidden On
> Behalf
> >>> Of Johannes Demel
> >>> Sent: Thursday, December 19, 2013 9:00 AM
> >>> To: Mike Cornelius; Demel, Johannes
> >>> Cc: discuss-gnuradio
> >>> Subject: Re: [Discuss-gnuradio] gr-lte updated to GNU Radio 3.7 API
> >>>
> >>> Hi Mike,
> >>>
> >>> the reference I use is a rather big file > 1gb. It is hard to share
> >>> such a
> >> file
> >>> publicly anywhere. I put a signal generator on the list of needed
> >> features.
> >>>
> >>> All tests are supposed to pass. Which tests fail on your system? Can
> >>> you
> >> run
> >>> them with -V and mail the error messages. That could help.
> >>>
> >>> Happy hacking
> >>> Johannes
> >>>
> >>> On 18.12.2013 23:54, Mike Cornelius wrote:
> >>>> Hi Johannes,
> >>>>
> >>>> With regard to my earlier message regarding the crash I'm seeing, I
> >>>> note that a few tests fail when I run make test, is that to be
expected?
> >>>> Also do you think it would be possible to publish the reference
> >>>> waveform that you are using ?
> >>>> That way I could check to see if the crash occurs with your known
'good'
> >>>> waveform too.
> >>>>
> >>>> Mike
> >>>>
> >>>>
> >>>> On 19 December 2013 18:37, Mike Cornelius <address@hidden
> >>>> <mailto:address@hidden>> wrote:
> >>>>
> >>>>     Hi Ralph,
> >>>>
> >>>>     I had the same problem at first myself, there is no need to
> >>>>     reconnect anything in the top_level.grc block so long as all the
> >>>>     hier blocks have actually been compiled.
> >>>>     In my case the biggest problem was the LTE_estimator_hier block
> >>>>     would not compile because the 'import lte' failed (see earlier
> >>>>     messages in this thread for details).
> >>>>
> >>>>
> >>>>     Mike
> >>>>
> >>>>
> >>>>     On 19 December 2013 18:27, Johannes Demel
> <address@hidden
> >>>>     <mailto:address@hidden>> wrote:
> >>>>
> >>>>         Hi everybody,
> >>>>
> >>>>         I added screenshots for all the hierarchical flowgraphs and
> >>>> the
> >> top
> >>>>         flowgraph to the docs directory. I hope this helps to build
the
> >>>>         whole
> >>>>         LTE flowgraph in GRC.
> >>>>         Although, I realized that would be very helpful if the
> >> hierarchical
> >>>>         flowgraphs would be compiled with grcc during make and then
> >>>>         installed.
> >>>>         Preferably added to a CMakeLists file. I will look into this.
> >>>>
> >>>>         Happy hacking
> >>>>         Johannes
> >>>>
> >>>>         On 18.12.2013 09:47, Johannes Demel wrote:
> >>>>         > Hi Ralph,
> >>>>         >
> >>>>         > unfortunately there are no screenshots yet. I guess it is a
> >>>>         good idea to
> >>>>         > add some. After the estimator, there should be 2 blocks:
> >>>>         Decode PBCH and
> >>>>         > Decode PCFICH. They take the same stream. and work in
> >>>>         parallel. Then
> >>>>         > after Decode PBCH there is supposed to be a 'Decode BCH'
> >>>>         block. These
> >>>>         > blocks may need some time to generate because they
> >>>> consist of
> >> hier
> >>>>         > blocks. That's kind of the tribute that has to be paid
> >>>> for a
> >> clean
> >>>>         > flowgraph.
> >>>>         > If you opened a flowgraph with missing blocks, as far as I
> >>>>         know, to make
> >>>>         > the missing blocks appear you have to close and reopen at
> >>>>         least this
> >>>>         > particular flowgraph.
> >>>>         >
> >>>>         > Happy hacking
> >>>>         > Johannes
> >>>>         >
> >>>>         >
> >>>>         > On Wed, Dec 18, 2013 at 3:49 AM, Ralph A. Schmid, dk5ras
> >>>>         > <address@hidden <mailto:address@hidden
> >>>>         <mailto:address@hidden>>> wrote:
> >>>>         >
> >>>>         >     Hi,
> >>>>         >
> >>>>         >     after opening and generating the hier blocks still the
> >>>>         top_level.grc
> >>>>         >     has missing blocks, at least LTE estimator outputs and
> >>>>         unpack MIB
> >>>>         >     inputs are unconnected, leaving a large white area in
> >>>>         between. How
> >>>>         >     should this flowgraph look like, is there a screenshot
> >>>>         available
> >>>>         >     somewhere?
> >>>>         >
> >>>>         >     Just wanted to put this all together in my lunch break,
> >>>>         but seems
> >>>>         >     too big for such a short break anyway :)
> >>>>         >
> >>>>         >     Ralph.
> >>>>         >
> >>>>         >
> >>>>         >     > -----Original Message-----
> >>>>         >     > From:
address@hidden
> >>>>         <mailto:address@hidden>
> >>>>         >     <mailto:address@hidden <mailto:address@hidden>>
> >>>>         [mailto:discuss-gnuradio-bounces+ralph
> >>>>         <mailto:discuss-gnuradio-bounces%2Bralph>
> >>>>         >     <mailto:discuss-gnuradio-bounces%2Bralph
> >>>>         <mailto:discuss-gnuradio-
> bounces%252Bralph>>address@hidden
> >>>>         <mailto:address@hidden>
> >>>>         >     <mailto:address@hidden
<mailto:address@hidden>>]
> >>>>         On Behalf Of
> >>>>         >     > Johannes Demel
> >>>>         >     > Sent: Sunday, 15 December, 2013 00:34
> >>>>         >     > To: discuss-gnuradio
> >>>>         >     > Subject: [Discuss-gnuradio] gr-lte updated to GNU
Radio
> >>>>         3.7 API
> >>>>         >     >
> >>>>         >     > Hello GNU Radio enthusiasts,
> >>>>         >     >
> >>>>         >     > some time after the GNU Radio 3.7 release I started
to
> >>>>         move the
> >>>>         >     code for 'gr-lte' to the new API. Besides moving it to
the
> >>>>         new API, I
> >>>>         >     > wanted to clean up code and rework a lot of tests.
Thus,
> >>>>         the whole
> >>>>         >     transition took a lot of time and work.
> >>>>         >     > Now, all current blocks are moved to the GNU Radio
3.7
> >>>>         API with
> >>>>         >     lots of enhancements. e.g. I tried to remove all
> >>>>         hierarchical python
> >>>>         >     blocks
> >>>>         >     > and created them as GRC hier blocks instead. Or
runtime
> >>>>         status
> >>>>         >     events, like cell_id extraction, are all propagated
> >>>>         through message
> >>>>         >     ports
> >>>>         >     > now.
> >>>>         >     > Also, there is a PyBOMBS recipe now to ease the
> >>>>         installation process.
> >>>>         >     >
> >>>>         >     > I hope 'gr-lte' can be useful for others.
> >>>>         >     >
> >>>>         >     > Source code is available at
> >>>>         https://github.com/kit-cel/gr-lte
> >>>>         >     >
> >>>>         >     > Happy hacking
> >>>>         >     > Johannes
> >>>>         >     >
> >>>>         >     > _______________________________________________
> >>>>         >     > Discuss-gnuradio mailing list
> >>>>         >     > address@hidden
> >>>>         <mailto:address@hidden>
> >>>>         <mailto:address@hidden <mailto:Discuss-
> >>> address@hidden>>
> >>>>         >     >
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >>>>         >
> >>>>         >
> >>>>         >     _______________________________________________
> >>>>         >     Discuss-gnuradio mailing list
> >>>>         >     address@hidden
<mailto:address@hidden>
> >>>>         <mailto:address@hidden <mailto:Discuss-
> >>> address@hidden>>
> >>>>         >     https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >>>>         >
> >>>>         >
> >>>>
> >>>>         _______________________________________________
> >>>>         Discuss-gnuradio mailing list
> >>>>         address@hidden <mailto:address@hidden>
> >>>>         https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >>>>
> >>>>
> >>>>
> >>>
> >>> _______________________________________________
> >>> Discuss-gnuradio mailing list
> >>> address@hidden
> >>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >>
> >>
> >> _______________________________________________
> >> Discuss-gnuradio mailing list
> >> address@hidden
> >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >>
> >>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]