[ 
https://issues.apache.org/jira/browse/SPARK-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mike Beyer reopened SPARK-4900:
-------------------------------

i traced the problem back due to Double.NaN, Double.POSITIVE_INFINITY or  
Double.NEGATIVE_INFINITY values of the java double values. In my opinion the 
user should care to have not such values in the data, but when an exception is 
thrown it should give a hint that this is a likely cause. If also other 
allgorithms in MLLib are not pretecting against failing due to Double.NaN, 
Double.POSITIVE_INFINITY or  Double.NEGATIVE_INFINITY it should be mentioned in 
the MLlib doc that the users has to ensure only proper double numbers.

> MLlib SingularValueDecomposition ARPACK IllegalStateException 
> --------------------------------------------------------------
>
>                 Key: SPARK-4900
>                 URL: https://issues.apache.org/jira/browse/SPARK-4900
>             Project: Spark
>          Issue Type: Bug
>          Components: MLlib
>    Affects Versions: 1.1.1, 1.2.0, 1.2.1
>         Environment: Ubuntu 1410, Java HotSpot(TM) 64-Bit Server VM (build 
> 25.25-b02, mixed mode)
> spark local mode
>            Reporter: Mike Beyer
>            Assignee: Sean Owen
>             Fix For: 1.3.0
>
>
> java.lang.reflect.InvocationTargetException
>         ...
> Caused by: java.lang.IllegalStateException: ARPACK returns non-zero info = 3 
> Please refer ARPACK user guide for error message.
>         at 
> org.apache.spark.mllib.linalg.EigenValueDecomposition$.symmetricEigs(EigenValueDecomposition.scala:120)
>         at 
> org.apache.spark.mllib.linalg.distributed.RowMatrix.computeSVD(RowMatrix.scala:235)
>         at 
> org.apache.spark.mllib.linalg.distributed.RowMatrix.computeSVD(RowMatrix.scala:171)
>               ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to