Thank you. I tried, and it worked Cheers
On Wed, Jun 12, 2019 at 11:48 AM Müller, Marcus (CEL) <muel...@kit.edu> wrote: > Oh, or try > > from pmt.pmt_to_python import pmt_to_python as p2p > > vector = p2p(message) > for elem in vector: > do_stuff_with_elem > > > On Wed, 2019-06-12 at 10:56 -0500, Daniel Andres Palacios wrote: > > Thanks Marcus, thats a good idea. I got the message from the debug block > but, is there a way to iterate over that message recieved? > > When I pass pmt.is_vector(message) i got True, but then I can't get a > specific object in the vector because it hasn't a get attribute. > > > > sorry for the insistence, I kind of beginner and the PMT python API is > not specific enough > > > > On Tue, Jun 11, 2019 at 12:27 PM Daniel Andres Palacios < > dapa...@gmail.com> wrote: > > > Ok. Thank you. > > > I managed to get the messages from the debug block. Now, I have to > deal with types conversation. > > > > > > Thanks > > > > > > On Tue, Jun 11, 2019 at 7:59 AM Müller, Marcus (CEL) <muel...@kit.edu> > wrote: > > > > But the debug block does exactly what you need: store the data and > thus > > > > allow for analysis. Why don't you want to use it? Sounds like the > right > > > > tool. > > > > > > > > > > > > On Tue, 2019-06-11 at 03:03 -0500, Daniel Andres Palacios wrote: > > > > > Hi. Thanks for your reply. > > > > > > > > > > The signal extractor block's output is a vector of tuples with > center frequency an band width. I want to know the length of the vector > without using the debug block. And store the data for further processing. > > > > > > > > > > On Tue, Jun 11, 2019, 02:22 Müller, Marcus (CEL) <muel...@kit.edu> > wrote: > > > > > > There's the function probes. > > > > > > > > > > > > Using that is almost always a sign of bad design; what do you > want to > > > > > > achieve that way? > > > > > > > > > > > > Best regards, > > > > > > Marcus > > > > > > > > > > > > On Sun, 2019-06-09 at 19:23 -0500, Daniel Andres Palacios wrote: > > > > > > > > > > > > > > Hi everyone > > > > > > > it is there a way to get and store in a variable the output of > gr- > > > > > > > inspector's blocks. > > > > > > > > > > > > > > -- > > > > > > > Daniel Andrés Palacios Carabalí > > > > > > > Student of Telemathics engineering > > > > > > > Icesi University- Cali, Colombia > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Discuss-gnuradio mailing list > > > > > > > Discuss-gnuradio@gnu.org > > > > > > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > > > > > _______________________________________________ > > > > > Discuss-gnuradio mailing list > > > > > Discuss-gnuradio@gnu.org > > > > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > > > > -- > > > Daniel Andrés Palacios Carabalí > > > Student of Telemathics engineering > > > Icesi University- Cali, Colombia > > > =========================== > > > Estudiante de Ingeniería Telemática > > > Universidad Icesi. - Cali, Colombia > > > > > -- *Daniel Andrés Palacios Carabalí* *Student of Telemathics engineering* *Icesi University- Cali, Colombia* *===========================* *Estudiante de Ingeniería Telemática* *Universidad Icesi. - Cali, Colombia*
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
