GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||
GeezerVison is showing github.com — lti squeeze: ndarray.ndim == 0 is also a scalar by bnavigator · Pull Request #595 · python-control/python-control Conversation
Contributor
Fixes #594
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
|
There was an error while loading. Please reload this page.
|
Coverage remained the same at 89.274% when pulling 5646146 on bnavigator:fix-594 into 8b900ca on python-control:master. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
#594 is fixed, as one can check manually. But I am confused that 4b44923 without f8fe08a cannot trigger a test failure. And now I will really stop for today. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Found it: >>> np.array(0.1) array(0.1) >>> np.array(0.1)*1J 0.1j |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
What is going on here? does np.array(0.1)*1 also return a scalar instead of an array? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I guess it is a somewhat less intuitive result of the broadcasting mechanics. >>> import numpy as np >>> a=np.array(1.0) >>> a array(1.) >>> a*1J 1j >>> a*1 1.0 >>> 1*a 1.0 >>> 1J*a 1j >>> a+1 2.0 >>> type(a) <class 'numpy.ndarray'> >>> type(1*a) <class 'numpy.float64'> >>> type(a*1J) <class 'numpy.complex128'> |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
squeeze: return shape of the frequency response.
There was an error while loading. Please reload this page.