On Tue, Aug 19, 2008 at 11:16:17PM -0500, Murtuza wrote: > Hi Friends > > I understand the idea behind using history() in the Gnuradio blocks but > there is one thing that I would like to know in order to understand the > rationale behind using it. I looked at 'gr_single_threaded_scheduler.cc' to > gain an understanding of scheduler implementation and understood how the > forecast() method plays a role. But I wasn't able to figure out how > history() affects its execution. In a previous post Eric said that it > affects the way forecast() behaves and suggested to look at forecast(). But > I am not sure of where to look. Can someone tell me where to look at ? > > Thanks > Ali
It's used in the implementation of forecast in gr_sync_block.cc, gr_sync_interpolator.cc and gr_sync_decimator (indirectly). In looking at the code, I think there's a long standing latent bug in gr_block's forecast, which should be using history in it's stub implementation. I've opened ticket:262. Eric _______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
