[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Re: complex numbers in GRC missing documentation?
From: |
Jim Melton |
Subject: |
RE: Re: complex numbers in GRC missing documentation? |
Date: |
Thu, 21 Oct 2021 21:02:18 +0000 |
I had a very confusing conversation with a co-worker where he was describing
complex numbers as "j + 0.00001". I had no referent for using "j" to represent
"sqrt(-1)". Apparently Matlab uses "j", Electrical Engineers use "j" (because
"i" is current), and now I learn that Python supports it as well.
I like "complex(0.5,0.5)" as much less ambiguous. Of course, once you know
about "j" it's easy to use...
---
Jim Melton
-----Original Message-----
From: Discuss-gnuradio <discuss-gnuradio-bounces+jim.melton=sncorp.com@gnu.org>
On Behalf Of Aardric
Sent: Thursday, October 21, 2021 13:35
To: discuss-gnuradio@gnu.org
Subject: [EXTERNAL] Re: complex numbers in GRC missing documentation?
I thought and tried but for some unknown internal reason, I used "i"
rather than "j" this time. I didn't think of "complex(real,imag)").
So, this was trivial and the documentation is adequate.
Thanks.
On 2021-10-21 12:28 p.m., Marcus D. Leech wrote:
> On 2021-10-21 3:21 p.m., Aardric wrote:
>> Hail,
>> I'm surprised that I haven't encountered this before but I am
>> unable to enter a complex number in a GRC field for example the "Signal
>> Source"
>> block (gr version: 3.9.3). There doesn't appear to be documentation,
>> at least in an obvious place.
>> Entering (0.5,0.5) in the complex offset field yields:
>> Param - Offset(offset):
>> Expression (0.5, 0.5) is invalid for type 'complex'.
>>
>> A single float value offsets I but not Q.
>>
>> I apologize if I have missed something totally obvious.
>> BTW: the documentation is improving nicely over time; my compliments
>> to the contributors.
>>
>> Rick
>>
>>
>>
> They are necessarily Python expressions, so
>
> complex(real,imag)
>
> or
>
> 1.0+0j
>
> Etc
>
>
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 Corporation (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.