2013/7/25 Yexi Jiang <[email protected]> > I also think about to remove the regression.CostFunction and create one in > ml.math. But it seems that the argument list is quite different from the > DoubleDoubleFunction defined in ml.math.
yes, that's because it came before the MLP Function API and was designed just for the case of regression. So I'd be +1 in standardizing our interfaces, making some of the changes mentioned before and more if needed. > I think we need to figure out how > to replace the regression.CostFunction with existing ones. Moreover, I > found both the linear regression and logistic regression use gradient > descent. So they can be treated as a two layer MLP in fact. > yes, they just use the plain gradient descent BSP implementation but one could do both with a neural network (MLP) as well, however I'd like to have separate implementations which can address different scenarios. Regards, Tommaso > > Regards, > Yexi > > > 2013/7/25 Tommaso Teofili <[email protected]> > > > Hi Yexi, > > > > sorry for the late reply, I think we can improve a bit our ML API by > adding > > (for example) generics to Functions, move regression.CostFunction > interface > > to math or remove it as some functions in math are themselves cost > > functions, change MLP package name from perception to perceptron, this > kind > > of small things that may result (IMHO) in a more readable and user > friendly > > API. > > > > My 2 cents, > > Tommaso > > > > > > > > > > 2013/7/21 Yexi Jiang <[email protected]> > > > > > Hi, Tommaso, > > > > > > For the machine learning module, what kind of refactoring do you think > is > > > necessary? > > > > > > Regards, > > > Yexi > > > > > > > > > 2013/7/21 Edward J. Yoon <[email protected]> > > > > > > > Additionally, Queue is also one of big issues. > > > > > > > > On Sun, Jul 21, 2013 at 8:55 PM, Tommaso Teofili > > > > <[email protected]> wrote: > > > > > Hi Edward, > > > > > > > > > > I'm still quite unsure about the status of FT so it may be worth > > doing > > > > some > > > > > work to make sure that is fully working (but it may be just me). > > > > > Also vertex storage in graph package should be improved. > > > > > Then I'd say some refactoring of machine learning module APIs > > together > > > > with > > > > > addition of "Collaborative Filtering" (and eventually some other > > > > > algorithms, but I'm still unsure there). > > > > > > > > > > My 2 cents, > > > > > Tommaso > > > > > > > > > > > > > > > > > > > > 2013/7/19 Edward J. Yoon <[email protected]> > > > > > > > > > >> Hi all, > > > > >> > > > > >> Once HAMA-742 is done, users will be able to install a Hama > cluster > > on > > > > >> existing Hadoop 1.x and new Hadoop 2.x without issues. > > > > >> > > > > >> I think urgent tasks are finished, now it's time to discuss about > > the > > > > >> future roadmap Hama 0.7 and begin enhancement work. > > > > >> > > > > >> Please feel free to voice your opinions. > > > > >> > > > > >> Thanks. > > > > >> > > > > >> -- > > > > >> Best Regards, Edward J. Yoon > > > > >> @eddieyoon > > > > >> > > > > > > > > > > > > > > > > -- > > > > Best Regards, Edward J. Yoon > > > > @eddieyoon > > > > > > > > > > > > > > > > -- > > > ------ > > > Yexi Jiang, > > > ECS 251, [email protected] > > > School of Computer and Information Science, > > > Florida International University > > > Homepage: http://users.cis.fiu.edu/~yjian004/ > > > > > > > > > -- > ------ > Yexi Jiang, > ECS 251, [email protected] > School of Computer and Information Science, > Florida International University > Homepage: http://users.cis.fiu.edu/~yjian004/ >
