Dr. Juno Woods comments

Results 166 comments of


                                            Dr. Juno Woods

The input record separator on method IO.each is changed when nmatrix library in required

No. We're all volunteers. I'd encourage you to submit whatever workaround you come up with.

Passing array of arrays as shape leads to bad output

Good catch.

Passing array of arrays as shape leads to bad output

It's because you have double brackets (which is the bug @v0dro was highlighting). For correct functionality, you want one of these: ``` a = NMatrix.zeroes([3], dtype: :complex128) a = NMatrix.zeroes([3,1],...

Passing array of arrays as shape leads to bad output

You shouldn't enter `[[3]]`. It's nonsensical. But NMatrix should be checking to make sure the first entry in the array is a Fixnum.

Passing array of arrays as shape leads to bad output

I'm not really sure what you're asking. We check for lots of user input that is nonsensical because those nonsensical inputs cause unpredictable behavior (such as segmentation faults). You don't...

Passing array of arrays as shape leads to bad output

Oh, I get what you're saying now. Yes, on Ruby 2.2.2 I get the same output as @lokeshh. @v0dro What version of Ruby are you using?

Passing array of arrays as shape leads to bad output

Are you running it in pry, @v0dro?

Passing array of arrays as shape leads to bad output

I hate to ask you to install a new Ruby, but does it happen with 2.2.2? I'd like to try to isolate it.

Passing array of arrays as shape leads to bad output

@v0dro Does the behavior persist if you totally erase your build files and re-build?

Concatenate matrices by specifying them in an Array

So, like hstack/vstack in Numpy? I'm shocked we don't have this, but I can't find it in the code. It ought to be a pretty easy addition.