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
ND4J: INDArray.getColumn on row vector returning scalar #7305
Comments
AlexDBlack
added a commit
that referenced
this issue
Mar 27, 2019
AlexDBlack
added a commit
that referenced
this issue
Mar 28, 2019
AlexDBlack
added a commit
that referenced
this issue
Mar 28, 2019
AlexDBlack
added a commit
that referenced
this issue
Mar 28, 2019
* Add FirstDigitTransform (Benfords law) + tests * Javadoc, polish * #7325 Fix SameDiff.asFlatPrint * Refactor DataVec readers to remove hard-coded use of Files, in favor of streams * Add StreamInputSplit (partly complete) * More tests, fixes * Fixes for model import test failures * DataVec fixes after earlier changes * Another DataVec fix * #7355 SameDiff array reuse fix * #7343 SameDiff method for Pad op * #7305 Fix getColumn on row vector (returning scalar, not view) * #7168 Empty arrays - create only once * #7002 Remove newFormat arg/field * #7352 MultiLayerNetwork.output(DataSetIterator) validation * Fixes * Small fixes * SameDiff variables: Switch to LinkedHashMap for consitent iteration order * Fix validation NPE for LogFileWriter * Reduce3 fixes * Small test fix * Small test fix * Fix bad test * Small test threshold tweak * OpProfiler fix: null x array (random ops etc) * Fix issue with array order not matching flattening order when Nd4j.ordering() == f - Nd4j.createFromArray
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Should return rank 2 (or 1) for consistency with the non row-vector source case.
Aha! Link: https://skymindai.aha.io/features/ND4J-123
The text was updated successfully, but these errors were encountered: