Welcome Pat Ferrel as new committer on Mahout
Hi, this is to announce that the Project Management Committee (PMC) for Apache Mahout has asked Pat Ferrel to become committer and we are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since in addition to posting patches on JIRA it also gives write access to the code repository. That also means that now we have yet another person who can commit patches submitted by others to our repo *wink* Pat, we look forward to working with you in the future. Welcome! It would be great if you could introduce yourself with a few words. -s
Re: Build failed in Jenkins: Mahout-Quality #2588
Grant told me he will have a look, he should have access. Would be a good thing if you could also ask for access with infra. -s On 04/24/2014 02:36 AM, Andrew Musselman wrote: Infra escalation in order? I hate broken builds. On Tue, Apr 22, 2014 at 12:33 PM, Sean Owen sro...@gmail.com wrote: (I have some access but don't seem to have permission to change the job config.) On Tue, Apr 22, 2014 at 8:02 PM, Sebastian Schelter s...@apache.org wrote: Who has access to the jenkins build server and can fix the failure? It looks as if some paths need to be modified after the renaming of core to mrlegacy. --sebastian
Re: Welcome Pat Ferrel as new committer on Mahout
Congratulations Pat! Best regards, Saleem On Thu, Apr 24, 2014 at 3:49 PM, Sebastian Schelter s...@apache.org wrote: Hi, this is to announce that the Project Management Committee (PMC) for Apache Mahout has asked Pat Ferrel to become committer and we are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since in addition to posting patches on JIRA it also gives write access to the code repository. That also means that now we have yet another person who can commit patches submitted by others to our repo *wink* Pat, we look forward to working with you in the future. Welcome! It would be great if you could introduce yourself with a few words. -s
Re: Welcome Pat Ferrel as new committer on Mahout
Congratulations Pat! :-) On Apr 24, 2014, at 12:19, Sebastian Schelter s...@apache.org wrote: Hi, this is to announce that the Project Management Committee (PMC) for Apache Mahout has asked Pat Ferrel to become committer and we are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since in addition to posting patches on JIRA it also gives write access to the code repository. That also means that now we have yet another person who can commit patches submitted by others to our repo *wink* Pat, we look forward to working with you in the future. Welcome! It would be great if you could introduce yourself with a few words. -s
Re: Welcome Pat Ferrel as new committer on Mahout
Awesome Pat congrats!!! Very well deserved. Sent from my iPhone On Apr 24, 2014, at 6:20 AM, Sebastian Schelter s...@apache.org wrote: Hi, this is to announce that the Project Management Committee (PMC) for Apache Mahout has asked Pat Ferrel to become committer and we are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since in addition to posting patches on JIRA it also gives write access to the code repository. That also means that now we have yet another person who can commit patches submitted by others to our repo *wink* Pat, we look forward to working with you in the future. Welcome! It would be great if you could introduce yourself with a few words. -s
Re: Welcome Pat Ferrel as new committer on Mahout
Congratulations Pat! Been enjoying your discussions so far. Looking forward to working with you. On 4/24/14, 6:22 AM, Frank Scholten wrote: Congratulations Pat! :-) On Apr 24, 2014, at 12:19, Sebastian Schelter s...@apache.org wrote: Hi, this is to announce that the Project Management Committee (PMC) for Apache Mahout has asked Pat Ferrel to become committer and we are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since in addition to posting patches on JIRA it also gives write access to the code repository. That also means that now we have yet another person who can commit patches submitted by others to our repo *wink* Pat, we look forward to working with you in the future. Welcome! It would be great if you could introduce yourself with a few words. -s
[jira] [Commented] (MAHOUT-157) Frequent Pattern Mining using Parallel FP-Growth
[ https://issues.apache.org/jira/browse/MAHOUT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979725#comment-13979725 ] Amanpreet Singh Saini commented on MAHOUT-157: -- Hey Robin, Regarding your comment dated 07/Sep/09 06:32 I know its been a long time since the post, but i actually wanted to use pfpgrowth on mahout without closing of the itemsets. For it, I downloaded your source and tried to interpret it and initially i thought that the issue was in FPGrowth.generateSinglePathPatterns() as you are adding the entire conditional FP Tree in the frequentPatterns. For eg: if the conditional fp tree had [f:3 c:3 a:3 m:3], then this method makes the pattern [f,c,a,m | 3] and inserts it into the FrequentPatternMaxHeap. I thought the problem was not generating all the combinations here but it seems that i couldn't able to understand the code correctly. Could you please just lead me to the point(s) or code snippet(s) where the closure is being performed so that i could test on how to remove this closure. Thanks, Aman Frequent Pattern Mining using Parallel FP-Growth Key: MAHOUT-157 URL: https://issues.apache.org/jira/browse/MAHOUT-157 Project: Mahout Issue Type: New Feature Components: Frequent Itemset/Association Rule Mining Affects Versions: 0.2 Reporter: Robin Anil Assignee: Robin Anil Fix For: 0.2 Attachments: MAHOUT-157-August-17.patch, MAHOUT-157-August-24.patch, MAHOUT-157-August-31.patch, MAHOUT-157-August-6.patch, MAHOUT-157-Combinations-BSD-License.patch, MAHOUT-157-Combinations-BSD-License.patch, MAHOUT-157-CompactTransactionMapperFormat.patch, MAHOUT-157-Oct-1.patch, MAHOUT-157-Oct-10.pfpgrowth.patch, MAHOUT-157-Oct-8.TestedMapReducePipeline.patch, MAHOUT-157-Oct-8.pfpgrowth.patch, MAHOUT-157-Oct-9.StreamingDBRead-Inprogress.patch, MAHOUT-157-September-10.patch, MAHOUT-157-September-18.patch, MAHOUT-157-September-5.patch, MAHOUT-157-codecleanup-javadocs.patch, MAHOUT-157-final.patch, MAHOUT-157-inProgress-August-5.patch Implement: http://infolab.stanford.edu/~echang/recsys08-69.pdf -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Welcome Pat Ferrel as new committer on Mahout
Great news, welcome Pat! On Apr 24, 2014, at 3:19 AM, Sebastian Schelter s...@apache.org wrote: Hi, this is to announce that the Project Management Committee (PMC) for Apache Mahout has asked Pat Ferrel to become committer and we are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since in addition to posting patches on JIRA it also gives write access to the code repository. That also means that now we have yet another person who can commit patches submitted by others to our repo *wink* Pat, we look forward to working with you in the future. Welcome! It would be great if you could introduce yourself with a few words. -s
RE: Welcome Pat Ferrel as new committer on Mahout
Congratulations Pat! Subject: Re: Welcome Pat Ferrel as new committer on Mahout From: andrew.mussel...@gmail.com Date: Thu, 24 Apr 2014 06:44:43 -0700 CC: u...@mahout.apache.org To: dev@mahout.apache.org Great news, welcome Pat! On Apr 24, 2014, at 3:19 AM, Sebastian Schelter s...@apache.org wrote: Hi, this is to announce that the Project Management Committee (PMC) for Apache Mahout has asked Pat Ferrel to become committer and we are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since in addition to posting patches on JIRA it also gives write access to the code repository. That also means that now we have yet another person who can commit patches submitted by others to our repo *wink* Pat, we look forward to working with you in the future. Welcome! It would be great if you could introduce yourself with a few words. -s
[jira] [Commented] (MAHOUT-1485) Clean up Recommender Overview page
[ https://issues.apache.org/jira/browse/MAHOUT-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13980045#comment-13980045 ] Yash Sharma commented on MAHOUT-1485: - Have been reading about solr based recommenders. Should the new overview page be based on the code here by Pat : https://github.com/pferrel/solr-recommender/. Also are there any plans of merging this code in mahout as well? Am creating a sample document here and would keep on documenting my findings here: https://docs.google.com/document/d/1iwzcvIbXudSCEZ6n5J5lAhoGGf78Qo9LQsaAvChzMV4/edit I also agree that we should retain the current overview page as well because its a popular implementation and lot of people are using this approach. We can have a new page talking about online recommenders powered with search engines. Clean up Recommender Overview page -- Key: MAHOUT-1485 URL: https://issues.apache.org/jira/browse/MAHOUT-1485 Project: Mahout Issue Type: Improvement Components: Documentation Reporter: Sebastian Schelter Assignee: Sebastian Schelter Fix For: 1.0 Clean up the recommender overview page, remove outdated content and make sure the examples work. https://mahout.apache.org/users/recommender/recommender-documentation.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MAHOUT-1525) train/validateAdaptiveLogistic
Richard Scharrer created MAHOUT-1525: Summary: train/validateAdaptiveLogistic Key: MAHOUT-1525 URL: https://issues.apache.org/jira/browse/MAHOUT-1525 Project: Mahout Issue Type: Question Components: Classification Affects Versions: 0.7 Reporter: Richard Scharrer Hi, I tried to use train- and validateAdaptiveLogistic on my data which is like: category, id, var1, var2, ...var72 (all numeric) I used the following settings: mahout trainAdaptiveLogistic --input resource/trainingData \ --output ./model \ --target category --categories 9 \ --predictors a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 a10 a11 . --types numeric \ --passes 100 \ --showperf \ mahout validateAdaptiveLogistic --input resource/testData --model model --confusion --defaultCategory none The output of validateAdaptiveLogistic is: Log-likelihood:Min=-5.54, Max=-0.04, Mean=-1.58, Median=-1.33 === Confusion Matrix --- a b d e f g h i --Classified as 14 0 0 0 0 0 0 0| 14 a = projekt 0 18 0 0 0 0 0 0| 18 b = news/aktuelles/presse 0 0 24 0 0 0 0 0| 24 d = lehrveranstaltung 0 0 0 19 0 0 0 0| 19 e = publikation 0 0 0 0 20 0 0 0| 20 f = event 0 0 0 0 0 14 0 0| 14 g = mitarbeiter/person 0 0 0 0 0 0 44 0| 44 h = übersicht 0 0 0 0 0 0 0 13 | 13 i = institut (in case you were wondering, the categories a in german) My problem is that this is impossible. I always get a perfect classification even with just a little amount of training data. It doesnt even matter how many features I use I tried it with all 72 and with only one. Am I missing something? Regards, Richard -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MAHOUT-1525) train/validateAdaptiveLogistic
[ https://issues.apache.org/jira/browse/MAHOUT-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13980395#comment-13980395 ] Suneel Marthi commented on MAHOUT-1525: --- You shouldn't be using 0.7, 0.7 has long been retired and is unsupported. Please upgrade to 0.9 or work off of trunk. train/validateAdaptiveLogistic -- Key: MAHOUT-1525 URL: https://issues.apache.org/jira/browse/MAHOUT-1525 Project: Mahout Issue Type: Question Components: Classification Affects Versions: 0.7 Reporter: Richard Scharrer Labels: adaptiveLogisticRegression,, newbie Hi, I tried to use train- and validateAdaptiveLogistic on my data which is like: category, id, var1, var2, ...var72 (all numeric) I used the following settings: mahout trainAdaptiveLogistic --input resource/trainingData \ --output ./model \ --target category --categories 9 \ --predictors a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 a10 a11 . --types numeric \ --passes 100 \ --showperf \ mahout validateAdaptiveLogistic --input resource/testData --model model --confusion --defaultCategory none The output of validateAdaptiveLogistic is: Log-likelihood:Min=-5.54, Max=-0.04, Mean=-1.58, Median=-1.33 === Confusion Matrix --- a b d e f g h i --Classified as 140 0 0 0 0 0 0| 14 a = projekt 0 18 0 0 0 0 0 0| 18 b = news/aktuelles/presse 0 0 24 0 0 0 0 0| 24 d = lehrveranstaltung 0 0 0 19 0 0 0 0| 19 e = publikation 0 0 0 0 20 0 0 0| 20 f = event 0 0 0 0 0 14 0 0| 14 g = mitarbeiter/person 0 0 0 0 0 0 44 0| 44 h = übersicht 0 0 0 0 0 0 0 13 | 13 i = institut (in case you were wondering, the categories a in german) My problem is that this is impossible. I always get a perfect classification even with just a little amount of training data. It doesnt even matter how many features I use I tried it with all 72 and with only one. Am I missing something? Regards, Richard -- This message was sent by Atlassian JIRA (v6.2#6252)
Build failed in Jenkins: Mahout-Quality #2592
See https://builds.apache.org/job/Mahout-Quality/2592/
--
[...truncated 8573 lines...]
36196 [ScalaTest-main-running-RLikeDrmOpsSuite] DEBUG
org.apache.mahout.sparkbindings.drm.decompositions.DQR$ - R=
{
0 = {0:27.313000567495326,1:42.54384270701014}
1 = {1:0.14645040518827934}
}
Q=
{
0 = {0:0.40273861426601687,1:-0.9153150324187648}
1 = {0:0.9153150324227656,1:0.40273861426427493}
}
[32m- C = A %*% B mapBlock {}[0m
[32m- C = A %*% B incompatible B keys[0m
39177 [ScalaTest-main-running-RLikeDrmOpsSuite] DEBUG
org.apache.mahout.sparkbindings.blas.AtB$ - A and B for A'B are not
identically partitioned, performing inner join.
[32m- C = At %*% B , join[0m
40867 [ScalaTest-main-running-RLikeDrmOpsSuite] DEBUG
org.apache.mahout.sparkbindings.blas.AtB$ - A and B for A'B are not
identically partitioned, performing inner join.
[32m- C = At %*% B , join, String-keyed[0m
42502 [ScalaTest-main-running-RLikeDrmOpsSuite] DEBUG
org.apache.mahout.sparkbindings.blas.AtB$ - A and B for A'B are identically
distributed, performing row-wise zip.
[32m- C = At %*% B , zippable, String-keyed[0m
{
2 = {0:62.0,1:86.0,3:132.0,2:115.0}
1 = {0:50.0,1:69.0,3:105.0,2:92.0}
3 = {0:74.0,1:103.0,3:159.0,2:138.0}
0 = {0:26.0,1:35.0,3:51.0,2:46.0}
}
[32m- C = A %*% inCoreB[0m
{
0 = {0:26.0,1:35.0,2:46.0,3:51.0}
1 = {0:50.0,1:69.0,2:92.0,3:105.0}
2 = {0:62.0,1:86.0,2:115.0,3:132.0}
3 = {0:74.0,1:103.0,2:138.0,3:159.0}
}
[32m- C = inCoreA %*%: B[0m
46942 [ScalaTest-main-running-RLikeDrmOpsSuite] DEBUG
org.apache.mahout.sparkbindings.blas.AtA$ - Applying slim A'A.
[32m- C = A.t %*% A[0m
48486 [ScalaTest-main-running-RLikeDrmOpsSuite] DEBUG
org.apache.mahout.sparkbindings.blas.AtA$ - Applying non-slim non-graph A'A.
80788 [ScalaTest-main-running-RLikeDrmOpsSuite] DEBUG
org.apache.mahout.sparkbindings - test done.
[32m- C = A.t %*% A fat non-graph[0m
82049 [ScalaTest-main-running-RLikeDrmOpsSuite] DEBUG
org.apache.mahout.sparkbindings.blas.AtA$ - Applying slim A'A.
[32m- C = A.t %*% A non-int key[0m
[32m- C = A + B[0m
[32m- C = A + B side test 1[0m
[32m- C = A + B side test 2[0m
[32m- C = A + B side test 3[0m
ArrayBuffer(0, 1, 2, 3, 4)
ArrayBuffer(0, 1, 2, 3, 4)
[32m- general side[0m
[32m- Ax[0m
[32m- A'x[0m
[32m- colSums, colMeans[0m
[36mRun completed in 1 minute, 43 seconds.[0m
[36mTotal number of tests run: 38[0m
[36mSuites: completed 9, aborted 0[0m
[36mTests: succeeded 38, failed 0, canceled 0, ignored 0, pending 0[0m
[32mAll tests passed.[0m
[INFO]
[INFO] --- build-helper-maven-plugin:1.8:remove-project-artifact
(remove-old-mahout-artifacts) @ mahout-spark ---
[INFO] /home/jenkins/.m2/repository/org/apache/mahout/mahout-spark removed.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ mahout-spark ---
[INFO] Building jar:
https://builds.apache.org/job/Mahout-Quality/2592/artifact/trunk/spark/target/mahout-spark-1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ mahout-spark ---
[INFO] Building jar:
https://builds.apache.org/job/Mahout-Quality/2592/artifact/trunk/spark/target/mahout-spark-1.0-SNAPSHOT-tests.jar
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources) @
mahout-spark ---
[INFO] Building jar:
https://builds.apache.org/job/Mahout-Quality/2592/artifact/trunk/spark/target/mahout-spark-1.0-SNAPSHOT-sources.jar
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ mahout-spark
---
[INFO] Installing
https://builds.apache.org/job/Mahout-Quality/2592/artifact/trunk/spark/target/mahout-spark-1.0-SNAPSHOT.jar
to
/home/jenkins/.m2/repository/org/apache/mahout/mahout-spark/1.0-SNAPSHOT/mahout-spark-1.0-SNAPSHOT.jar
[INFO] Installing
https://builds.apache.org/job/Mahout-Quality/ws/trunk/spark/pom.xml to
/home/jenkins/.m2/repository/org/apache/mahout/mahout-spark/1.0-SNAPSHOT/mahout-spark-1.0-SNAPSHOT.pom
[INFO] Installing
https://builds.apache.org/job/Mahout-Quality/2592/artifact/trunk/spark/target/mahout-spark-1.0-SNAPSHOT-tests.jar
to
/home/jenkins/.m2/repository/org/apache/mahout/mahout-spark/1.0-SNAPSHOT/mahout-spark-1.0-SNAPSHOT-tests.jar
[INFO] Installing
https://builds.apache.org/job/Mahout-Quality/2592/artifact/trunk/spark/target/mahout-spark-1.0-SNAPSHOT-sources.jar
to
/home/jenkins/.m2/repository/org/apache/mahout/mahout-spark/1.0-SNAPSHOT/mahout-spark-1.0-SNAPSHOT-sources.jar
[INFO]
[INFO] maven-javadoc-plugin:2.9.1:javadoc (default-cli) @ mahout-spark
[INFO]
[INFO] --- build-helper-maven-plugin:1.8:add-source (add-source) @ mahout-spark
---
[INFO] Source directory:
https://builds.apache.org/job/Mahout-Quality/ws/trunk/spark/target/generated-sources/mahout
added.
[INFO]
[INFO] --- build-helper-maven-plugin:1.8:add-test-source (add-test-source) @
mahout-spark ---
[INFO] Test Source directory:
https://builds.apache.org/job/Mahout-Quality/ws/trunk/spark/target/generated-test-sources/mahout
