[mlpack] Automative benchmarking

Ranjani shreeranjaniss at gmail.com
Thu Mar 6 07:47:44 EST 2014


Hi,
Sorry for the delayed response and Thanks Ryan for the reply .

Shogun's description about the project said
"We have the idea that you will give them a helping hand in pushing the
infrastructure of their project (buildbot!) about 30% of the time, spend
another 30% on polishing the visualisation and presentation of the results,
and spend the remaining 30% on Shogun specific things, such as polishing
the used Shogun code, fix possible bugs and add new algorithms from our
toolbox."

What I meant was I want to discuss about visualisation subpart a little
later as I thought that results part come at the end of the project and
hence we can focus on the remaining subparts now.

Any other suggestions are welcome.
Also I understood that adding new algorithms to the benchmarking project
can be considered as an additional result apart from the main project.


Thanks,
Ranjani





On Wed, Mar 5, 2014 at 8:19 PM, Ryan Curtin <gth671b at mail.gatech.edu> wrote:

> On Wed, Mar 05, 2014 at 09:23:43AM +0530, Ranjani wrote:
> > Hi,
> > Thanks for the link on Shogun's integration.I looked at their detailed
> > expectations.
> > I would like to discuss more on
> > 1.Adding new algorithms
> > 2.Improving accuracy and fixing Bottlenecks
>
> This is a very vague description.  Can you describe more what you mean?
> If you mean that you want to implement entirely new algorithms for
> mlpack, then that would be outside the scope of the automatic
> benchmarking project, but could still be a project.  What I mean to
> point out here is that the benchmarking project itself is now a separate
> codebase than mlpack.
>
> If you meant adding new algorithms to the benchmarking project results,
> be aware that adding an algorithm is usually done in a few days, with
> not very many hours of work.  So just adding a few algorithms would not
> be a large enough chunk of work to be a good Summer of Code project.
>
> I don't know what you mean about "improving accuracy and fixing
> bottlenecks"; can you elaborate?
>
> Thanks,
>
> Ryan
>
> --
> Ryan Curtin    | "Maybe the next time."
> ryan at ratml.org |   - J.G. Ballard
>



-- 
Regards,
Shree Ranjani
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cc.gatech.edu/pipermail/mlpack/attachments/20140306/262a930e/attachment-0003.html>


More information about the mlpack mailing list