[Chandler-dev] [MVA] Next steps after SoC project
vik.list.chandler at gmail.com
Tue Aug 29 23:26:03 PDT 2006
> - a working parcel to make experiments
> - a set of data performed on Slashdot feeds showing that auto tagging
> after a learning phase is feasible
> - a path to incorporate PCA into Chandler (using MDP)
Awesome. I was wondering if the alpha1 (or 3?) code is usable at this
point, so that I might be able to play around with it? I remember Xun
talking about some steps needed to make the code run, and from what I
gather from Philippe, things weren't totally automated, and a number of
steps were needed to run them.
> I've been discussing with vikSIT on IRC what should be the next steps.
> Eventually, the goal will be to have auto tagging turned on (optionally)
> on the trunk but we won't even see that in Chandler before we have a
> tagging feature in (planned for alpha6). In the meantime, there's a set
> of short term things we should do:
Ah. Couldn't we do it using some hard coded tags anyway? These tags
needn't be applicable to all the other Chandler data, and can instead be
just dummy data.
> 2- update the parcel to be running against the 0.7alpha4 trunk code:
> right now, it runs against 0.7alpha1 which is kind of old. I know that
> the egg stuff sort of threw a wrench in your plan but we should get pass
> that hurdle. May be vikSIT or other contributors (Markku?) could help
Yep, that might be fun. I'm not sure what the general egg problem was,
to be honest - could I have some more information about it?
> 5- make the relevant changes in the MVA project to call the MDP library:
> that we consider sandbox/xluo as the official repo for MVA.
> BTW, just as a roll call, who on this list would be interested to
> contribute to this project moving forward?
Me, for one :)
More information about the chandler-dev