Your comment is noted but moot at this point because a new issue has grabbed my attention. I will get a test working properly with std::complex<float> and only then will I explore new territory.
Rick On 2025-02-20 15:30, Jim Melton wrote: > I don't know if you are working in C++ or Python, but I might point out that > std::complex<int> is likely Undefined Behavior. Sure, it's attractive, but > you deserve what you get when you tread in UB territory. > > Your best bet is to convert your std::pair<int,int> into std::complex<float> > and be done with it. > > --- > Jim Melton > > -----Original Message----- > Sent: Thursday, February 20, 2025 16:05 > Cc: discuss-gnuradio@gnu.org > Subject: [EXTERNAL] Re: Complex Integer16 type conversion > > > I was hoping for a simple work around of this type; thank you. Your > suggestion looks promising but this block throws out an error message even > within a very simple configuration using Complex Float data as the input > type. I'll try the integer data when this current bug is fixed. > > > Rick > > > On 2025-02-20 11:12, Martin Braun wrote: >> Try a stream-to-vector and make the output a vector length of 2. Then >> feed that into your other block. The runtime checks the item size, not >> the literal types IIRC. >> >> --M >> >> On Thu, Feb 20, 2025 at 2:03 AM aardric via GNU Radio, the Free & >> Open-Source Toolkit for Software Radio <discuss-gnuradio@gnu.org> wrote: >> >> Since 3.10.12.0-rc1 does not have a type converter from Integer 16 >> Re-Im >> pairs to Complex Integer16, is there a clever, simple kludge to feed >> Integer 16 Re-Im pairs to a block with Complex Integer 16? I >> could read >> the file and convert to Complex float 32 (which the block also >> accepts) >> but I am concerned about throughput since this is a relatively high >> bandwidth test. I guess I should try first. >> >> >> Rick > CONFIDENTIALITY NOTICE - SNC EMAIL: This email and any attachments are > confidential, may contain proprietary, protected, or export controlled > information, and are intended for the use of the intended recipients only. > Any review, reliance, distribution, disclosure, or forwarding of this email > and/or attachments outside of Sierra Nevada Company, LLC. (SNC) without > express written approval of the sender, except to the extent required to > further properly approved SNC business purposes, is strictly prohibited. If > you are not the intended recipient of this email, please notify the sender > immediately, and delete all copies without reading, printing, or saving in > any manner. --- Thank You.
