-
Notifications
You must be signed in to change notification settings - Fork 140
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
Use NMatrix instead of Matrix #1
Comments
I am creating the gem such that one will able to create a dataframe from an Array, Hash, Matrix, NMatrix(MRI), or MDArray (JRuby). You can see my latest push in the Will that do? |
Oh and anyway, the supplied Matrix object is converted to a flattened Array before storing. |
athityakumar
added a commit
to athityakumar/daru
that referenced
this issue
Apr 7, 2017
v0dro
pushed a commit
that referenced
this issue
Apr 12, 2017
* Adds default order for Daru::DataFrame Rspec test added, has been written in the older format to main consistency. This will be easier to change while re-writing all tests to modern specifications file-wise. RDoc documentation has also been added. * Refines code with ||= * Tries resolving rubocop 0.48.1 release offenses - try #1 * Fixes Rdoc - example of Daru::DataFrame initialize without order
baarkerlounger
added a commit
to baarkerlounger/daru
that referenced
this issue
Nov 7, 2017
* API Readme added to the main DB repo * Images
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Sameer, great job getting started on this problem.
However, one the benefits of having a "DataFrame-like" gem is to improve performance in several other libraries dependant on it simultaneously. So NMatrix is a better chance than the pure Ruby alternative, Matrix.
Other benefit of this approach is that you will probably uncover more bugs in NMatrix. :)
If you have any problems, please ask on the mailing list!
The text was updated successfully, but these errors were encountered: