Le 2019-11-13 16:40, Müller a écrit :

> To second that: GNU Radio has no intrinsic notion of time.
> 
> If you have a signal that is a continuous sample flow, then: the sample
> number divided by the (theoretical) sampling rate would be the
> theoretical time since start of the flow graph?
> 
> Best regards,
> Marcus
> 
> On Wed, 2019-11-13 at 10:33 -0500, Michael Dickens wrote: Hi GD - GNU Radio 
> doesn't implement simulated time in runtime in any direct way. If you enable 
> performance counters, assuming that feature still builds and functions, you 
> might be able to get info on timing -- for example latencies and throughput; 
> maybe more, I don't recall all the info PC provides access to.
> 
> The only blocks with a knowledge of time are a few sources & sinks (e.g., 
> gr-uhd using timed Tx packets), and the "throttle" block. There are probably 
> some GR OOT modules that have blocks with knowledge of time, too. I don't 
> know of any GR OOT project that tries to augment GR with more specific 
> knowledge of time, such as implement simulated time.
> 
> Hope this is useful! - MLD
> 
> On Wed, Nov 13, 2019 at 8:40 AM Guy Durrieu <guy.durr...@onera.fr> wrote: 
> Hello list !
> 
> In GNU Radio, does it exist a mean, for a logical module which needs it, 
> to get during a simulation the current simulated time (e.g. in order to 
> calculate the delay between message arrivals) ? I was not able to find 
> out something like that in the doc...
> 
> Thanks in advance for your help !
> 
> Regards.
> 
> -- GD.
> 
> Guy Durrieu
> ONERA - Département Traitement de l'Information et Systèmes
> CEntRe de Toulouse, 2, avenue Edouard Belin BP 74025 31055 TOULOUSE CEDEX 4
> Tél. +33 5 62 25 26 59
> avertissement http://www.onera.fr/onera-en/emails-terms

Mickael, Marcus, 

Thanks for your help. That's what I suspected, but it's better to have a
confirmation by authorized people :) 

Regards. 

-- GD.

Reply via email to