Re: [DISCUSS] Release 14.1, RC7

Still haven’t had a chance to test since it will take some experimentation to figure out jars needed etc. My test is to replace 0.13 with 0.14.1 Still I see no reason to delay the release for my slow testing +1 From: Andrew Musselman Reply: dev@mahout.apache.org Date: September 28, 2020 at

Re: [ANNOUNCE] Mahout Con 2020 (A sub-track of ApacheCon @ Home)

Big fun. Thanks for putting this together. I’ll abuse my few Twitter followers with the announcement. From: Trevor Grant Reply: u...@mahout.apache.org Date: August 12, 2020 at 5:59:45 AM To: Mahout Dev List , u...@mahout.apache.org Subject:  [ANNOUNCE] Mahout Con 2020 (A sub-track of

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

+1 From: Apache Mahout Reply: dev@mahout.apache.org Date: January 3, 2019 at 11:53:02 AM To: dev Subject:  Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org  On Thu, 3 Jan 2019 13:51:40 -0600, dev wrote: Cool, just making sure we needed it. On Thu, Jan 3,

[jira] [Created] (MAHOUT-2048) There are duplicate content pages which need redirects instead

Pat Ferrel created MAHOUT-2048: -- Summary: There are duplicate content pages which need redirects instead Key: MAHOUT-2048 URL: https://issues.apache.org/jira/browse/MAHOUT-2048 Project: Mahout

Users of Scala 2.11

Hi all, Mahout has hit a bit of a bump in releasing a Scala 2.11 version. I was able to build 0.13.0 for Scala 2.11 and have published it on github as a Maven compatible repo. I’m also using it from SBT. If anyone wants access let me know.

Re: Spark 2.x/scala 2.11.x release

evor Grant <trevor.d.gr...@gmail.com> > Sent: Friday, March 2, 2018 5:15:35 PM > To: Mahout Dev List > Subject: Re: Spark 2.x/scala 2.11.x release > > The only "mess" is in the cli spark drivers, namely scopt. > > Get rid of the drivers/fix the scopt issue- we

Re: Spark 2.x/scala 2.11.x release

e cli spark drivers, namely scopt. > > Get rid of the drivers/fix the scopt issue- we have no mess. > > > > On Mar 2, 2018 4:09 PM, "Pat Ferrel" <p...@occamsmachete.com> wrote: > > > BTW the mess master is in is why git flow was invented and why I asked &

Re: Spark 2.x/scala 2.11.x release

t; > - Cherrypick any commits that we'd like to release (E.g.: SparseSpeedup) > onto `develop` (along with a PR ad a ticket). > > > - Merge `develop` to `master`, run through Smoke tests, tag master @ > `mahout-0.13.1`(automatically), and release. > > > This will also ge

Re: Spark 2.x/scala 2.11.x release

r`, run through Smoke tests, tag master @ > `mahout-0.13.1`(automatically), and release. > > > This will also get us to more of a git-flow workflow, as we've discussed > moving towards. > > > Thoughts @all? > > > --andy > > > > > > > _

Re: Spark 2.x/scala 2.11.x release

big +1 If you are planning to branch off the 0.13.0 tag let me know, I have a speedup that is in my scala 2.11 fork of 0.13.0 that needs to be released From: Andrew Palumbo Reply: dev@mahout.apache.org

Re: New Website

ate the vote on the logo and the site. Sent from my Verizon Wireless 4G LTE smartphone Original message -------- From: Pat Ferrel <p...@occamsmachete.com> Date: 12/13/2017 09:47 (GMT-08:00) To: dev@mahout.apache.org Subject: Re: New Website Due to 8 years of Ruby cruft I can’t get the Je

Re: New Website

<https://sarcasticresonance.files.wordpress.com/2017/01/cubes1.png?w=721=2> On Dec 6, 2017, at 11:27 AM, Pat Ferrel <p...@occamsmachete.com> wrote: Since you’ve already built it can you share a screen shot? The mockup I saw on Slack looked awesome. Also a logo change is a lot more far reaching so can we have

Re: New Website

Since you’ve already built it can you share a screen shot? The mockup I saw on Slack looked awesome. Also a logo change is a lot more far reaching so can we have at least a little discussion? On Dec 6, 2017, at 10:18 AM, Andrew Musselman wrote: +1, looks great

Re: Prepping Release

https://issues.apache.org/jira/browse/MAHOUT-2023 is the only blocker I see. It’s a big one since it make drivers and GPU bindings not work in clusters (I think). But the fix is probably easy. On Nov 27, 2017, at 8:06 AM, Jim Jagielski

[jira] [Created] (MAHOUT-2023) Drivers broken, scopt classes not found

Pat Ferrel created MAHOUT-2023: -- Summary: Drivers broken, scopt classes not found Key: MAHOUT-2023 URL: https://issues.apache.org/jira/browse/MAHOUT-2023 Project: Mahout Issue Type: Bug

[jira] [Created] (MAHOUT-2020) Maven repo structure compatibility with SBT

Pat Ferrel created MAHOUT-2020: -- Summary: Maven repo structure compatibility with SBT Key: MAHOUT-2020 URL: https://issues.apache.org/jira/browse/MAHOUT-2020 Project: Mahout Issue Type: Bug

[jira] [Created] (MAHOUT-2019) SparseRowMatrix assign ops user for loops instead of iterateNonZero and so can be optimized

Pat Ferrel created MAHOUT-2019: -- Summary: SparseRowMatrix assign ops user for loops instead of iterateNonZero and so can be optimized Key: MAHOUT-2019 URL: https://issues.apache.org/jira/browse/MAHOUT-2019

Re: [DISCUSS] Naming convention for multiple spark/scala combos

IIRC these all fit sbt’s conventons? On Jul 7, 2017, at 2:05 PM, Trevor Grant wrote: So to tie all of this together- org.apache.mahout:mahout-spark_2.10:0.13.1_spark_1_6 org.apache.mahout:mahout-spark_2.10:0.13.1_spark_2_0

Re: [DISCUSS] New mailing list for JIRA

Other project I’ve seen funnel all github, Jira, and Jenkins emails to one place so actual discussions are easier to notice in @dev +1 to moving elsewhere On Jun 24, 2017, at 5:23 AM, Trevor Grant wrote: Can we create a new mailing list like j...@mahout.apache.org

Re: Proposal for changing Mahout's Git branching rules

hich will result to high > contribtors' attrition, or resolve them yourself without deep knowledge of > the author's intent, which will result in delays and plain errors. > > On Thu, Jun 22, 2017 at 2:48 PM, Dmitriy Lyubimov <dlie...@gmail.com> > wrote: > >>

Re: Proposal for changing Mahout's Git branching rules

And all this leads me to think that the concerns/worries may not really be warranted, this process just codifies best practices and adds one new thing, which is “develop’ as the default WIP branch. On Jun 22, 2017, at 10:47 AM, Pat Ferrel <p...@occamsmachete.com> wrote: Which tran

Re: Proposal for changing Mahout's Git branching rules

Which translates into exactly what you suggest if we are maintaining release branches. On Jun 22, 2017, at 10:45 AM, Pat Ferrel <p...@occamsmachete.com> wrote: Actually I think git flow would merge it into master and tag it with an annotated tag like “0.13.0.jira-123” to reference the b

Re: Proposal for changing Mahout's Git branching rules

t;dlie...@gmail.com> wrote: > PS. but i see the rational. to have stable fixes to get into release. > perhaps named release branches is still a way to go if one cuts them early > enough. > > On Wed, Jun 21, 2017 at 2:25 PM, Dmitriy Lyubimov <dlie...@gmail.com> > wrote: >

Re: Proposal for changing Mahout's Git branching rules

s to develop instead of master? Do they need to PR against develop branch, and if not, who is responsible for confict resolution then that is to arise from diffing and merging into different targets? On Tue, Jun 20, 2017 at 10:09 AM, Pat Ferrel <p...@actionml.com> wrote: > As I said I

Re: Proposal for changing Mahout's Git branching rules

wrote: so people need to make sure their PR merges to develop instead of master? Do they need to PR against develop branch, and if not, who is responsible for confict resolution then that is to arise from diffing and merging into different targets? On Tue, Jun 20, 2017 at 10:09 AM, Pat Fer

Re: new committer: Dustin Vanstee

Welcome Dustin! Nice work so far, much needed. On Jun 21, 2017, at 12:08 PM, Andrew Palumbo wrote: Welcome Dustin! Sent from my Verizon Wireless 4G LTE smartphone Original message From: Andrew Musselman Date: 06/20/2017

Re: Proposal for changing Mahout's Git branching rules

branches that are created and ephemeral with this method. On Jun 19, 2017, at 5:52 PM, Pat Ferrel <p...@occamsmachete.com> wrote: I just heard we are not using git flow (the process not the tool), we are checking unclean (untested in any significant way) changes to master

Re: Proposal for changing Mahout's Git branching rules

l.com> > wrote: > > Cool, I'll make a new dev branch now. > > Dev, develop, any preference? > > On Sat, Apr 22, 2017 at 10:30 AM, Pat Ferrel <p...@occamsmachete.com> > wrote: > >> It hasn't been often but I’ve been bit by it and had to ask users of a >

[jira] [Updated] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1951: --- The jar isn't supposed to have all deps, only the ones not provided by the environment. In fact

[jira] [Commented] (MAHOUT-1988) scala 2.10 is hardcoded somewhere

[ https://issues.apache.org/jira/browse/MAHOUT-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16037567#comment-16037567 ] Pat Ferrel commented on MAHOUT-1988: Don't have time to look now but believe Scopt may hardcode 2.10

Re: LLR thresholds

correlation tests that would not be onerous given small dimensionality and more dense data? On Mar 8, 2017, at 5:22 PM, Pat Ferrel <p...@occamsmachete.com> wrote: Couldn’t agree more and I was arguing this below. To illustrate the issue I’m thinking about let’s use an extreme ecom case

Re: GitHub primary repo

72hour lazy consensus if not an all out vote first. In general I like it though On May 18, 2017 5:15 PM, "Pat Ferrel" <p...@occamsmachete.com> wrote: > Ok, is there a catch? Why would we not do this? > > If someone wants to talk about GH going down, I’d still take the r

Re: GitHub primary repo

d turn on two-factor authentication. and talk to infra Trevor Grant Data Scientist https://github.com/rawkintrevo http://stackexchange.com/users/3002022/rawkintrevo http://trevorgrant.org *"Fortunate is he, who is able to know the causes of things." -Virgil* On Thu, May 18, 2017

Re: GitHub primary repo

What, actual hosting on GH so merging PRs and reviewing with the GUI? This would open up a whole new toolchain, +1 I’ll write that Jira if that’s what you mean. BTW github is mirroring the ASF git server, not svn afaik. On May 17, 2017, at 7:39 AM, Trevor Grant

Re: Website Incident

+1, headline: "A serendipitous mistake leads to fast action at Mahout” We now know Trevor is a webdev god :-) On May 13, 2017, at 8:21 AM, Andrew Musselman wrote: Trevor, thanks for the late night repairing things; I'm a +1 and will scrub this weekend for any

Re: New Website is Staged

Are you guys ready for serious comments on the new design or is this just a first running version? On May 9, 2017, at 8:20 AM, Trevor Grant wrote: In the interest of getting this thing up and running, use DFW Meetup video as a place holder for time being? Trevor

Re: New logo

nterlocking solid yellow/blue background 3rd is simple letter M as wireframe but prefer the diagram be in yellow. I don't care for the loopy curved logos (sorry Andrew!) Good luck!! Ellen Friedman On Thu, Apr 27, 2017 at 12:56 PM, Pat Ferrel <p...@occamsmachete.com <mailto:p...@occ

Re: New logo

hu, Apr 27, 2017 at 5:54 PM, Pat Ferrel <p...@occamsmachete.com> wrote: > Fair enough, I think Trevor feels the same. > > The blue man can continue, all it takes is a -1 > > > On Apr 27, 2017, at 3:50 PM, Ted Dunning <ted.dunn...@gmail.com> wrote: > &

Re: New logo

uggest a better path and I hate negative feedback. But there it is. On Thu, Apr 27, 2017 at 3:48 PM, Pat Ferrel <p...@occamsmachete.com> wrote: > Do you have constructive input (guidance or opinion is welcome input) or > would you like to discontinue the contest. If the later, -1 now. >

Re: New logo

Apr 27, 2017 at 3:36 PM, Pat Ferrel <p...@occamsmachete.com> wrote: > Yes, -1 means you hate them all or think the designers are not worth > paying. We have to pay to continue, I’ll foot the bill (donations > appreciated) but don’t want to unless people think it will lead t

Re: New logo

ments/84/84017/attachment_84017937 >> >> I like the stylized and simple "M" and it reminds me of diagrams showing >> vector multiplication. >> >> On Thu, Apr 27, 2017 at 12:56 PM, Pat Ferrel <p...@occamsmachete.com> >> wrote: >> >>> We

Re: New logo

you have 24 hours to vote Here’s my +1 to continue refining. On Apr 27, 2017, at 11:41 AM, Pat Ferrel <p...@occamsmachete.com> wrote: Here is a second group, hopefully picked to be unique.https://99designs.com/contests/poll/vl7xed We got a lot of responses, these 2 polls contain th

Re: New logo

Here is a second group, hopefully picked to be unique.https://99designs.com/contests/poll/vl7xed We got a lot of responses, these 2 polls contain the best afaict. On Apr 27, 2017, at 11:25 AM, Pat Ferrel <p...@occamsmachete.com> wrote: Vote: https://99designs.com/contests/poll/rqcg

New logo

Vote: https://99designs.com/contests/poll/rqcgif We asked for something “mathy” and asked for no elephant and rider. We have the rest of the week to tweak so leave comments about what you like or would like to change. We don’t have to pick one of these, so if you hate them all, make that known

New site and logo

The Mahout site is moving to Jekyll with a bit if a new look and so it might be nice to get an update of the logo. I think the consensus was to keep the Mahout name but I didn’t get a feel for the logo. One concern mentioned is that Mahout is no longer attached to Hadoop (the elephant) so

Re: Proposal for changing Mahout's Git branching rules

er/dev branch approach is solid. On Sat, Apr 22, 2017 at 10:06 AM, Pat Ferrel <p...@occamsmachete.com> wrote: > I’ve been introduced to what is now being called git-flow, which at it’s > simplest is just a branching strategy with several key benefits. The most > important part of

Proposal for changing Mahout's Git branching rules

I’ve been introduced to what is now being called git-flow, which at it’s simplest is just a branching strategy with several key benefits. The most important part of it is that the master branch is rock solid all the time because we use the “develop” branch for integrating Jiras, PRs, features,

Re: Marketing

2017 7:22 PM (GMT-08:00) To: u...@mahout.apache.org Cc: Mahout Dev List <dev@mahout.apache.org> Subject: Re: Marketing On Fri, Mar 24, 2017 at 8:27 AM, Pat Ferrel <p...@occamsmachete.com> wrote: > maybe we should drop the name Mahout altogether. I have been told that there is a co

Re: Marketing

o:smar...@apache.org] > Sent: Friday, March 24, 2017 11:13 AM > To: mahout <dev@mahout.apache.org> > Cc: u...@mahout.apache.org > Subject: Re: Marketing > > On Fri, Mar 24, 2017 at 12:09 PM, Dmitriy Lyubimov <dlie...@gmail.com> > wrote: > >> On Fri, Ma

Re: Marketing

." -Virgil* On Thu, Mar 23, 2017 at 5:43 PM, Pat Ferrel <p...@occamsmachete.com> wrote: > The little blue man (the mahout) was reborn (samsara) as a honey-badger? > He must be close indeed to reaching true enlightenment, or is that Buddhism? > > > On Mar 23, 2017, at

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

I can’t +1 because of system integration errors that have to do with scoring that could be in Mahout. I doubt it is but don’t have time in the allotted vote period to track it down. My close looking tests of Mahout including the previous driver issues pass. Not sure if we use this style of

Re: Marketing

The little blue man (the mahout) was reborn (samsara) as a honey-badger? He must be close indeed to reaching true enlightenment, or is that Buddhism? On Mar 23, 2017, at 12:42 PM, Andrew Palumbo wrote: +1 on revamp. Sent from my Verizon Wireless 4G LTE smartphone

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

Before voting I’d like to run down the integration errors, which are different recs scores and could theoretically be because of different math results. On Mar 23, 2017, at 3:34 PM, Pat Ferrel <p...@occamsmachete.com> wrote: BTW I’m getting bad integration test results, which are pr

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

BTW I’m getting bad integration test results, which are probably not related to what Mahout does since the math is tested in unit tests too. But the test runs with no runtime errors, Mahout as a Lib and drivers On Mar 23, 2017, at 3:32 PM, Pat Ferrel <p...@occamsmachete.com> wrote:

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

ess 4G LTE smartphone Original message From: Pat Ferrel <p...@occamsmachete.com> Date: 03/23/2017 3:05 PM (GMT-08:00) To: dev@mahout.apache.org Subject: Re: [VOTE] Apache Mahout 0.13.0 Release Candidate using the repo build of mahout I get all sorts of errors like

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

using the repo build of mahout I get all sorts of errors like this: [INFO] [RootSolverFactory$] Unable to create class GPUMMul: attempting OpenMP version [INFO] [RootSolverFactory$] Creating org.apache.mahout.viennacl.openmp.OMPMMul solver [INFO] [RootSolverFactory$]

Re: New RC?

Makes sense to me, I can’t test the 2 GPU versions. If 0.13.0 that is java only do we have an RC or code freeze to test? On Mar 18, 2017, at 1:43 PM, Andrew Palumbo wrote: Or rather if you're both in favor of it.. get the source/java only version out as 0.13.0 and follow

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

OK, my tests passed including the last blocker, will test again on the new RC. On Mar 16, 2017, at 8:56 AM, Andrew Musselman wrote: Cancelling vote due to https://issues.apache.org/jira/browse/MAHOUT-1955 On Wed, Mar 15, 2017 at 8:55 AM, Andrew Musselman <

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

The release was not made due to broken drivers, now fixed. I assume a new RC will come shortly? On Mar 11, 2017, at 9:54 PM, Andrew Musselman wrote: This is the vote for release 0.13.0 of Apache Mahout. The vote will be going for at least 72 hours and will be closed on

[jira] [Commented] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903739#comment-15903739 ] Pat Ferrel commented on MAHOUT-1951: Oops misnamed the commit message for MAHOUT-1950. The fix

[jira] [Resolved] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel resolved MAHOUT-1951. Resolution: Fixed Test thoroughly, not sure of side effects of the fix > Drivers don't

[jira] [Commented] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903327#comment-15903327 ] Pat Ferrel commented on MAHOUT-1951: [~Andrew_Palumbo] [~smarthi] There seems to be some question

[jira] [Commented] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903320#comment-15903320 ] Pat Ferrel commented on MAHOUT-1951: A quick way to test this is: 1) get Spark and HDFS running

[jira] [Commented] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903315#comment-15903315 ] Pat Ferrel commented on MAHOUT-1951: scratch that PR. We do not have a fix for this but I have

Re: LLR thresholds

d hits in the results page. On Wed, Mar 8, 2017 at 8:18 AM, Pat Ferrel <p...@occamsmachete.com> wrote: > The CCO algorithm now supports a couple ways to limit indicators by > “quality". The new way is by the value of LLR. We built a t-digest > mechanism to look at th

LLR thresholds

The CCO algorithm now supports a couple ways to limit indicators by “quality". The new way is by the value of LLR. We built a t-digest mechanism to look at the overall density produced with different thresholds. The higher the threshold, the lower the number of indicators and the lower the

[jira] [Commented] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897636#comment-15897636 ] Pat Ferrel commented on MAHOUT-1951: fix being tested in https://github.com/apache/mahout/pull/292

[jira] [Created] (MAHOUT-1952) Allow pass-through of params for driver's CLI to spark-submit

Pat Ferrel created MAHOUT-1952: -- Summary: Allow pass-through of params for driver's CLI to spark-submit Key: MAHOUT-1952 URL: https://issues.apache.org/jira/browse/MAHOUT-1952 Project: Mahout

[jira] [Updated] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1951: --- Component/s: Collaborative Filtering Classification > Drivers don't run with rem

[jira] [Commented] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897625#comment-15897625 ] Pat Ferrel commented on MAHOUT-1951: [~rawkintrevo] added the use of spark-submit to the Mahout

[jira] [Updated] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1951: --- User found the following error running the spark-itemsimilarity driver (affect the NB driver too

[jira] [Created] (MAHOUT-1951) Drivers don't run with remote Spark

Pat Ferrel created MAHOUT-1951: -- Summary: Drivers don't run with remote Spark Key: MAHOUT-1951 URL: https://issues.apache.org/jira/browse/MAHOUT-1951 Project: Mahout Issue Type: Bug

[jira] [Updated] (MAHOUT-1951) Drivers don't run with remote Spark

[ https://issues.apache.org/jira/browse/MAHOUT-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1951: --- Sprint: Jan/Feb-2017 > Drivers don't run with remote Sp

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

scratch that, anyone using sbt use the following resolver: resolvers += “Apache Staging" at "https://repository.apache.org/content/repositories/orgapachemahout-1034 <https://repository.apache.org/content/repositories/orgapachemahout-1034>” On Mar 3, 2017, at 10:41 A

Re: [VOTE] Apache Mahout 0.13.0 Release Candidate

My first observation is that the typical way to release Scala libs is with multiple versions for the currently popular Scalas. Akka for instance is not stable with Scala 2.10 anymore so consider it deprecated and it is the core of Spark. Many libs release 2.10 and 2.11 versions of binaries with

[jira] [Updated] (MAHOUT-1940) Provide a Java API to SimilarityAnalysis and any other needed APIs

[ https://issues.apache.org/jira/browse/MAHOUT-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1940: --- Description: We want to port the functionality from

[jira] [Updated] (MAHOUT-1940) Provide a Java API to SimilarityAnalysis and any other needed APIs

[ https://issues.apache.org/jira/browse/MAHOUT-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1940: --- Summary: Provide a Java API to SimilarityAnalysis and any other needed APIs (was: Implementing

[jira] [Commented] (MAHOUT-1940) Implementing similarity analysis using co-occurence matrix in java

[ https://issues.apache.org/jira/browse/MAHOUT-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862862#comment-15862862 ] Pat Ferrel commented on MAHOUT-1940: This would be Awesome! Let me know if you need help

[jira] [Commented] (MAHOUT-1904) Create a test harness to test mahout across different hardware configurations

[ https://issues.apache.org/jira/browse/MAHOUT-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822907#comment-15822907 ] Pat Ferrel commented on MAHOUT-1904: Did you have in mind a CLI tool or unit test? I assume

[jira] [Updated] (MAHOUT-1904) Create a test harness to test mahout across different hardware configurations

[ https://issues.apache.org/jira/browse/MAHOUT-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1904: --- Affects Version/s: (was: 0.12.2) 0.14.0 > Create a test harness to t

[jira] [Commented] (MAHOUT-1882) SequentialAccessSparseVector inerateNonZeros is incorrect.

[ https://issues.apache.org/jira/browse/MAHOUT-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812561#comment-15812561 ] Pat Ferrel commented on MAHOUT-1882: Can't see that I use this, at least not obviously unless

[jira] [Commented] (MAHOUT-1786) Make classes implements Serializable for Spark 1.5+

[ https://issues.apache.org/jira/browse/MAHOUT-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15761631#comment-15761631 ] Pat Ferrel commented on MAHOUT-1786: It sounds like we could remove Kryo altogether and improve

Git branching policy

I have changes in the master that are needed for some users of Mahout. However the master is often chaotic due to being the branch that is the SNAPSHOT of all partial or not well tested changes. The key feature of the branching model described in the blog is that master is stable and contains

using root LLR

around 20-30 for raw LLR which corresponds to about 5 for root LLR. I often eyeball the lists of indicators for items that I understand to find a point where the list of indicators becomes about half noise, half useful indicators. On Sat, Jan 2, 2016 at 2:15 PM, Pat Ferrel <p...@occamsmachete

[jira] [Resolved] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel resolved MAHOUT-1853. Resolution: Fixed > Improvements to CCO (Correlated Cross-Occurre

[jira] [Resolved] (MAHOUT-1883) Create a type if IndexedDataset that filters unneeded data for CCO

[ https://issues.apache.org/jira/browse/MAHOUT-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel resolved MAHOUT-1883. Resolution: Fixed Hmm, I thought these were aut-resolved with a commit that contains the issue

[jira] [Updated] (MAHOUT-1883) Create a type if IndexedDataset that filters unneeded data for CCO

[ https://issues.apache.org/jira/browse/MAHOUT-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1883: --- Issue Type: New Feature (was: Bug) > Create a type if IndexedDataset that filters unneeded d

[jira] [Updated] (MAHOUT-1883) Create a type if IndexedDataset that filters unneeded data for CCO

[ https://issues.apache.org/jira/browse/MAHOUT-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1883: --- Sprint: Jan/Feb-2016 > Create a type if IndexedDataset that filters unneeded data for

[jira] [Updated] (MAHOUT-1883) Create a type if IndexedDataset that filters unneeded data for CCO

[ https://issues.apache.org/jira/browse/MAHOUT-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1883: --- Description: The collaborative filtering CCO algo uses drms for each "indicator" type.

[jira] [Created] (MAHOUT-1883) Create a type if IndexedDataset that filters unneeded data for CCO

Pat Ferrel created MAHOUT-1883: -- Summary: Create a type if IndexedDataset that filters unneeded data for CCO Key: MAHOUT-1883 URL: https://issues.apache.org/jira/browse/MAHOUT-1883 Project: Mahout

Recommenders and MABs

I’ve been thinking about how one would implement an application that only shows recommendations. This is partly because people want to build such things. There are many problems with this including cold start and overfit. However these problems also face MABs and are solved with sampling

[jira] [Commented] (MAHOUT-1878) implement quartile type thresholds for indicator matrix downsampling

[ https://issues.apache.org/jira/browse/MAHOUT-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429553#comment-15429553 ] Pat Ferrel commented on MAHOUT-1878: see discussion here https://issues.apache.org/jira/browse/MAHOUT

[jira] [Issue Comment Deleted] (MAHOUT-1679) example script run-item-sim should work on hdfs as well as local

[ https://issues.apache.org/jira/browse/MAHOUT-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1679: --- Comment: was deleted (was: see discussion https://issues.apache.org/jira/browse/MAHOUT-1853

[jira] [Commented] (MAHOUT-1679) example script run-item-sim should work on hdfs as well as local

[ https://issues.apache.org/jira/browse/MAHOUT-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429552#comment-15429552 ] Pat Ferrel commented on MAHOUT-1679: see discussion https://issues.apache.org/jira/browse/MAHOUT-1853

[jira] [Created] (MAHOUT-1878) implement quartile type thresholds for indicator matrix downsampling

Pat Ferrel created MAHOUT-1878: -- Summary: implement quartile type thresholds for indicator matrix downsampling Key: MAHOUT-1878 URL: https://issues.apache.org/jira/browse/MAHOUT-1878 Project: Mahout

[jira] [Commented] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429550#comment-15429550 ] Pat Ferrel commented on MAHOUT-1853: ok first part implemented. Not sure Ted's suggestion will get

[jira] [Commented] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409595#comment-15409595 ] Pat Ferrel commented on MAHOUT-1853: Great, that's what I wanted to hear. Normal in principal

[jira] [Commented] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408326#comment-15408326 ] Pat Ferrel commented on MAHOUT-1853: If t-digest is more tolerant of "not having enough data&

[jira] [Commented] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408256#comment-15408256 ] Pat Ferrel commented on MAHOUT-1853: is rootLLR normally distributed (the positive half)? If so we'd

[jira] [Updated] (MAHOUT-1853) Improvements to CCO (Correlated Cross-Occurrence)

[ https://issues.apache.org/jira/browse/MAHOUT-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pat Ferrel updated MAHOUT-1853: --- Sprint: Jan/Feb-2016 > Improvements to CCO (Correlated Cross-Occurre

  1   2   3   4   5   6   7   8   9   >