Hi folks, Sorry my bad (I think) - please update gr-baz and try again. From: op25-dev@yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf Of aaknitt Sent: Monday, 9 April 2012 12:26 PM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: GRC error Ahh...and now Balint has reminded me that yesterday I was using: from baz import op25 That still works today. Andy --- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , "aaknitt" <andyknitt@...> wrote:
I was just about to say "yes, I can import op25 from the python command
line" since I'm almost 100% certain I tried that yesterday after installing op25. However, I just tried it again and it's not working, so I think you're on to something with the PYTHONPATH issue. I'm clueless about how to fix it though, any tips?
Thanks,
Andy
--- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> ,
Steve Glass <stevie.glass@> wrote:
I don't normally build the GRC stuff but I am stoked at Balint's
progress
there. So, with that warning here are some thoughts... Firstly, decoder_ff isn't the way to go. We should be using decoder_bf with a slicer on its input to convert the floats to symbols. That's what the python code does. Secondly, it might just be a PYTHONPATH issue. Can you import the op25 package from the python command line? If you can get it in Python then I reckon it should work in GRC.
ATB
On 9 April 2012 11:13, hotfire00 <andyknitt@> wrote:
**
