[
https://issues.apache.org/jira/browse/MAHOUT-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deneche A. Hakim updated MAHOUT-56:
---
Attachment: watchmaker-tsp.patch
> Watchmaker Integration
> --
>
>
[
https://issues.apache.org/jira/browse/MAHOUT-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597873#action_12597873
]
Deneche A. Hakim commented on MAHOUT-56:
I started with the Traveling Salesman Probl
Watchmaker Integration
--
Key: MAHOUT-56
URL: https://issues.apache.org/jira/browse/MAHOUT-56
Project: Mahout
Issue Type: Task
Reporter: Deneche A. Hakim
The goal of this task is to allow watchmaker definded
Yes this test is a bit fragile, in that it depends quite a bit on the
speed of the machine that runs it. I set fairly conservative timing
targets but I can easily relax them further. I will adjust this right
away.
On Sun, May 18, 2008 at 3:46 PM, deneche abdelhakim <[EMAIL PROTECTED]> wrote:
> as
As you do this, it would be good to include a version or three that use
simple meta-mutation. For TSP, a simple rate can be encode as single number
which expresses the distribution of the number of edits to make when
producing an offshoot. Given this parameter you can sample from, say, a
Poisson
Yes.
That would be the normal procedure.
You should also file a jira on the test that fails. Sean, who has been
putting taste into the system will likely get that squared away pretty
quickly.
On Sun, May 18, 2008 at 12:46 PM, deneche abdelhakim <[EMAIL PROTECTED]>
wrote:
> as part of my gsoc p
as part of my gsoc project I started adapting one of Watchmaker examples (TSP)
to use with Mahout. I believe that the next step is to start a Jira issue and
post an svn patch, isn't it ?
I also did a fresh checkout of Mahout and run "ant test" in the core
directory and got a wonderful "Tests fai