--
You received this message because you are subscribed to the Google Groups "Scala Breeze" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-breeze...@googlegroups.com.
To post to this group, send email to scala-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-breeze/CALW2ey1kxbVCHJu5PK__iPDw9x7s70XERNdkhbrWJx_0anbrPg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-breeze/F13F2FD9-0FA5-44EA-98DE-DC71E2A08F8C%40gmail.com.
I was thinking graphics objects-based (more like mathematica instead of axis based like matlab/mathplotlib) with maybe a scalafx backend, and fine-tuned customization (colors, lines, opacities, dsashing, filling...) by passing option objects like I've been trying in breeze.signal
Kenta
--
You received this message because you are subscribed to the Google Groups "Scala Breeze" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-breeze...@googlegroups.com.
To post to this group, send email to scala-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-breeze/038f2155-c915-4aa2-9946-d0e5a3d08ed7%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "Scala Breeze" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/scala-breeze/Z_2_WIwpjdI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to scala-breeze...@googlegroups.com.
To post to this group, send email to scala-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-breeze/CALW2ey2dV_1oP5R7MRsQZZ3-CeJNgWObcxaaYsSt2sxSgX%3DHGA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-breeze/CALW2ey0cZ%3DB95E-V2tMrxLoadqPPc5eKQjMSS-%3DresrCGZPy4w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-breeze/CA%2B5idAWtUJ1D7r6WmTHk6rkzon%2BYM9CfCVGRG7XNxDCLR0WesQ%40mail.gmail.com.
Hi David,Not to worry. I was only able to complete half of Odersky's online course due to various university commitments but it was enough to fall in love with the language. This summer, I have four months free to follow my interests, really getting to grips with Scala being one of them. So I'm interested in anything that will enable me to gain some experience using the Scala language. I don't have the most technical background but I am a quick learner.
Sacha
On Thursday, 13 March 2014 15:31:18 UTC-4, David Hall wrote:Hi Sacha,Sorry for the long delay.I've been in communication with another student who has been working with Erik (of Spire) and myself to set up a plan for this project.Is there another project that might interest you?On Tue, Mar 4, 2014 at 1:45 PM, <sac...@hotmail.com> wrote:
Dear David,
I am writing to express my interest in the Scala project 'Spire/Algebird Interoperability'. I am a second year student in Applied Maths at McGill with a good knowledge of abstract algebra and an interest in the Scala language.
Looking forward to hearing from you,
Sacha
On Tuesday, February 11, 2014 6:54:08 PM UTC+1, David Hall wrote:Hey everyone,This year I'm planning on trying to get Breeze sponsored by GSoC through Scala itself. They're happy to have us, but want some ideas. Here's what I'm thinking:* Multiple dimensional arrays: Numpy supports arbitrarily dimensioned. Breeze, being strongly typed, currently only supports 1-dimensional vectors and 2-dimensional matrices. We'd like to extend support to higher-order arrays. One possible avenue is to use Shapeless's HLists.* Spire/Algebird interoperability: There are currently a number of different math libraries for Scala. Spire (and, to a lesser extent, Algebird) have fairly fleshed out algebraic hierarchies for Rings, Semirings, Monoids, and the like. Breeze has its own parallel hierarchy, but it is less developed. It would be good to unify these, or at least to provide an interoperability layer.* Another, more ambitious project is to tackle a GPU-backed extension to Breeze, either using (J)CUDA or OpenCL/JavaCL. Breeze is generic enough to support multiple implementations seamlessly, but we have to actually do it.* Improving Breeze-Viz. Breeze-Viz is a visualization library inspired by matplotlib. However, it offers a limited range of operations. Breeze-Viz needs to be revamped to support more kinds of visualizations, and to take advantage of modern Scala design patterns. (More generally, we need a great visualization library for Scala. Currently there are none.)We need a list by tomorrow. I need to flesh these out some more, but I wanted to see what ideas people had.(For reference, an idea needs about 150 words of write-up: http://www.scala-lang.org/news/2013/03/20/gsoc13.html)
--
You received this message because you are subscribed to the Google Groups "Scala Breeze" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-breeze...@googlegroups.com.
To post to this group, send email to scala-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-breeze/b5301fb9-ced0-4867-a547-8584204d6c91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Scala Breeze" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-breeze...@googlegroups.com.
To post to this group, send email to scala-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scala-breeze/e7cd7a3e-2212-4c0a-b7fa-3f52639dc11d%40googlegroups.com.
Thanks for trying to take this on!I like the separation between ndshape and ndarray.The biggest issues are1) I'd like to make the shape of the array (well, the arity of the shape) statically known at compile time. This is the hardest thing about making an ndarray I'll be happy with.
2) Don't use List[T] by default. The default should always be IndexedSeq[T] or Seq[T], unless you actually need a singly linked list or structure sharing.
3) Performance: You've demonstrated competency at using higher order functions and such, but all those closures and things have terrible performance implications for operations that should be fast.
So now array could be created from HList or Tuple of an arbitrary size and it has dimension number check at compile time.
nd = NDArray(arr, 3::4:: Hnil) //ok
nd = NDArray(arr, (2,3,4)) //compilation error
Also made small refactoring according to your notes.
Plan for some next day's:
1)I will introduce NDFlags – container for specific information like is array owning data or just an view. Could be very useful in later development
2)Will try to get familiar with some scala testing framework(Is utest preferable?) and will write some tests.
3)Will implement merging list of n-dim arrays into 1 n+1-dim array, reshaping, axis swapping. Is there some other valuable transformations which I forgot?
How often should I write reports to you and which form of them is preferable?
Hey everyone,This year I'm planning on trying to get Breeze sponsored by GSoC through Scala itself. They're happy to have us, but want some ideas. Here's what I'm thinking:* Multiple dimensional arrays: Numpy supports arbitrarily dimensioned. Breeze, being strongly typed, currently only supports 1-dimensional vectors and 2-dimensional matrices. We'd like to extend support to higher-order arrays. One possible avenue is to use Shapeless's HLists.