I'll simply pull the stereotypical software guy card: Then you'll need get faster storage, and probably a faster PC.
Really, run an analysis ("perf top -ag" is an excellent tool for that)
where your computer is stuck spending most of its time during
operation. Optimize your resources where it matters.
Best regards,
Marcus
On Thu, 2019-07-18 at 14:44 +0530, SG wrote:
> I agree the problem is the amount of samples so I have dropped the idea
> of storing samples but is there a way to handle such sampling rates in
> gnuradio? I would like to know the time stamp of the data received which
> i am unable to access using tag debug. I don't know why but it suddenly
> stops displaying timestamps on the console while displaying the data
> decoded by wifi rx.
>
> Is there any other way to record timestamps of reception ?
>
> Thanks and Regards
>
> SG
>
> On 18/07/19 2:34 PM, Müller, Marcus (CEL) wrote:
> > The problem is not the metadata, the problems is the sheer amount of
> > samples.
> >
> > Best regards,
> > Marcus
> > On Thu, 2019-07-18 at 13:18 +0530, SG wrote:
> > > Hi,
> > >
> > > Thanks for your reply.
> > >
> > > Now that since metadata can't be saved to a file, how can we keep track
> > > of timestamp of the received packets? I can use tag debug to display the
> > > timestamps of received signal but when flowgraph starts demodulating
> > > data it looses track of timestamp display on console. Is there a way to
> > > save timestamps or display timestamps without fail on console.
> > >
> > > Thanks and Regards
> > >
> > > SG
> > >
> > >
> > > _______________________________________________
> > > Discuss-gnuradio mailing list
> > > Discuss-gnuradio@gnu.org
> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
