[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss-gnuradio] Re: How the valve block works
From: |
Patrick Strasser |
Subject: |
[Discuss-gnuradio] Re: How the valve block works |
Date: |
Sat, 08 Jan 2011 03:21:41 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050602 Thunderbird/1.0.2 Mnenhy/0.7.2.0 |
schrieb Josh Blum on 2011-01-08 01:44:
> The input blocks to the valve, when open, connect to null sinks. The
> idea was to drain any incoming data. This could be desirable if for
> example you had other blocks, like a file sink that also used this
> stream. You wouln't want to back-up indefinitely and then consume all
> the old data when closed again. It depends on the topology. So maybe the
> user should decide...
>
> I think the valve needs a user-set policy. Consume when open, or block
> when open. And while we are at it, for the outputs, produce zeros when
> open, or block when open.
Just found out that the selector block fits my requirements much better.
But do I have the same behaviour here again?
I replaced my const multipliers/adders with selectors, but now it uses
much more cpu load :-(
Regards
Patrick