[Top][All Lists]

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

Re: [Discuss-gnuradio] Question about metadata filesink

From: CEL
Subject: Re: [Discuss-gnuradio] Question about metadata filesink
Date: Thu, 25 Jul 2019 16:50:51 +0000

Also, I'd recommend not to rely on TCP sink/source, it's python-only
and it is indeed quite fiddly – the constructors can deadlock each
On Wed, 2019-07-10 at 17:51 -0400, Marcus D. Leech wrote:
> On 07/10/2019 02:54 PM, Ellie White wrote:
> > Hello!
> > 
> > I am working on a radio astronomy project with the Green Bank
> > Observatory / NRAO Central Development Lab this summer, utilizing GNU
> > Radio and an Ettus Research SDR, and I've got a question regarding how
> > to collect metadata information from a filesink.
> > 
> > I have attached the flowgraph I am using to this email. The project
> > requires that I use two computers in tandem for data collection -- one
> > is connected to the Ettus -- it is the TCP server, and sends an
> > interleaved data stream to the TCP client flowgraph (attached) on the
> > machine which will be storing the data. As you can see, I am saving
> > integrated spectra to a file. My question is simply, how do I retrieve
> > a time stamp corresponding to each spectra using the metadata time
> > sink? I have been fiddling with this all afternoon attempting to get
> > it to work properly, and I have been able to save data to a file, read
> > out spectra (using attached Python program), and display header
> > information using the command gr_read_file_metadata in the terminal,
> > but this is just showing me a timestamp for the beginning of the data
> > collection run, rather than showing me timestamps for each spectrum
> > which is saved to file, and I am not sure how to implement this.
> > 
> > Any advice would be much appreciated! If I can provide any more info
> > about my system or what steps I have tried, please let me know. Thank
> > you so much for your time -- have a good afternoon!
> > 
> > Best,
> > Ellie
> So, another thing to keep in mind is that the TCP source/sink DO NOT 
> CARRY metadata tags--only the samples.  So if you're relying on that,
>    it won't work.
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Attachment: smime.p7s
Description: S/MIME cryptographic signature

reply via email to

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