es:
> >>
> >>>> * GPU support (full compiler and runtime support)
> >>
> >>>>>> Can we break this down into phases:
> >> https://issues.apache.org/jira/browse/SYSTEMML-445 ? We can discuss the
> >> timeline of the phase
ebra v2
>>
>>>> * Code generation (automatic operator fusion)
>>
>>>> * Extended parfor (full spark exploitation, micro-batch support)
>>
>>>> * Scale-up architecture (large dense blocks, numa)?
>>
>>>>
>>
>>&g
t; 5) Algorithms
>
> >> * Graduate "staging" algorithms (robustness/performance)
>
> >> * Perftest: include all algorithms into automated performance tests
>
> >> >> via spark-submit + via Scala/Python wrappers
>
> >>
>
> >
msvm
>> (preprocessing, label representation, etc)
>> >> + command-line variable naming. For example: maxi, maxiter, etc.
>>
>> Thanks,
>>
>> Niketan Pansare
>> IBM Almaden Research Center
>> E-mail: npansar At us.ibm.com
>> http://re
iew.php?person=us-npansar
>
> Matthias Boehm ---01/03/2017 02:44:39 PM---Yes indeed, most of (3) and (4)
> can be done incrementally. For (5), some of the changes might also
>
> From: Matthias Boehm
> To: dev@systemml.incubator.apache.org
> Date: 01/03/2017 02:44 PM
> Subje
cubator.apache.org
Date: 01/03/2017 02:44 PM
Subject: Re: [DISCUSS] Roadmap SystemML 1.0
Yes indeed, most of (3) and (4) can be done incrementally. For (5), some
of the changes might also modify the signature of algorithms (i.e.,
parameters and required input data) but it would help, f
Yes indeed, most of (3) and (4) can be done incrementally. For (5), some
of the changes might also modify the signature of algorithms (i.e.,
parameters and required input data) but it would help, for example with
decision trees, as users no longer need to dummy code their inputs.
Generally, I'
On Tue, Jan 3, 2017 at 11:50 AM, Matthias Boehm
wrote:
> I'd like to initiate the discussion of a concrete roadmap for our next
> release. According, to previous discussions, I'd think it's fair to say
> that we agree on calling it SystemML 1.0. We should carefully plan this
> release as it's an
I'd like to initiate the discussion of a concrete roadmap for our next
release. According, to previous discussions, I'd think it's fair to say
that we agree on calling it SystemML 1.0. We should carefully plan this
release as it's an opportunity to change APIs and remove some older
deprecated f
