Hi Marcus,
Just reran the test after editing volk_config, and the result is
somewhat surprising:
Every float in [-1:1] now converts to zero. Every float in [1:2] now
converts to 1. Whereas it should be [-0.5:0.5] and [0.5:1.5].
It seems that most of the time, the u_sse2 converter is used, b
I can reproduce these, but do the errors disappear for you if you
replace "u_sse2 u_sse2" with "generic generic" on that line?
Best regards,
Marcus
On Sat, 2018-06-09 at 18:04 +0200, Paul Boven wrote:
> Hi Marcus,
>
> This machine did not yet have a volk_config when I ran these tests.
>
> I hav
Hi Marcus,
This machine did not yet have a volk_config when I ran these tests.
I have since run volk_profile and rebooted, and the Float->Char
quantization bug still occurs.
$ volk-config-info --machine
avx2_64_mmx_orc
$ grep volk_32f_s32f_convert_8i .volk/volk_config
volk_32f_s32f_convert_8
If possible, please track progress on
https://github.com/gnuradio/volk/issues/188
On Sat, 2018-06-09 at 15:30 +, Müller, Marcus (CEL) wrote:
> Hi Paul,
>
> hm, OK, considering the actual conversion is done in VOLK, can you
> tell
> us
>
> * whether ~/.volk/volk_config exists (and if so, its
Hi Paul,
hm, OK, considering the actual conversion is done in VOLK, can you tell
us
* whether ~/.volk/volk_config exists (and if so, its contents regarding
volk_32f_s32f_convert_8i )
* what the output of `volk-config-info --machine` is?
Thanks,
Marcus
On Sat, 2018-06-09 at 17:13 +0200, Paul Bov
Hi everyone,
I'm trying to perform 2 bit sampling of an RF signal. In one approach,
I'm using a float->char block, and noticed that around zero, a number of
float inputs become quantized in a bin that's one off from the correct
value. The ones that are wrong are always off by one, with their