[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] foreacast (mis)behavior for gating block
From: |
Jared Dulmage |
Subject: |
Re: [Discuss-gnuradio] foreacast (mis)behavior for gating block |
Date: |
Tue, 6 Oct 2015 15:19:55 +0000 |
Martin, et. al,
I apologize for the delayed response. My forecast function had merely:
def forecast(self, noutput_items, ninput_items_required):
ninput_items_required[0] = noutput_items
I determined my error. In my flow graph I had
vector source -> throttle -> frame sync (DUT) -> vector sink
and I found my forecast was being called with ever decreasing noutput_items.
The problem was my throttle rate was too low (on the order of samples/second)
and the frame sync block was being starved for input. I probably could have
waited longer until samples collected in throttle to be sent to my DUT, but the
forecast messages arrived so fast it looked like an unending loop.
Thanks.
Jared.
------------------------------------------------------
Jared Dulmage
Engineering Specialist
Digital Comm. and Implementation Dept.
Aerospace Corporation
310-336-3140