-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change function kron to output a 1d vector when input is 1d #1753
Comments
Note this only applies when both inputs are 1d; when either input is 2d, the current behavior appears to be correct |
@josdejong @gwhitney Regarding the issue, I have made changes, if two vectors are 1D then they are returning 1D vector only, although I have two queries in the unit test. |
Kronecker product of two empty arrays being an empty array seems right. |
@gwhitney |
Ah, now I see it; sorry it wasn't clear before. Yes, the agreed-upon behavior change is to remove one level of brackets in the expected output of this case. So you can go ahead and make that change to the unit test as well. If you feel there are any other tests that would exercise cases of interest in the new code, feel free to add them as well. Thanks! |
@gwhitney do I need some sort of access to push the changes in my local branch taken out from develop branch and raise a PR? |
No, you fork the repository, make a branch in your fork, and raise the PR from your fork. Guide at https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork |
Thanks @Kiki-1234-web, I'll review the PR later this week. |
is this issue still open ? |
There was a PR #3133 that purported to resolve this issue; on review there was feedback to the submitter requesting changes to the PR; those changes have not to date been made; hence, yes, this issue remains open at this point. |
Currently the function
kron
outputs a 2d matrix for both 1d and 2d input. It would be more consistent when the output is 1d for 1d input. This will be a breaking change though.For reference: #230 (comment)
The text was updated successfully, but these errors were encountered: