[ 
https://issues.apache.org/jira/browse/MAHOUT-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123652#comment-13123652
 ] 

Dan Brickley commented on MAHOUT-792:
-------------------------------------

Looking to try this, I tried applying the last patch per 
https://cwiki.apache.org/MAHOUT/how-to-contribute.html#HowToContribute-Applyingapatch
  i.e. 'patch -p 0 -i MAHOUT-792.patch', and get a pile of 'Reversed (or 
previously applied) patch detected' and a 'can't find file to patch'. Is some 
but not all of this now committed? 

Per "Github branch MAHOUT-792 available at 
git://github.com/tdunning/mahout.git"  I'm looking around 
https://github.com/tdunning/mahout but there's no branch listed of that name.  
Presumably https://github.com/tdunning/mahout/tree/new-stochastic is the place 
to go?

                
> Add new stochastic decomposition code
> -------------------------------------
>
>                 Key: MAHOUT-792
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-792
>             Project: Mahout
>          Issue Type: New Feature
>            Reporter: Ted Dunning
>         Attachments: MAHOUT-792.patch, MAHOUT-792.patch, sd-2.pdf
>
>
> I have figured out some simplification for our SSVD algorithms.  This 
> eliminates the QR decomposition and makes life easier.
> I will produce a patch that contains the following:
>   - a CholeskyDecomposition implementation that does pivoting (and thus 
> rank-revealing) or not.  This should actually be useful for solution of large 
> out-of-core least squares problems.
>   - an in-memory SSVD implementation that should work for matrices up to 
> about 1/3 of available memory.
>   - an out-of-core SSVD threaded implementation that should work for very 
> large matrices.  It should take time about equal to the cost of reading the 
> input matrix 4 times and will require working disk roughly equal to the size 
> of the input.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to