You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Arne Plöse (JIRA)" <ji...@apache.org> on 2011/07/21 11:32:57 UTC

[jira] [Created] (MATH-626) Move RealVector.sparseIterator() to SparseRealVector

Move RealVector.sparseIterator() to   SparseRealVector
------------------------------------------------------

                 Key: MATH-626
                 URL: https://issues.apache.org/jira/browse/MATH-626
             Project: Commons Math
          Issue Type: Improvement
    Affects Versions: 3.0
            Reporter: Arne Plöse
            Priority: Minor


Having this method available for all is not very efficient, because if I want use this feature I must check for interface SparseRealVector.
otherwise different implementations could be faster. 
I.e. no array clone and the assigning all values again.
Maybe one could add a menthod fillstate() to SparseRealVector to guide which is faster - use array clone and then sparseIterator or just create the array and then fill it up.

To reduce confusion a second Interface ArrayRealVector with the method getDataRef() and removing getData() from RealVector would be nice - there is a toArray() this should be sufficient. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (MATH-626) Move RealVector.sparseIterator() to SparseRealVector

Posted by "Gilles (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MATH-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082299#comment-13082299 ] 

Gilles commented on MATH-626:
-----------------------------

Wouldn't it be an incompatible change? I'm referring to the title of this issue, not the various other suggestions that should have been in their own JIRA requests.


> Move RealVector.sparseIterator() to   SparseRealVector
> ------------------------------------------------------
>
>                 Key: MATH-626
>                 URL: https://issues.apache.org/jira/browse/MATH-626
>             Project: Commons Math
>          Issue Type: Improvement
>            Reporter: Arne Plöse
>            Priority: Minor
>             Fix For: 3.1
>
>
> Having this method available for all is not very efficient, because if I want use this feature I must check for interface SparseRealVector.
> otherwise different implementations could be faster. 
> I.e. no array clone and the assigning all values again.
> Maybe one could add a menthod fillstate() to SparseRealVector to guide which is faster - use array clone and then sparseIterator or just create the array and then fill it up.
> To reduce confusion a second Interface ArrayRealVector with the method getDataRef() and removing getData() from RealVector would be nice - there is a toArray() this should be sufficient. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (MATH-626) Move RealVector.sparseIterator() to SparseRealVector

Posted by "Sébastien Brisard (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MATH-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425545#comment-13425545 ] 

Sébastien Brisard commented on MATH-626:
----------------------------------------

See also this recent [discussion|http://markmail.org/thread/l5d3f2ap4apjukbk].
                
> Move RealVector.sparseIterator() to   SparseRealVector
> ------------------------------------------------------
>
>                 Key: MATH-626
>                 URL: https://issues.apache.org/jira/browse/MATH-626
>             Project: Commons Math
>          Issue Type: Improvement
>            Reporter: Arne Plöse
>            Priority: Minor
>             Fix For: 4.0
>
>
> Having this method available for all is not very efficient, because if I want use this feature I must check for interface SparseRealVector.
> otherwise different implementations could be faster. 
> I.e. no array clone and the assigning all values again.
> Maybe one could add a menthod fillstate() to SparseRealVector to guide which is faster - use array clone and then sparseIterator or just create the array and then fill it up.
> To reduce confusion a second Interface ArrayRealVector with the method getDataRef() and removing getData() from RealVector would be nice - there is a toArray() this should be sufficient. 

--
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

       

[jira] [Updated] (MATH-626) Move RealVector.sparseIterator() to SparseRealVector

Posted by "Gilles (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MATH-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gilles updated MATH-626:
------------------------

    Fix Version/s:     (was: 3.1)
                   4.0
    
> Move RealVector.sparseIterator() to   SparseRealVector
> ------------------------------------------------------
>
>                 Key: MATH-626
>                 URL: https://issues.apache.org/jira/browse/MATH-626
>             Project: Commons Math
>          Issue Type: Improvement
>            Reporter: Arne Plöse
>            Priority: Minor
>             Fix For: 4.0
>
>
> Having this method available for all is not very efficient, because if I want use this feature I must check for interface SparseRealVector.
> otherwise different implementations could be faster. 
> I.e. no array clone and the assigning all values again.
> Maybe one could add a menthod fillstate() to SparseRealVector to guide which is faster - use array clone and then sparseIterator or just create the array and then fill it up.
> To reduce confusion a second Interface ArrayRealVector with the method getDataRef() and removing getData() from RealVector would be nice - there is a toArray() this should be sufficient. 

--
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

       

[jira] [Updated] (MATH-626) Move RealVector.sparseIterator() to SparseRealVector

Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MATH-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phil Steitz updated MATH-626:
-----------------------------

    Affects Version/s:     (was: 3.0)
        Fix Version/s: 3.1

If we do implement this, it can wait until 3.1

> Move RealVector.sparseIterator() to   SparseRealVector
> ------------------------------------------------------
>
>                 Key: MATH-626
>                 URL: https://issues.apache.org/jira/browse/MATH-626
>             Project: Commons Math
>          Issue Type: Improvement
>            Reporter: Arne Plöse
>            Priority: Minor
>             Fix For: 3.1
>
>
> Having this method available for all is not very efficient, because if I want use this feature I must check for interface SparseRealVector.
> otherwise different implementations could be faster. 
> I.e. no array clone and the assigning all values again.
> Maybe one could add a menthod fillstate() to SparseRealVector to guide which is faster - use array clone and then sparseIterator or just create the array and then fill it up.
> To reduce confusion a second Interface ArrayRealVector with the method getDataRef() and removing getData() from RealVector would be nice - there is a toArray() this should be sufficient. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira