Thank you very much for the suggestions, Marcus.
I'll consider all of them and I'll try to think on a solution to the
problem you mentioned about the other blocks.
Best regards,
Artur
Em seg., 27 de abr. de 2020 às 13:25, Marcus Müller
escreveu:
> Hi Artur,
>
> Two options:
>
> 1.
>
> simply se
Hi Artur,
Two options:
1.
simply set your output signature to a single output, with the itemsize
being the size of one element of your matrix. Use set_output_multiple to
N·M, so that the scheduler knows you'll always produce as many items as
fit into your matrix.
2.
simply set your output
Hi Marcus,
By "variable", it means "the size is set by the user once and doesn't change
during runtime" and, most importantly, it can change from one simulation to
another. In my case, each output terminal from my Python Block is connected
to a Frequency Sink and therefore it would be unpractical
Hi Artur,
does "variable" mean the size is set by the user once and doesn't change
during runtime, or does it mean that the same block outputs matrices of
different length?
Another way of thinking about this would be:
Is this a block that really produces a _stream of identical items_ or is
i
Hi all,
I'm using the Python Block for signal processing and I need to export a
matrix for further Fourier analysis.
I think I can 'slice' this matrix into several lines (or columns) and store
each of them in an 1-d output_items[i][:] variable, i=1,2...,number of
lines (or columns).
But considerin
