[jira] [Closed] (SYSTEMML-516) Index Range Slicing Should Allow Implicit Upper Or Lower Bounds

["Mike Dusenberry (JIRA)" <ji...@apache.org>]

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

Mike Dusenberry closed SYSTEMML-516.
------------------------------------
    Resolution: Won't Fix

Update: We will instead aim to add implicit slicing bounds to the PyDML language, rather than in the DML language.  This is being tracked in SYSTEMML-676.

> Index Range Slicing Should Allow Implicit Upper Or Lower Bounds
> ---------------------------------------------------------------
>
>                 Key: SYSTEMML-516
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-516
>             Project: SystemML
>          Issue Type: Improvement
>            Reporter: Mike Dusenberry
>
> DML allows for index slicing of matrices for specified ranges, as in {{X[1:4, 2:6]}}.  However, this currently requires that *both* a lower *and* upper bound be specified for a given row or column range.
> It would be useful to be able to specify *either* a lower *or* upper bound, with the missing bound implicitly added internally.  This would allow for scenarios such as selecting all columns *except* the first one, as in
> {code}
> data = rand(rows=10, cols=20, min=0, max=1, pdf="uniform", sparsity=0.2)
> X = X[1:4, 2:]  # select rows 1 to 4, and columns 2 to ncol(X)
> {code}.
> This is the same functionality that [NumPy provides |http://docs.scipy.org/doc/numpy/reference/arrays.indexing.html].



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