[jira] [Commented] (SYSTEMML-698) Investigate removal of compile-scope dependencies
[ https://issues.apache.org/jira/browse/SYSTEMML-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321049#comment-15321049 ] Deron Eriksson commented on SYSTEMML-698: - I submitted [PR174|https://github.com/apache/incubator-systemml/pull/174] to remove the guava dependency. This can be done without too much effort since guava is not widely integrated into the project. I hand-coded some replacement code. This reduces the main jar size from ~6.6MB to ~4.4MB. > Investigate removal of compile-scope dependencies > - > > Key: SYSTEMML-698 > URL: https://issues.apache.org/jira/browse/SYSTEMML-698 > Project: SystemML > Issue Type: Improvement > Components: Build >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > SystemML currently has several compile-scope dependencies. Including these in > the main jar leads to a larger jar and complicates LICENSE/NOTICE maintenance. > Investigate if any or all of these can be removed, replaced, or set to > package scope. > These are: > org.abego.treelayout:org.abego.treelayout.core:jar:1.0.1 > com.google.guava:guava:bundle:14.0.1 > org.antlr:antlr4-annotations:jar:4.3 > org.antlr:antlr4-runtime:jar:4.3 > org.apache.wink:wink-json4j:jar:1.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-478) Upgrade maven-failsafe-plugin if fixed
[
https://issues.apache.org/jira/browse/SYSTEMML-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321010#comment-15321010
]
Deron Eriksson commented on SYSTEMML-478:
-
Tried removing maven-surefire-plugin version and maven-failsafe-plugin version
so that they would use the Apache parent pom version (2.19.1).
Running test suite on OS X (with version 2.19.1), I saw the following:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (default) on
project systemml: There was a timeout or other error in the fork
{code}
In addition, some of the output referred to numbers rather than test case
names. I saw things like this:
{code}
Running [2]
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 82.2 sec - in
[2]
{code}
rather than all of the 'running' output looking similar to this:
{code}
Running org.apache.sysml.test.integration.functions.jmlc.FrameCastingTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.694 sec - in
org.apache.sysml.test.integration.functions.jmlc.FrameCastingTest
{code}
So I would say we should probably stick with 2.17 for now.
> Upgrade maven-failsafe-plugin if fixed
> --
>
> Key: SYSTEMML-478
> URL: https://issues.apache.org/jira/browse/SYSTEMML-478
> Project: SystemML
> Issue Type: Improvement
>Reporter: Deron Eriksson
>Priority: Minor
>
> The maven-failsafe-plugin entry in pom.xml is set to version 2.17 due to:
> "Failsafe 2.18 has a bug in computing # cores, so use 2.17"
> The maven central repo has the following later versions of
> maven-failsafe-plugin available:
> 2.19.1
> 2.19
> 2.18.1
> We should determine if a later version of the plugin can be used and the
> "HACK ALERT" message can be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYSTEMML-698) Investigate removal of compile-scope dependencies
[ https://issues.apache.org/jira/browse/SYSTEMML-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321046#comment-15321046 ] Deron Eriksson commented on SYSTEMML-698: - I believe Hadoop and Spark use different JSON libraries. Also, wink-json4j is quite small (~77K). So keeping it compile-scope is fine. > Investigate removal of compile-scope dependencies > - > > Key: SYSTEMML-698 > URL: https://issues.apache.org/jira/browse/SYSTEMML-698 > Project: SystemML > Issue Type: Improvement > Components: Build >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > SystemML currently has several compile-scope dependencies. Including these in > the main jar leads to a larger jar and complicates LICENSE/NOTICE maintenance. > Investigate if any or all of these can be removed, replaced, or set to > package scope. > These are: > org.abego.treelayout:org.abego.treelayout.core:jar:1.0.1 > com.google.guava:guava:bundle:14.0.1 > org.antlr:antlr4-annotations:jar:4.3 > org.antlr:antlr4-runtime:jar:4.3 > org.apache.wink:wink-json4j:jar:1.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-698) Investigate removal of compile-scope dependencies
[ https://issues.apache.org/jira/browse/SYSTEMML-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321020#comment-15321020 ] Deron Eriksson commented on SYSTEMML-698: - The org.abego.treelayout.core jar is a transitive dependency of antlr4-runtime (v4.3), so it can't be removed. > Investigate removal of compile-scope dependencies > - > > Key: SYSTEMML-698 > URL: https://issues.apache.org/jira/browse/SYSTEMML-698 > Project: SystemML > Issue Type: Improvement > Components: Build >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > SystemML currently has several compile-scope dependencies. Including these in > the main jar leads to a larger jar and complicates LICENSE/NOTICE maintenance. > Investigate if any or all of these can be removed, replaced, or set to > package scope. > These are: > org.abego.treelayout:org.abego.treelayout.core:jar:1.0.1 > com.google.guava:guava:bundle:14.0.1 > org.antlr:antlr4-annotations:jar:4.3 > org.antlr:antlr4-runtime:jar:4.3 > org.apache.wink:wink-json4j:jar:1.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-746) Update Quick Start for l2-svm-predict.dml 3x3 confusion matrix
[ https://issues.apache.org/jira/browse/SYSTEMML-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324980#comment-15324980 ] Deron Eriksson commented on SYSTEMML-746: - Thank you [~MechCoder]! I added you as a SystemML contributor. > Update Quick Start for l2-svm-predict.dml 3x3 confusion matrix > -- > > Key: SYSTEMML-746 > URL: https://issues.apache.org/jira/browse/SYSTEMML-746 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Manoj Kumar >Priority: Minor > > Current Quick Start Guide discusses 2x2 confusion matrix generated by > l2-svm-predict.dml. The l2-svm-predict.dml script has been updated to > generate a 3x3 confusion matrix, so Quick Start Guide should reflect this. > See: > https://www.mail-archive.com/dev@systemml.incubator.apache.org/msg00629.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYSTEMML-698) Investigate removal of compile-scope dependencies
[ https://issues.apache.org/jira/browse/SYSTEMML-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson resolved SYSTEMML-698. - Resolution: Fixed Guava removed from project by [PR174|https://github.com/apache/incubator-systemml/pull/174]. > Investigate removal of compile-scope dependencies > - > > Key: SYSTEMML-698 > URL: https://issues.apache.org/jira/browse/SYSTEMML-698 > Project: SystemML > Issue Type: Improvement > Components: Build >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > SystemML currently has several compile-scope dependencies. Including these in > the main jar leads to a larger jar and complicates LICENSE/NOTICE maintenance. > Investigate if any or all of these can be removed, replaced, or set to > package scope. > These are: > org.abego.treelayout:org.abego.treelayout.core:jar:1.0.1 > com.google.guava:guava:bundle:14.0.1 > org.antlr:antlr4-annotations:jar:4.3 > org.antlr:antlr4-runtime:jar:4.3 > org.apache.wink:wink-json4j:jar:1.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYSTEMML-746) Update Quick Start for l2-svm-predict.dml 3x3 confusion matrix
[ https://issues.apache.org/jira/browse/SYSTEMML-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson resolved SYSTEMML-746. - Resolution: Fixed Fixed by [PR172|https://github.com/apache/incubator-systemml/pull/172]. > Update Quick Start for l2-svm-predict.dml 3x3 confusion matrix > -- > > Key: SYSTEMML-746 > URL: https://issues.apache.org/jira/browse/SYSTEMML-746 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Manoj Kumar >Priority: Minor > > Current Quick Start Guide discusses 2x2 confusion matrix generated by > l2-svm-predict.dml. The l2-svm-predict.dml script has been updated to > generate a 3x3 confusion matrix, so Quick Start Guide should reflect this. > See: > https://www.mail-archive.com/dev@systemml.incubator.apache.org/msg00629.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-746) Update Quick Start for l2-svm-predict.dml 3x3 confusion matrix
[ https://issues.apache.org/jira/browse/SYSTEMML-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-746. --- > Update Quick Start for l2-svm-predict.dml 3x3 confusion matrix > -- > > Key: SYSTEMML-746 > URL: https://issues.apache.org/jira/browse/SYSTEMML-746 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Manoj Kumar >Priority: Minor > > Current Quick Start Guide discusses 2x2 confusion matrix generated by > l2-svm-predict.dml. The l2-svm-predict.dml script has been updated to > generate a 3x3 confusion matrix, so Quick Start Guide should reflect this. > See: > https://www.mail-archive.com/dev@systemml.incubator.apache.org/msg00629.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | Pass | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows | Pass | |
| Test Suite Passes - OS X| Pass | (Deron will re-verify) |
| Test Suite Passes - Linux | | |
| All Binaries Execute| Pass | Verified on OS X (Deron will
re-verify) |
| Check LICENSE and NOTICE Files | Pass | (Deron will re-verify) |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | Pass | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | Pass | Verified on OS X
| Single-Node Hadoop | Pass | Verified on OS X
| Notebooks - Jupyter | | |
| Notebooks - Zeppelin| | |
| Performance Suite - Spark | Pass | Run on Spark 1.6.1 for data
sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel|bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | Pass | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows | Pass | |
| Test Suite Passes - OS X| Pass | (Deron will re-verify) |
| Test Suite Passes - Linux | | |
| All Binaries Execute| Pass | Verified on OS X (Deron will
re-verify) |
| Check LICENSE and NOTICE Files | Pass | (Deron will re-verify) |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | Pass | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | Pass | Verified on OS X
| Single-Node Hadoop | Pass | Verified on OS X
| Notebooks - Jupyter | | |
| Notebooks - Zeppelin| | |
| Performance Suite - Spark | Pass | Run on Spark 1.6.1 for data
sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | | |
> | Release Candidate Build - OS X | Pass | |
> | Release Candidate Build - Linux | | |
> | Test Suite Passes - Windows | Pass | |
> | Test Suite Passes - OS X| Pass | (Deron will re-verify) |
> | Test Suite Passes - Linux | | |
> | All Binaries Execute| Pass | Verified on OS X (Deron will
> re-verify) |
> | Check LICENSE and NOTICE Files | Pass | (Deron will re-verify) |
> | Src Artifact Builds and Tests Pass | | |
> | Single-Node Standalone - Windows| | |
> | Single-Node Standalone - OS X | Pass | |
> | Single-Node Standalone - Linux | | |
> | Single-Node Spark | Pass | Verified on OS X
> | Single-Node Hadoop | Pass | Verified on OS X
> | Notebooks - Jupyter | | |
> | Notebooks - Zeppelin| | |
> | Performance Suite - Spark | Pass | Run on Spark 1.6.1 for data
> sizes {80MB, 800MB, 8GB, 80GB} |
> | Performance Suite - Hadoop | | |
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
Deron Eriksson created SYSTEMML-708:
---
Summary: Release checklist for 0.10.0-incubating-rc1
Key: SYSTEMML-708
URL: https://issues.apache.org/jira/browse/SYSTEMML-708
Project: SystemML
Issue Type: Task
Reporter: Deron Eriksson
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | Pass | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | Pass | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows | Pass | |
| Test Suite Passes - OS X| Pass | (Deron will re-verify) |
| Test Suite Passes - Linux | | |
| All Binaries Execute| Pass | Verified on OS X (Deron will
re-verify) |
| Check LICENSE and NOTICE Files | Pass | (Deron will re-verify) |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | Pass | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | Pass | Verified on OS X
| Single-Node Hadoop | Pass | Verified on OS X
| Notebooks - Jupyter | | |
| Notebooks - Zeppelin| | |
| Performance Suite - Spark | Pass | Performance testsuite run on
Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB}, sparse/dense, intercept
0/1/2, and the algorithm classes binomial (Mlogreg, L2SVM, MSVM), multinomial
(Mlogreg, MSVM, Naive Bayes), regression (LinregCG, LinregDS, GLM poisson-log,
GLM gamma-log, GLM binomal-probit), clustering (Kmeans), and statistics
(Univariate, Bivariate). The good news is that there are no compiler/runtime
issues and performance is as expected. |
| Performance Suite - Hadoop | | |
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | Pass | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | Pass | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows | Pass | |
| Test Suite Passes - OS X| Pass | (Deron will re-verify) |
| Test Suite Passes - Linux | | |
| All Binaries Execute| Pass | Verified on OS X (Deron will
re-verify) |
| Check LICENSE and NOTICE Files | Pass | (Deron will re-verify) |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | Pass | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | Pass | Verified on OS X
| Single-Node Hadoop | Pass | Verified on OS X
| Notebooks - Jupyter | | |
| Notebooks - Zeppelin| | |
| Performance Suite - Spark | Pass | Run on Spark 1.6.1 for data
sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | Pass | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | Pass | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows | Pass | |
| Test Suite Passes - OS X| Pass | (Deron will re-verify) |
| Test Suite Passes - Linux | | |
| All Binaries Execute| Pass | Verified on OS X (Deron will
re-verify) |
| Check LICENSE and NOTICE Files | Pass | (Deron will re-verify) |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | Pass | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | Pass | Verified on OS X
| Single-Node Hadoop | Pass | Verified on OS X
| Notebooks - Jupyter | | |
| Notebooks - Zeppelin| | |
| Performance Suite - Spark | Pass | Performance testsuite run on
Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB}, sparse/dense, intercept
0/1/2, and the algorithm classes binomial (Mlogreg, L2SVM, MSVM), multinomial
(Mlogreg, MSVM, Naive Bayes), regression (LinregCG, LinregDS, GLM poisson-log,
GLM gamma-log, GLM binomal-probit), clustering (Kmeans), and statistics
(Univariate, Bivariate). The good news is that there are no compiler/runtime
issues and performance is as expected. |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | Pass | |
> | Release Candidate Build - Windows | | |
> | Release Candidate Build - OS X | Pass | |
> | Release Candidate Build - Linux | | |
> | Test Suite Passes - Windows | Pass | |
> | Test Suite Passes - OS X| Pass | (Deron will re-verify) |
> | Test Suite Passes - Linux | | |
> | All Binaries Execute| Pass | Verified on OS X (Deron will
> re-verify) |
> | Check LICENSE and NOTICE Files | Pass | (Deron will re-verify) |
> | Src Artifact Builds and Tests Pass | | |
> | Single-Node Standalone - Windows| | |
> | Single-Node Standalone - OS X | Pass | |
> | Single-Node Standalone - Linux | | |
> | Single-Node Spark | Pass | Verified on OS X
> | Single-Node Hadoop | Pass | Verified on OS X
> | Notebooks - Jupyter | | |
> | Notebooks - Zeppelin| | |
> | Performance Suite - Spark | Pass | Run on Spark 1.6.1 for data
> sizes {80MB, 800MB, 8GB, 80GB} |
> | Performance Suite - Hadoop | | |
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows | | |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#fcf883}Fix{panel} |
systemml-0.10.0-incubating-standalone.jar not have right LICENSE and NOTICE |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows | | |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | | |
> | Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Linux | | |
> | Test Suite Passes - Windows | | |
> | Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
> (Deron will re-verify) |
> | Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X (Deron will re-verify) |
> | Check LICENSE and NOTICE Files | {panel:bgColor=#fcf883}Fix{panel} |
> systemml-0.10.0-incubating-standalone.jar not have right LICENSE and NOTICE |
> | Src Artifact Builds and Tests Pass | | |
> | Single-Node Standalone - Windows| | |
> | Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Single-Node Standalone - Linux | | |
> | Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X
> | Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X
> | Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X |
> | Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
>
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows | | |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#fcf883}Fix{panel} |
systemml-0.10.0-incubating-standalone.jar not have right LICENSE and NOTICE |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || {nowrap}Status{nowrap} || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows | | |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#fcf883}Fix{panel} |
systemml-0.10.0-incubating-standalone.jar not have right LICENSE and NOTICE |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | | |
> | Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Linux | | |
> | Test Suite Passes - Windows | | |
> | Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
> (Deron will re-verify) |
> | Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X (Deron will re-verify) |
> | Check LICENSE and NOTICE Files | {panel:bgColor=#fcf883}Fix{panel} |
> systemml-0.10.0-incubating-standalone.jar not have right LICENSE and NOTICE |
> | Src Artifact Builds and Tests Pass | | |
> | Single-Node Standalone - Windows| | |
> | Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Single-Node Standalone - Linux | | |
> | Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X
> | Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X
> | Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X |
> | Notebooks
[jira] [Created] (SYSTEMML-711) Fix LICENSE and NOTICE in standalone jar
Deron Eriksson created SYSTEMML-711:
---
Summary: Fix LICENSE and NOTICE in standalone jar
Key: SYSTEMML-711
URL: https://issues.apache.org/jira/browse/SYSTEMML-711
Project: SystemML
Issue Type: Bug
Components: Build
Reporter: Deron Eriksson
The standalone uberjar does not contain the correct LICENSE and NOTICE files.
Most likely this can be corrected by removing the following from
src/assembly/standalone-jar.xml:
{code}
META-INF/LICENSE
META-INF/NOTICE
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-758) PYDML toString sparse displays 1 vs 0 indexing
Deron Eriksson created SYSTEMML-758:
---
Summary: PYDML toString sparse displays 1 vs 0 indexing
Key: SYSTEMML-758
URL: https://issues.apache.org/jira/browse/SYSTEMML-758
Project: SystemML
Issue Type: Bug
Components: APIs
Reporter: Deron Eriksson
Priority: Minor
Recently PYDML changed from 1-based indexing to 0-based indexing for matrices.
The toString sparse display needs to be changed from 1-based to 0-based
indexing.
{code}
m = full("1 2 3 4 5 6 7 8 9 10 11 12", rows=4, cols=3)
print(toString(m, sparse=True))
{code}
displays
{code}
1 1 1.000
1 2 2.000
1 3 3.000
2 1 4.000
2 2 5.000
2 3 6.000
3 1 7.000
3 2 8.000
3 3 9.000
4 1 10.000
4 2 11.000
4 3 12.000
{code}
The first line should be
{code}
0 0 1.000
{code}
and the other numbers should be updated accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYSTEMML-760) PYDML save function ijv and mm formats use 1-based indexing
[
https://issues.apache.org/jira/browse/SYSTEMML-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328063#comment-15328063
]
Deron Eriksson commented on SYSTEMML-760:
-
I don't know how the binary format is implemented, but it should also be
checked.
> PYDML save function ijv and mm formats use 1-based indexing
> ---
>
> Key: SYSTEMML-760
> URL: https://issues.apache.org/jira/browse/SYSTEMML-760
> Project: SystemML
> Issue Type: Task
> Components: APIs
>Reporter: Deron Eriksson
>
> PYDML now uses 0-based indexing rather than 1-based indexing. Saving to ivj
> (text) and mm (matrix market) formats uses 1-based matrices.
> The following code:
> {code}
> m = full("1 2 3 0 0 0 7 8 9 0 0 0", rows=4, cols=3)
> save(m, "m.txt", format="text")
> save(m, "m.mm", format="mm")
> {code}
> generates:
> m.txt:
> {code}
> 1 1 1.0
> 1 2 2.0
> 1 3 3.0
> 3 1 7.0
> 3 2 8.0
> 3 3 9.0
> {code}
> and
> m.mm:
> {code}
> %%MatrixMarket matrix coordinate real general
> 4 3 6
> 1 1 1.0
> 1 2 2.0
> 1 3 3.0
> 3 1 7.0
> 3 2 8.0
> 3 3 9.0
> {code}
> 0-based indexing for m.txt would be:
> {code}
> 0 0 1.0
> 0 1 2.0
> 0 2 3.0
> 2 0 7.0
> 2 1 8.0
> 2 2 9.0
> {code}
> A similar situation would exist for the m.mm file.
> Note: The reading of the matrices should also be 0-based if PYDML is 0-based.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYSTEMML-759) Update Beginner's Guide for toString and PYDML 0-based indexing
[ https://issues.apache.org/jira/browse/SYSTEMML-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson updated SYSTEMML-759: Description: The toString function has been added to DML/PYDML, the use of which should be included in the Beginner's Guide. The guide needs to be updated for the PYDML 0-based indexing. > Update Beginner's Guide for toString and PYDML 0-based indexing > --- > > Key: SYSTEMML-759 > URL: https://issues.apache.org/jira/browse/SYSTEMML-759 > Project: SystemML > Issue Type: Task >Reporter: Deron Eriksson >Assignee: Deron Eriksson >Priority: Minor > > The toString function has been added to DML/PYDML, the use of which should be > included in the Beginner's Guide. > The guide needs to be updated for the PYDML 0-based indexing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-759) Update Beginner's Guide for toString and PYDML 0-based indexing
Deron Eriksson created SYSTEMML-759: --- Summary: Update Beginner's Guide for toString and PYDML 0-based indexing Key: SYSTEMML-759 URL: https://issues.apache.org/jira/browse/SYSTEMML-759 Project: SystemML Issue Type: Task Reporter: Deron Eriksson Assignee: Deron Eriksson Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-760) PYDML save function ijv and mm formats use 1-based indexing
Deron Eriksson created SYSTEMML-760:
---
Summary: PYDML save function ijv and mm formats use 1-based
indexing
Key: SYSTEMML-760
URL: https://issues.apache.org/jira/browse/SYSTEMML-760
Project: SystemML
Issue Type: Task
Components: APIs
Reporter: Deron Eriksson
PYDML now uses 0-based indexing rather than 1-based indexing. Saving to ivj
(text) and mm (matrix market) formats uses 1-based matrices.
The following code:
{code}
m = full("1 2 3 0 0 0 7 8 9 0 0 0", rows=4, cols=3)
save(m, "m.txt", format="text")
save(m, "m.mm", format="mm")
{code}
generates:
m.txt:
{code}
1 1 1.0
1 2 2.0
1 3 3.0
3 1 7.0
3 2 8.0
3 3 9.0
{code}
and
m.mm:
{code}
%%MatrixMarket matrix coordinate real general
4 3 6
1 1 1.0
1 2 2.0
1 3 3.0
3 1 7.0
3 2 8.0
3 3 9.0
{code}
0-based indexing for m.txt would be:
{code}
0 0 1.0
0 1 2.0
0 2 3.0
2 0 7.0
2 1 8.0
2 2 9.0
{code}
A similar situation would exist for the m.mm file.
Note: The reading of the matrices should also be 0-based if PYDML is 0-based.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYSTEMML-760) PYDML save function ijv and mm formats use 1-based indexing
[
https://issues.apache.org/jira/browse/SYSTEMML-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328201#comment-15328201
]
Deron Eriksson commented on SYSTEMML-760:
-
cc [~mwdus...@us.ibm.com]
> PYDML save function ijv and mm formats use 1-based indexing
> ---
>
> Key: SYSTEMML-760
> URL: https://issues.apache.org/jira/browse/SYSTEMML-760
> Project: SystemML
> Issue Type: Task
> Components: APIs
>Reporter: Deron Eriksson
>
> PYDML now uses 0-based indexing rather than 1-based indexing. Saving to ivj
> (text) and mm (matrix market) formats uses 1-based matrices.
> The following code:
> {code}
> m = full("1 2 3 0 0 0 7 8 9 0 0 0", rows=4, cols=3)
> save(m, "m.txt", format="text")
> save(m, "m.mm", format="mm")
> {code}
> generates:
> m.txt:
> {code}
> 1 1 1.0
> 1 2 2.0
> 1 3 3.0
> 3 1 7.0
> 3 2 8.0
> 3 3 9.0
> {code}
> and
> m.mm:
> {code}
> %%MatrixMarket matrix coordinate real general
> 4 3 6
> 1 1 1.0
> 1 2 2.0
> 1 3 3.0
> 3 1 7.0
> 3 2 8.0
> 3 3 9.0
> {code}
> 0-based indexing for m.txt would be:
> {code}
> 0 0 1.0
> 0 1 2.0
> 0 2 3.0
> 2 0 7.0
> 2 1 8.0
> 2 2 9.0
> {code}
> A similar situation would exist for the m.mm file.
> Note: The reading of the matrices should also be 0-based if PYDML is 0-based.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SYSTEMML-735) Www
[ https://issues.apache.org/jira/browse/SYSTEMML-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-735. --- Resolution: Invalid This appears to be an invalid JIRA? > Www > --- > > Key: SYSTEMML-735 > URL: https://issues.apache.org/jira/browse/SYSTEMML-735 > Project: SystemML > Issue Type: Blogs - New Blog User Account Request >Reporter: Bryan lim >Priority: Blocker > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-736) Www
[ https://issues.apache.org/jira/browse/SYSTEMML-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-736. --- Resolution: Invalid This appears to be an invalid JIRA? > Www > --- > > Key: SYSTEMML-736 > URL: https://issues.apache.org/jira/browse/SYSTEMML-736 > Project: SystemML > Issue Type: Bug >Reporter: Bryan lim > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
systemml-0.10.0-incubating-standalone.jar not have right LICENSE and NOTICE |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | | |
> | Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Linux | | |
> | Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
> SYSTEMML-712 opened for intermittent test failure |
> | Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
> (Deron will re-verify) |
> | Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X (Deron will re-verify) |
> | Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
> non-blocker, SYSTEMML-711 filed |
> | Src Artifact Builds and Tests Pass | | |
> | Single-Node Standalone - Windows| | |
> | Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Single-Node Standalone - Linux | | |
> | Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X
> | Single-Node Hadoop |
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
systemml-0.10.0-incubating-standalone.jar not have right LICENSE and NOTICE |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#fcf883}Fix{panel} |
systemml-0.10.0-incubating-standalone.jar not have right LICENSE and NOTICE |
| Src Artifact Builds and Tests Pass | | |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | | |
> | Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Linux | | |
> | Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
> SYSTEMML-712 opened for intermittent test failure |
> | Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
> (Deron will re-verify) |
> | Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X (Deron will re-verify) |
> | Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
> systemml-0.10.0-incubating-standalone.jar not have right LICENSE and NOTICE |
> | Src Artifact Builds and Tests Pass | | |
> | Single-Node Standalone - Windows| | |
> | Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Single-Node Standalone - Linux | | |
> | Single-Node Spark |
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | | |
> | Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
> SYSTEMML-712 opened for intermittent test failure |
> | Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
> (Deron will re-verify) |
> | Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X (Deron will re-verify) |
> | Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
> non-blocker, SYSTEMML-711 filed |
> | Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
>
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | | |
> | Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
> SYSTEMML-712 opened for intermittent test failure |
> | Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
> (Deron will re-verify) |
> | Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X (Deron will re-verify) |
> | Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
> non-blocker, SYSTEMML-711 filed |
> | Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
> 5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
> |
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | | |
> | Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
> SYSTEMML-712 opened for intermittent test failure |
> | Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} | |
> | Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X |
> | Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
> non-blocker, SYSTEMML-711 filed |
> | Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
> 5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
> | Single-Node
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
| Single-Node Standalone - Windows| {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>Assignee: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
> SYSTEMML-712 opened for intermittent test failure |
> | Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} | |
> | Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X |
> | Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
> non-blocker, SYSTEMML-711 filed |
> | Src
[jira] [Updated] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-708:
Description:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
was:
|| Task || Status || Notes ||
| All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Windows | | |
| Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
SYSTEMML-712 opened for intermittent test failure |
| Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} |
(Deron will re-verify) |
| Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X (Deron will re-verify) |
| Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
non-blocker, SYSTEMML-711 filed |
| Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
| Single-Node Standalone - Windows| | |
| Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Standalone - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
| Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X
| Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
Verified on OS X |
| Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
| Performance Suite - Hadoop | | |
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | | |
> | Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
> SYSTEMML-712 opened for intermittent test failure |
> | Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} | |
> | Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X (Deron will re-verify) |
> | Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
> non-blocker, SYSTEMML-711 filed |
> | Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
> 5037 of 5038
[jira] [Assigned] (SYSTEMML-708) Release checklist for 0.10.0-incubating-rc1
[
https://issues.apache.org/jira/browse/SYSTEMML-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson reassigned SYSTEMML-708:
---
Assignee: Deron Eriksson
> Release checklist for 0.10.0-incubating-rc1
> ---
>
> Key: SYSTEMML-708
> URL: https://issues.apache.org/jira/browse/SYSTEMML-708
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>Assignee: Deron Eriksson
>
> || Task || Status || Notes ||
> | All Artifacts and Checksums Present | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Windows | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Release Candidate Build - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | Test Suite Passes - Windows |{panel:bgColor=#bfffba}Pass{panel} |
> SYSTEMML-712 opened for intermittent test failure |
> | Test Suite Passes - OS X| {panel:bgColor=#bfffba}Pass{panel} | |
> | Test Suite Passes - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | All Binaries Execute| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X |
> | Check LICENSE and NOTICE Files | {panel:bgColor=#bfffba}Pass{panel} |
> non-blocker, SYSTEMML-711 filed |
> | Src Artifact Builds and Tests Pass | {panel:bgColor=#bfffba}Pass{panel} |
> 5037 of 5038 passed on OS X (RightIndexingMatrixTest failed) |
> | Single-Node Standalone - Windows| | |
> | Single-Node Standalone - OS X | {panel:bgColor=#bfffba}Pass{panel} | |
> | Single-Node Standalone - Linux | {panel:bgColor=#bfffba}Pass{panel} | |
> | Single-Node Spark | {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X
> | Single-Node Hadoop | {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X
> | Notebooks - Jupyter | {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X |
> | Notebooks - Zeppelin| {panel:bgColor=#bfffba}Pass{panel} |
> Verified on OS X |
> | Performance Suite - Spark | {panel:bgColor=#bfffba}Pass{panel} |
> Run on Spark 1.6.1 for data sizes {80MB, 800MB, 8GB, 80GB} |
> | Performance Suite - Hadoop | | |
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-713) Create release process document
Deron Eriksson created SYSTEMML-713: --- Summary: Create release process document Key: SYSTEMML-713 URL: https://issues.apache.org/jira/browse/SYSTEMML-713 Project: SystemML Issue Type: Task Components: Documentation Reporter: Deron Eriksson Assignee: Deron Eriksson Describe the SystemML release process in a document so that the release validation consists of well-defined, documented, reproducible steps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-626) source statement not resolve absolute paths
[
https://issues.apache.org/jira/browse/SYSTEMML-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson closed SYSTEMML-626.
---
> source statement not resolve absolute paths
> ---
>
> Key: SYSTEMML-626
> URL: https://issues.apache.org/jira/browse/SYSTEMML-626
> Project: SystemML
> Issue Type: Bug
> Components: Parser
>Reporter: Deron Eriksson
>Assignee: Tatsuya Nishiyama
>
> Suppose we are using the default working directory "." and have a DML source
> statement such the following:
> {code}
> source("/foo.dml") as foo;
> {code}
> Rather than resolving to the absolute path, which is typical of a string path
> starting with a slash, this resolves to ".//foo.dml", as evidenced by:
> {code}
> Cannot find file: .//foo.dml
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SYSTEMML-626) source statement not resolve absolute paths
[
https://issues.apache.org/jira/browse/SYSTEMML-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson resolved SYSTEMML-626.
-
Resolution: Fixed
Fixed by [PR168|https://github.com/apache/incubator-systemml/pull/168].
> source statement not resolve absolute paths
> ---
>
> Key: SYSTEMML-626
> URL: https://issues.apache.org/jira/browse/SYSTEMML-626
> Project: SystemML
> Issue Type: Bug
> Components: Parser
>Reporter: Deron Eriksson
>Assignee: Tatsuya Nishiyama
>
> Suppose we are using the default working directory "." and have a DML source
> statement such the following:
> {code}
> source("/foo.dml") as foo;
> {code}
> Rather than resolving to the absolute path, which is typical of a string path
> starting with a slash, this resolves to ".//foo.dml", as evidenced by:
> {code}
> Cannot find file: .//foo.dml
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-763) Remove PyDML grammar dataIdentifier warnings during build
Deron Eriksson created SYSTEMML-763:
---
Summary: Remove PyDML grammar dataIdentifier warnings during build
Key: SYSTEMML-763
URL: https://issues.apache.org/jira/browse/SYSTEMML-763
Project: SystemML
Issue Type: Improvement
Components: APIs
Reporter: Deron Eriksson
Priority: Minor
During the build, the following warnings occur for the Pydml grammar:
{code}
[WARNING] warning(154): org/apache/sysml/parser/pydml/Pydml.g4:224:0: rule
'dataIdentifier' contains an optional block with at least one alternative that
can match an empty string
[WARNING]
/Users/deroneriksson/Documents/workspace/incubator-systemml/org/apache/sysml/parser/pydml/Pydml.g4
[224:0]: rule 'dataIdentifier' contains an optional block with at least one
alternative that can match an empty string
[WARNING] warning(154): org/apache/sysml/parser/pydml/Pydml.g4:224:0: rule
'dataIdentifier' contains an optional block with at least one alternative that
can match an empty string
[WARNING]
/Users/deroneriksson/Documents/workspace/incubator-systemml/org/apache/sysml/parser/pydml/Pydml.g4
[224:0]: rule 'dataIdentifier' contains an optional block with at least one
alternative that can match an empty string
[WARNING] warning(154): org/apache/sysml/parser/pydml/Pydml.g4:224:0: rule
'dataIdentifier' contains an optional block with at least one alternative that
can match an empty string
[WARNING]
/Users/deroneriksson/Documents/workspace/incubator-systemml/org/apache/sysml/parser/pydml/Pydml.g4
[224:0]: rule 'dataIdentifier' contains an optional block with at least one
alternative that can match an empty string
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-764) Add Univar-Stats.dml labeled console output to Quick Start Guide
Deron Eriksson created SYSTEMML-764: --- Summary: Add Univar-Stats.dml labeled console output to Quick Start Guide Key: SYSTEMML-764 URL: https://issues.apache.org/jira/browse/SYSTEMML-764 Project: SystemML Issue Type: Improvement Components: Documentation Reporter: Deron Eriksson Priority: Minor The results generated by Univar-Stats.dml are easier to interpret when the optional CONSOLE_OUTPUT=TRUE parameter is supplied. It would be nice to include this labeled output in the Quick Start Guide for readability of the results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-750) PYDML should not require newline at end of script
[
https://issues.apache.org/jira/browse/SYSTEMML-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347420#comment-15347420
]
Deron Eriksson commented on SYSTEMML-750:
-
When the pydml is placed in a file, it is being read in line-by-line, where \n
is being appended to each line being read in, so if the pydml is being read
from a file, the code will always end in \n.
> PYDML should not require newline at end of script
> -
>
> Key: SYSTEMML-750
> URL: https://issues.apache.org/jira/browse/SYSTEMML-750
> Project: SystemML
> Issue Type: Bug
> Components: APIs
>Reporter: Deron Eriksson
> Fix For: SystemML 0.11
>
>
> PYDML currently requires a linefeed at the end of the script. No linefeed
> should be required on the last line. This should be fixed in Pydml.g4.
> For example, the following code:
> {code}
> SparkConf conf = new
> SparkConf().setAppName("MLContextExample").setMaster("local");
> JavaSparkContext sc = new JavaSparkContext(conf);
> MLContext ml = new MLContext(sc);
> String scriptString = "print('hello world')";
> ml.executeScript(scriptString, true);
> {code}
> generates the following error:
> {code}
> [line 1:20] [Syntax error] -> print('hello world')
>missing NEWLINE at ''
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-514) Remove warnings from algorithm script executions
Deron Eriksson created SYSTEMML-514: --- Summary: Remove warnings from algorithm script executions Key: SYSTEMML-514 URL: https://issues.apache.org/jira/browse/SYSTEMML-514 Project: SystemML Issue Type: Task Components: Algorithms Reporter: Deron Eriksson When first executing an algorithm, if the user sees warning messages such as 'Initialization of ... depends on if-else execution', it can be disconcerting to the user since it appears that something isn't right. If possible, the main algorithms should be coded so that warning messages such as these don't appear. This should be done for the main DML algorithm, the corresponding DML test algorithm, and the corresponding PyDML test algorithm See SYSTEMML-494 for this issue with GLM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-468) Create Contributing to SystemML document
[ https://issues.apache.org/jira/browse/SYSTEMML-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-468. --- > Create Contributing to SystemML document > > > Key: SYSTEMML-468 > URL: https://issues.apache.org/jira/browse/SYSTEMML-468 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > Create a Contributing to SystemML document for developers and data scientists. > Describe our typical git workflow for contributing to the project (fork on > github, clone to local, checkout a branch and do work on branch, push to > github branch, file pull request, pull request reviewed, push additional > changes to github branch/pull request, pull request accepted and integrated > into project). > Describe basic IDE setup for working on SystemML code (move Eclipse debug > configuration info from Beginner's Guide to here). > Describe creation of a test class. > Describe running new code locally. > Describe running new code on Hadoop. > Describe running new code on Spark. > Describe running new code via MLContext. > Any other pointers that would help a new developer or data scientist > contribute to SystemML could go here. For instance, a data scientist might > want to contribute a new algorithm to SystemML. However, this algorithm > probably needs a test class, so the contribution may require more than DML. > The test class could be written by the data scientist, or perhaps a request > could be made for a developer to handle the test class. It's good to spell > out this kind of process to help grow our community. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYSTEMML-468) Create Contributing to SystemML document
[ https://issues.apache.org/jira/browse/SYSTEMML-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson resolved SYSTEMML-468. - Resolution: Fixed > Create Contributing to SystemML document > > > Key: SYSTEMML-468 > URL: https://issues.apache.org/jira/browse/SYSTEMML-468 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > Create a Contributing to SystemML document for developers and data scientists. > Describe our typical git workflow for contributing to the project (fork on > github, clone to local, checkout a branch and do work on branch, push to > github branch, file pull request, pull request reviewed, push additional > changes to github branch/pull request, pull request accepted and integrated > into project). > Describe basic IDE setup for working on SystemML code (move Eclipse debug > configuration info from Beginner's Guide to here). > Describe creation of a test class. > Describe running new code locally. > Describe running new code on Hadoop. > Describe running new code on Spark. > Describe running new code via MLContext. > Any other pointers that would help a new developer or data scientist > contribute to SystemML could go here. For instance, a data scientist might > want to contribute a new algorithm to SystemML. However, this algorithm > probably needs a test class, so the contribution may require more than DML. > The test class could be written by the data scientist, or perhaps a request > could be made for a developer to handle the test class. It's good to spell > out this kind of process to help grow our community. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-502) Remove javacc Token class and update related exception handling
[ https://issues.apache.org/jira/browse/SYSTEMML-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15131303#comment-15131303 ] Deron Eriksson commented on SYSTEMML-502: - Initially investigated in [PR28 | https://github.com/apache/incubator-systemml/pull/28]. See code and comments. > Remove javacc Token class and update related exception handling > --- > > Key: SYSTEMML-502 > URL: https://issues.apache.org/jira/browse/SYSTEMML-502 > Project: SystemML > Issue Type: Task > Components: Parser >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > The Token class was generated by javacc and is no longer used, so it should > be removed. The Token class is referenced by ParseException. ParseException > should probably be deleted. Related parsing exceptions can possibly be > handled by DMLParseException and related non-parsing exceptions can be > handled by LanguageException. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-502) Remove javacc Token class and update related exception handling
Deron Eriksson created SYSTEMML-502: --- Summary: Remove javacc Token class and update related exception handling Key: SYSTEMML-502 URL: https://issues.apache.org/jira/browse/SYSTEMML-502 Project: SystemML Issue Type: Task Components: Parser Reporter: Deron Eriksson The Token class was generated by javacc and is no longer used, so it should be removed. The Token class is referenced by ParseException. ParseException should probably be deleted. Related parsing exceptions can possibly be handled by DMLParseException and related non-parsing exceptions can be handled by LanguageException. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-503) Update license for CSS and JS
Deron Eriksson created SYSTEMML-503: --- Summary: Update license for CSS and JS Key: SYSTEMML-503 URL: https://issues.apache.org/jira/browse/SYSTEMML-503 Project: SystemML Issue Type: Task Reporter: Deron Eriksson IPMC review found project LICENSE needs to include licenses for CSS and JS in docs/. "LICENSE is missing: - Bootstrap [1] (MIT licensed) - Modernizr [2] (MIT/BSD licensed) - Polyfill [2] (MIT/BSD licensed) - Respond [2] (MIT/GPL licensed) - Normalize [3] (MIT licensed) - AnchorJS [5] (MIT licensed) - JQuery [6] (MIT licensed) ... 1. ./docs/js/vendor/bootstrap.min.js 2. ./docs/js/vendor/modernizr-2.6.1-respond-1.1.0.min.js 3. ./docs/css/bootstrap.min.css ... 5. ./docs/js/vendor/anchor.min.js 6. ./docs/js/vendor/jquery-1.12.0.min.js" Verify that all of these libraries are actually being used and if any are not required, remove them. Verify the licenses and update project LICENSE accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-534) Add optional console output with statistical labels to Univar-Stats.dml
[
https://issues.apache.org/jira/browse/SYSTEMML-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159799#comment-15159799
]
Deron Eriksson commented on SYSTEMML-534:
-
Fixed by [PR74 | https://github.com/apache/incubator-systemml/pull/74].
Also created SYSTEMML-538 for adding a similar feature to bivar-stats.dml.
> Add optional console output with statistical labels to Univar-Stats.dml
> ---
>
> Key: SYSTEMML-534
> URL: https://issues.apache.org/jira/browse/SYSTEMML-534
> Project: SystemML
> Issue Type: Improvement
> Components: Algorithms
>Reporter: Deron Eriksson
>Assignee: Deron Eriksson
>Priority: Minor
>
> Currently, the output from Univar-Stats.dml is a matrix that is written to a
> file, and the numbers in this file then need to be compared to a chart in the
> Algorithms Reference to be deciphered. This makes exploratory data analysis
> slower than it needs to be.
> Therefore, include an optional input parameter that turns on outputting the
> statistical results to the console. Label the statistics with words
> ("minimum", "maximum", "range", "mean", etc.) so that the results can be
> understood directly in the console output.
> Order the results by feature so that statistics for each feature are grouped
> together.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SYSTEMML-534) Add optional console output with statistical labels to Univar-Stats.dml
[
https://issues.apache.org/jira/browse/SYSTEMML-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson closed SYSTEMML-534.
---
> Add optional console output with statistical labels to Univar-Stats.dml
> ---
>
> Key: SYSTEMML-534
> URL: https://issues.apache.org/jira/browse/SYSTEMML-534
> Project: SystemML
> Issue Type: Improvement
> Components: Algorithms
>Reporter: Deron Eriksson
>Assignee: Deron Eriksson
>Priority: Minor
> Fix For: SystemML 0.10
>
>
> Currently, the output from Univar-Stats.dml is a matrix that is written to a
> file, and the numbers in this file then need to be compared to a chart in the
> Algorithms Reference to be deciphered. This makes exploratory data analysis
> slower than it needs to be.
> Therefore, include an optional input parameter that turns on outputting the
> statistical results to the console. Label the statistics with words
> ("minimum", "maximum", "range", "mean", etc.) so that the results can be
> understood directly in the console output.
> Order the results by feature so that statistics for each feature are grouped
> together.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYSTEMML-518) ijv vs text terminology
[
https://issues.apache.org/jira/browse/SYSTEMML-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-518:
Description:
Currently the IJV (i,j,v) text format is also referred to as the "text" format,
which is confusing. The word "text" is nebulous, since "csv" is a text format,
"ijv" is a text format, and "matrixmarket" is a text format. The term "ijv" is
more descriptive than "text".
So I would favor replacing all references to "text" with "ijv". This would also
eliminate how two terms ("text" and "ijv") are currently being used to refer to
the same thing, which is confusing.
This would include replacing the following JSON metadata:
{code}
"format": "text"
{code}
with
{code}
"format": "ijv"
{code}
was:
Currently the IJV (i,j,v) text format is also referred to as the "text" format,
which is confusing. The word "text" is nebulous, since "csv" is a text format,
"ijv" is a text format, and "matrixmarket" is a text format. The term "ijv" is
more descriptive than "text".
So I would favor replacing all references to "text" with "ijv". This would also
eliminate how two terms ("text" and "ijv") are currently being used to refer to
the same thing, which is confusing.
> ijv vs text terminology
> ---
>
> Key: SYSTEMML-518
> URL: https://issues.apache.org/jira/browse/SYSTEMML-518
> Project: SystemML
> Issue Type: Improvement
>Reporter: Deron Eriksson
>
> Currently the IJV (i,j,v) text format is also referred to as the "text"
> format, which is confusing. The word "text" is nebulous, since "csv" is a
> text format, "ijv" is a text format, and "matrixmarket" is a text format. The
> term "ijv" is more descriptive than "text".
> So I would favor replacing all references to "text" with "ijv". This would
> also eliminate how two terms ("text" and "ijv") are currently being used to
> refer to the same thing, which is confusing.
> This would include replacing the following JSON metadata:
> {code}
> "format": "text"
> {code}
> with
> {code}
> "format": "ijv"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-522) Add optional description parameter to read function
Deron Eriksson created SYSTEMML-522:
---
Summary: Add optional description parameter to read function
Key: SYSTEMML-522
URL: https://issues.apache.org/jira/browse/SYSTEMML-522
Project: SystemML
Issue Type: Task
Components: APIs, Parser
Reporter: Deron Eriksson
Priority: Minor
Metadata attributes can typically be passed as function parameters. For
example, in the first call below, we see that the header and sep attributes are
passed successfully as function parameters to the read() function.
{code}
# good
b = read("m.csv", header=FALSE, sep=",");
# bad
c = read("m.csv", header=FALSE, sep=",", description="desc");
{code}
However, if someone tries to pass in a description attribute as a function
parameter (as in the second example above), it blows up with an unhelpful error
message:
{code}
Caused by: org.apache.sysml.parser.ParseException: One or more errors found
during parsing (could not construct AST for file: hello.dml). Cannot proceed
ahead.
{code}
Even if the description attribute isn't being used for anything, given that it
is a valid metadata attribute, it shouldn't blow up the script when passed as a
function parameter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYSTEMML-530) Centralize built-in function names
[
https://issues.apache.org/jira/browse/SYSTEMML-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-530:
Description:
Currently, built-in functions are handled in various places in *.java files.
For instance, {{readMM}} and {{read.csv}} are handled in DataExpression.java.
{{writeMM}} and {{write.csv}} are handled in OutputStatement.java. Most others,
such as {{cbind}} and {{rbind}} are handled in BuiltinFunctionExpression.
It would be nice for all built-in function names to exist as constant strings
(or as an enum) in a single clear location so that a developer looking at the
project can go to a single place to see a definitive list of all built-in
functions.
was:
Currently, built-in functions are handled in various places in *.java files.
For instance, {{readMM}} and {{read.csv} are handled in DataExpression.java.
{{writeMM}} and {{write.csv}} are handled in OutputStatement.java. Most others,
such as {{cbind}} and {{rbind}} are handled in BuiltinFunctionExpression.
It would be nice for all built-in function names to exist as constant strings
(or as an enum) in a single clear location so that a developer looking at the
project can go to a single place to see a definitive list of all built-in
functions.
> Centralize built-in function names
> --
>
> Key: SYSTEMML-530
> URL: https://issues.apache.org/jira/browse/SYSTEMML-530
> Project: SystemML
> Issue Type: Improvement
> Components: Parser
>Reporter: Deron Eriksson
>
> Currently, built-in functions are handled in various places in *.java files.
> For instance, {{readMM}} and {{read.csv}} are handled in DataExpression.java.
> {{writeMM}} and {{write.csv}} are handled in OutputStatement.java. Most
> others, such as {{cbind}} and {{rbind}} are handled in
> BuiltinFunctionExpression.
> It would be nice for all built-in function names to exist as constant strings
> (or as an enum) in a single clear location so that a developer looking at the
> project can go to a single place to see a definitive list of all built-in
> functions.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYSTEMML-517) Update lang ref for read/write function boolean params
[ https://issues.apache.org/jira/browse/SYSTEMML-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152757#comment-15152757 ] Deron Eriksson commented on SYSTEMML-517: - Fixed by [PR71 | https://github.com/apache/incubator-systemml/pull/71] > Update lang ref for read/write function boolean params > -- > > Key: SYSTEMML-517 > URL: https://issues.apache.org/jira/browse/SYSTEMML-517 > Project: SystemML > Issue Type: Bug > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > DML requires boolean as uppercase (TRUE/FALSE), so the read/write function > parameters that are boolean (such as header) need to reflect this in the DML > language ref. > At the same time, parsing JSON with TRUE/FALSE instead of true/false throws a > parsing exception, so metadata files need to use true/false. > So, the docs need to reflect both of these (true/false for metadata, > TRUE/FALSE for DML function parameters). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-456) Refactor dml/pydml parsers for code deduplication
[ https://issues.apache.org/jira/browse/SYSTEMML-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-456. --- > Refactor dml/pydml parsers for code deduplication > - > > Key: SYSTEMML-456 > URL: https://issues.apache.org/jira/browse/SYSTEMML-456 > Project: SystemML > Issue Type: Improvement > Components: Parser >Reporter: Matthias Boehm >Assignee: Nakul Jindal >Priority: Critical > > The dml and pydml parsers exhibit to large extend duplicated code. We need to > clean this up in order to improvement maintainability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-468) Create Contributing to SystemML document
[ https://issues.apache.org/jira/browse/SYSTEMML-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145390#comment-15145390 ] Deron Eriksson commented on SYSTEMML-468: - Initial doc is a good intro the contributing to SystemML. If additional info is needed, we can create new issues. I'll mark as resolved. > Create Contributing to SystemML document > > > Key: SYSTEMML-468 > URL: https://issues.apache.org/jira/browse/SYSTEMML-468 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > Create a Contributing to SystemML document for developers and data scientists. > Describe our typical git workflow for contributing to the project (fork on > github, clone to local, checkout a branch and do work on branch, push to > github branch, file pull request, pull request reviewed, push additional > changes to github branch/pull request, pull request accepted and integrated > into project). > Describe basic IDE setup for working on SystemML code (move Eclipse debug > configuration info from Beginner's Guide to here). > Describe creation of a test class. > Describe running new code locally. > Describe running new code on Hadoop. > Describe running new code on Spark. > Describe running new code via MLContext. > Any other pointers that would help a new developer or data scientist > contribute to SystemML could go here. For instance, a data scientist might > want to contribute a new algorithm to SystemML. However, this algorithm > probably needs a test class, so the contribution may require more than DML. > The test class could be written by the data scientist, or perhaps a request > could be made for a developer to handle the test class. It's good to spell > out this kind of process to help grow our community. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-494) Remove warnings from regular GLM.dml execution
[
https://issues.apache.org/jira/browse/SYSTEMML-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15145397#comment-15145397
]
Deron Eriksson commented on SYSTEMML-494:
-
GLM.dml (main), GLM.dml (test), and GLM.pydml (test) updated to remove warnings.
Fixed by [PR67 | https://github.com/apache/incubator-systemml/pull/67]
> Remove warnings from regular GLM.dml execution
> --
>
> Key: SYSTEMML-494
> URL: https://issues.apache.org/jira/browse/SYSTEMML-494
> Project: SystemML
> Issue Type: Task
>Reporter: Deron Eriksson
>Assignee: Deron Eriksson
>
> If GLM.dml is run, the user sees 3 WARN messages. For instance, if I do the
> following:
> {code}
> $ hadoop jar ./lib/systemml-0.10.0-incubating-SNAPSHOT.jar -f
> scripts/algorithms/GLM.dml -nvargs X=myData.train.data.csv
> Y=myData.train.labels.csv B=logisticResult/B.csv fmt=csv dfam=2 link=2
> yneg=2.0 icpt=1 reg=0.0 tol=0.0001 moi=100 mii=10
> {code}
> I see:
> {code}
> 16/01/29 13:32:53 WARN parser.StatementBlock: WARNING:
> scripts/algorithms/GLM.dml -- line 357, column 14 -- Initialization of w
> depends on if-else execution
> 16/01/29 13:32:53 WARN parser.StatementBlock: WARNING:
> scripts/algorithms/GLM.dml -- line 357, column 14 -- Initialization of w
> depends on while execution
> 16/01/29 13:32:54 WARN util.NativeCodeLoader: Unable to load native-hadoop
> library for your platform... using builtin-java classes where applicable
> 16/01/29 13:32:54 WARN parser.StatementBlock: WARNING:
> scripts/algorithms/GLM.dml -- line 161, column 0 -- Variable termination_code
> defined with different value
> {code}
> For a new user to SystemML, it is disconcerting to see several warning
> messages, since that can imply that the user is doing something wrong.
> So perhaps the messages can be changed to INFO type messages, or the DML can
> be changed so as not to generate the warning messages. I would favor updating
> the DML script if possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (SYSTEMML-550) Add jMLC usage documentation
[ https://issues.apache.org/jira/browse/SYSTEMML-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson reassigned SYSTEMML-550: --- Assignee: Deron Eriksson > Add jMLC usage documentation > > > Key: SYSTEMML-550 > URL: https://issues.apache.org/jira/browse/SYSTEMML-550 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > SystemML needs a description of jMLC and examples of how to use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-550) Add jMLC usage documentation
[ https://issues.apache.org/jira/browse/SYSTEMML-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-550. --- > Add jMLC usage documentation > > > Key: SYSTEMML-550 > URL: https://issues.apache.org/jira/browse/SYSTEMML-550 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > SystemML needs a description of jMLC and examples of how to use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYSTEMML-550) Add jMLC usage documentation
[ https://issues.apache.org/jira/browse/SYSTEMML-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson resolved SYSTEMML-550. - Resolution: Fixed Resolved by [PR90|https://github.com/apache/incubator-systemml/pull/90] > Add jMLC usage documentation > > > Key: SYSTEMML-550 > URL: https://issues.apache.org/jira/browse/SYSTEMML-550 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > SystemML needs a description of jMLC and examples of how to use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-604) Undefined function error message not have line, col, and filename info
Deron Eriksson created SYSTEMML-604:
---
Summary: Undefined function error message not have line, col, and
filename info
Key: SYSTEMML-604
URL: https://issues.apache.org/jira/browse/SYSTEMML-604
Project: SystemML
Issue Type: Bug
Components: Parser
Reporter: Deron Eriksson
Priority: Minor
Given the following DML:
{code}
print("howdy");
a=foo();
{code}
Results in the following error message:
{code}Caused by: org.apache.sysml.parser.LanguageException: ERROR: null -- line
0, column 0 -- function foo is undefined in namespace .defaultNS
at
org.apache.sysml.parser.StatementBlock.isMergeableFunctionCallBlock(StatementBlock.java:201)
{code}
The line number, the column number, and the filename (if available) of the
undefined function should be displayed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SYSTEMML-586) Fix in-memory distribution for JMLC
[ https://issues.apache.org/jira/browse/SYSTEMML-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson resolved SYSTEMML-586. - Resolution: Fixed > Fix in-memory distribution for JMLC > --- > > Key: SYSTEMML-586 > URL: https://issues.apache.org/jira/browse/SYSTEMML-586 > Project: SystemML > Issue Type: Bug >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > The in-memory jar used for JMLC currently is not built. If it is built, it is > missing the dependencies needed in order to run. So, the minimal set of > dependencies needs to be added to the in-memory assembly for JMLC usage, and > the in-memory jar can then be included with the other distributions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-586) Fix in-memory distribution for JMLC
[ https://issues.apache.org/jira/browse/SYSTEMML-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-586. --- > Fix in-memory distribution for JMLC > --- > > Key: SYSTEMML-586 > URL: https://issues.apache.org/jira/browse/SYSTEMML-586 > Project: SystemML > Issue Type: Bug >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > The in-memory jar used for JMLC currently is not built. If it is built, it is > missing the dependencies needed in order to run. So, the minimal set of > dependencies needs to be added to the in-memory assembly for JMLC usage, and > the in-memory jar can then be included with the other distributions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-586) Fix in-memory distribution for JMLC
[ https://issues.apache.org/jira/browse/SYSTEMML-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15218966#comment-15218966 ] Deron Eriksson commented on SYSTEMML-586: - Fixed by [PR94|https://github.com/apache/incubator-systemml/pull/94] > Fix in-memory distribution for JMLC > --- > > Key: SYSTEMML-586 > URL: https://issues.apache.org/jira/browse/SYSTEMML-586 > Project: SystemML > Issue Type: Bug >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > The in-memory jar used for JMLC currently is not built. If it is built, it is > missing the dependencies needed in order to run. So, the minimal set of > dependencies needs to be added to the in-memory assembly for JMLC usage, and > the in-memory jar can then be included with the other distributions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-486) Modify standalone scripts to accept JVM size as configuration parameter
[ https://issues.apache.org/jira/browse/SYSTEMML-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-486. --- > Modify standalone scripts to accept JVM size as configuration parameter > --- > > Key: SYSTEMML-486 > URL: https://issues.apache.org/jira/browse/SYSTEMML-486 > Project: SystemML > Issue Type: Task >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > Modify the java invocation in .sh and .bat scripts to accept JVM size as > configuration parameters -- with a default value of 4g (or 2g). This would > give users a bit of flexibility when they are prototyping on their laptops. > Mention this setting in the standalone README.txt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-498) Create troubleshooting guide
[ https://issues.apache.org/jira/browse/SYSTEMML-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-498. --- > Create troubleshooting guide > > > Key: SYSTEMML-498 > URL: https://issues.apache.org/jira/browse/SYSTEMML-498 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYSTEMML-498) Create troubleshooting guide
[ https://issues.apache.org/jira/browse/SYSTEMML-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson resolved SYSTEMML-498. - Resolution: Fixed > Create troubleshooting guide > > > Key: SYSTEMML-498 > URL: https://issues.apache.org/jira/browse/SYSTEMML-498 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYSTEMML-498) Create troubleshooting guide
[ https://issues.apache.org/jira/browse/SYSTEMML-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson reassigned SYSTEMML-498: --- Assignee: Deron Eriksson > Create troubleshooting guide > > > Key: SYSTEMML-498 > URL: https://issues.apache.org/jira/browse/SYSTEMML-498 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-498) Create troubleshooting guide
[ https://issues.apache.org/jira/browse/SYSTEMML-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15229235#comment-15229235 ] Deron Eriksson commented on SYSTEMML-498: - As discussed on the mailing list, I'm going to go ahead and create a troubleshooting guide for issues like SYSTEMML-489. > Create troubleshooting guide > > > Key: SYSTEMML-498 > URL: https://issues.apache.org/jira/browse/SYSTEMML-498 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SYSTEMML-616) Cleanup exception handling apis/compiler/runtime
[
https://issues.apache.org/jira/browse/SYSTEMML-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227059#comment-15227059
]
Deron Eriksson edited comment on SYSTEMML-616 at 4/5/16 8:25 PM:
-
Here is a hierarchy of SystemML exceptions:
{code}
Throwable
┗ Exception
┣ DMLException (323 matches)
┃ ┣ AppException (not used)
┃ ┣ DMLDebuggerException (13 matches)
┃ ┣ DMLRuntimeException (3,689 matches)
┃ ┃ ┣ CacheException (82 matches)
┃ ┃ ┃ ┣ CacheIOException (26 matches)
┃ ┃ ┃ ┗ CacheStatusException (18 matches)
┃ ┃ ┗ DMLScriptException (39 matches)
┃ ┣ DMLUnsupportedOperationException (1,068 matches)
┃ ┣ HopsException (748 matches)
┃ ┣ LanguageException (390 matches)
┃ ┗ LopsException (596 matches)
┣ ParseException (320 matches)
┃ ┗ DMLParseException (50 matches)
┗ RuntimeException
┗ PackageRuntimeException (70 matches)
{code}
was (Author: deron):
Here is a hierarchy of SystemML exceptions:
{code}
Throwable
┗ Exception
┣ DMLException (323 matches)
┃ ┣ AppException (not used)
┃ ┣ DMLDebuggerException (13 matches)
┃ ┣ DMLRuntimeException (3,689 matches)
┃ ┃ ┣ CacheException (82 matches)
┃ ┃ ┃ ┣ CacheIOException (26 matches)
┃ ┃ ┃ ┗ CacheStatusException (18 matches)
┃ ┃ ┗ DMLScriptException (39 matches)
┃ ┣ DMLUnsupportedOperationException (1,068 matches)
┃ ┣ HopsException (748 matches)
┃ ┣ LanguageException (390 matches)
┃ ┗ LopsException (596 matches)
┣ ParseException (320 matches)
┃ ┗ DMLParseException (50 matches)
┗ RuntimeException
┗ PackageRuntimeException (70 matches)
{code}
> Cleanup exception handling apis/compiler/runtime
>
>
> Key: SYSTEMML-616
> URL: https://issues.apache.org/jira/browse/SYSTEMML-616
> Project: SystemML
> Issue Type: Improvement
> Components: APIs, Compiler, Runtime
>Reporter: Matthias Boehm
>Assignee: Matthias Boehm
>
> 1) Remove unnecessary exceptions (e.g., various subclasses of CacheException,
> DMLUnsupportedOperationException, AppException)
> 2) Fuse unnecessary deep exception hierarchies (e.g., DMLParseException)
> 3) Reinvestigation uncaught vs caught exceptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-621) Message for read error displays nested messages
Deron Eriksson created SYSTEMML-621:
---
Summary: Message for read error displays nested messages
Key: SYSTEMML-621
URL: https://issues.apache.org/jira/browse/SYSTEMML-621
Project: SystemML
Issue Type: Task
Components: Parser
Reporter: Deron Eriksson
Priority: Minor
DML such as the following
{code}
z=read();
{code}
generates an error message such as the following:
{code}
unable to process builtin function expression read:ERROR: example.dml -- line
1, column 3 -- read method must have at least filename parameter
{code}
The "unable to process builtin function expression read:ERROR: " is extraneous
and should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-622) Single variable PyDML script reports wrong line and column numbers
Deron Eriksson created SYSTEMML-622:
---
Summary: Single variable PyDML script reports wrong line and
column numbers
Key: SYSTEMML-622
URL: https://issues.apache.org/jira/browse/SYSTEMML-622
Project: SystemML
Issue Type: Bug
Components: Parser
Reporter: Deron Eriksson
Priority: Minor
A PyDML script consisting of a single string of alphanumeric characters such as
"f" generates the wrong line number and column number:
{code}
(syntaxError) - example.dml line 0:-1 no viable alternative at input 'f\n'
{code}
The position 'should' be 1:0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SYSTEMML-611) Enhance display of parsing errors for user
[
https://issues.apache.org/jira/browse/SYSTEMML-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson closed SYSTEMML-611.
---
> Enhance display of parsing errors for user
> --
>
> Key: SYSTEMML-611
> URL: https://issues.apache.org/jira/browse/SYSTEMML-611
> Project: SystemML
> Issue Type: Task
> Components: Parser
>Reporter: Deron Eriksson
>Assignee: Deron Eriksson
>
> Currently, if parsing errors occur, the actual messages are not displayed to
> standard output or standard error except via log4j. As a result, if a user
> does not have log4j configured, they do not see any of the actual parsing
> error messages, which makes it extremely difficult to fix DML/PyDML.
> As an example, executing the following code via DMLScript:
> {code}
> foo();
> {code}
> generates the following result to the console if log4j is not configured:
> {code}
> Exception in thread "main" org.apache.sysml.api.DMLException:
> org.apache.sysml.parser.ParseException: One or more errors found during
> parsing (could not construct AST for file: example.dml). Cannot proceed ahead.
> at org.apache.sysml.api.DMLScript.executeScript(DMLScript.java:350)
> at org.apache.sysml.api.DMLScript.main(DMLScript.java:197)
> Caused by: org.apache.sysml.parser.ParseException: One or more errors found
> during parsing (could not construct AST for file: example.dml). Cannot
> proceed ahead.
> at
> org.apache.sysml.parser.dml.DMLParserWrapper.parse(DMLParserWrapper.java:98)
> at org.apache.sysml.api.DMLScript.execute(DMLScript.java:588)
> at org.apache.sysml.api.DMLScript.executeScript(DMLScript.java:338)
> ... 1 more
> {code}
> There are a few issues to address here.
> 1) A stacktrace such as the one above does not help an end user to write/fix
> DML/PyDML. In fact, it detracts from the important information (the parse
> error message) that the user needs.
> 2) The actual parsing errors are needed by the end user (not the stacktrace),
> and these should be displayed to standard output/standard error (ie, the
> console) if SystemML is being invoked via DMLScript.
> 3) The parsing error information should be available at higher levels of the
> call stack (ie, in DMLScript and MLContext, for example). Allowing this
> information to be available at these higher levels has benefits, for example
> to display the parse error information in a notebook via MLContext.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-624) writeMM and write.csv code currently not called
Deron Eriksson created SYSTEMML-624:
---
Summary: writeMM and write.csv code currently not called
Key: SYSTEMML-624
URL: https://issues.apache.org/jira/browse/SYSTEMML-624
Project: SystemML
Issue Type: Bug
Components: Parser
Reporter: Deron Eriksson
Priority: Minor
Code exists in the OutputStatement(String fname, FunctionCallIdentifier fci,
String filename, int blp, int bcp, int elp, int ecp) constructor to support
writeMM and write.csv functions. However, this constructor is never called, so
writeMM and write.csv are currently not supported.
See setOutputStatement(ParserRuleContext ctx, ArrayList
paramExpression, StatementInfo info) of CommonSyntacticValidator, which calls
the other OutputStatement constructor with {code}info.stmt = new
OutputStatement((DataIdentifier) paramExpression.get(0).getExpr(),
DataOp.WRITE, fileName, line, col, line, col);{code}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYSTEMML-624) writeMM and write.csv code currently not called
[
https://issues.apache.org/jira/browse/SYSTEMML-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-624:
Description:
Code exists in the {code}OutputStatement(String fname, FunctionCallIdentifier
fci, String filename, int blp, int bcp, int elp, int ecp){code} constructor to
support writeMM and write.csv functions. However, this constructor is never
called, so writeMM and write.csv are currently not supported.
See {code}setOutputStatement(ParserRuleContext ctx,
ArrayList paramExpression, StatementInfo info){code} of
CommonSyntacticValidator, which calls the other OutputStatement constructor
with {code}info.stmt = new OutputStatement((DataIdentifier)
paramExpression.get(0).getExpr(), DataOp.WRITE, fileName, line, col, line,
col);{code}.
was:
Code exists in the {code}OutputStatement(String fname, FunctionCallIdentifier
fci, String filename, int blp, int bcp, int elp, int ecp){code} constructor to
support writeMM and write.csv functions. However, this constructor is never
called, so writeMM and write.csv are currently not supported.
See {code}setOutputStatement(ParserRuleContext ctx,
ArrayList paramExpression, StatementInfo info) of
CommonSyntacticValidator{code}, which calls the other OutputStatement
constructor with {code}info.stmt = new OutputStatement((DataIdentifier)
paramExpression.get(0).getExpr(), DataOp.WRITE, fileName, line, col, line,
col);{code}.
> writeMM and write.csv code currently not called
> ---
>
> Key: SYSTEMML-624
> URL: https://issues.apache.org/jira/browse/SYSTEMML-624
> Project: SystemML
> Issue Type: Bug
> Components: Parser
>Reporter: Deron Eriksson
>Priority: Minor
>
> Code exists in the {code}OutputStatement(String fname, FunctionCallIdentifier
> fci, String filename, int blp, int bcp, int elp, int ecp){code} constructor
> to support writeMM and write.csv functions. However, this constructor is
> never called, so writeMM and write.csv are currently not supported.
> See {code}setOutputStatement(ParserRuleContext ctx,
> ArrayList paramExpression, StatementInfo info){code} of
> CommonSyntacticValidator, which calls the other OutputStatement constructor
> with {code}info.stmt = new OutputStatement((DataIdentifier)
> paramExpression.get(0).getExpr(), DataOp.WRITE, fileName, line, col, line,
> col);{code}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYSTEMML-624) writeMM and write.csv code currently not called
[
https://issues.apache.org/jira/browse/SYSTEMML-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-624:
Description:
Code exists in the {code}OutputStatement(String fname, FunctionCallIdentifier
fci, String filename, int blp, int bcp, int elp, int ecp){code} constructor to
support writeMM and write.csv functions. However, this constructor is never
called, so writeMM and write.csv are currently not supported.
See {code}setOutputStatement(ParserRuleContext ctx,
ArrayList paramExpression, StatementInfo info) of
CommonSyntacticValidator{code}, which calls the other OutputStatement
constructor with {code}info.stmt = new OutputStatement((DataIdentifier)
paramExpression.get(0).getExpr(), DataOp.WRITE, fileName, line, col, line,
col);{code}.
was:
Code exists in the OutputStatement(String fname, FunctionCallIdentifier fci,
String filename, int blp, int bcp, int elp, int ecp) constructor to support
writeMM and write.csv functions. However, this constructor is never called, so
writeMM and write.csv are currently not supported.
See setOutputStatement(ParserRuleContext ctx, ArrayList
paramExpression, StatementInfo info) of CommonSyntacticValidator, which calls
the other OutputStatement constructor with {code}info.stmt = new
OutputStatement((DataIdentifier) paramExpression.get(0).getExpr(),
DataOp.WRITE, fileName, line, col, line, col);{code}.
> writeMM and write.csv code currently not called
> ---
>
> Key: SYSTEMML-624
> URL: https://issues.apache.org/jira/browse/SYSTEMML-624
> Project: SystemML
> Issue Type: Bug
> Components: Parser
>Reporter: Deron Eriksson
>Priority: Minor
>
> Code exists in the {code}OutputStatement(String fname, FunctionCallIdentifier
> fci, String filename, int blp, int bcp, int elp, int ecp){code} constructor
> to support writeMM and write.csv functions. However, this constructor is
> never called, so writeMM and write.csv are currently not supported.
> See {code}setOutputStatement(ParserRuleContext ctx,
> ArrayList paramExpression, StatementInfo info) of
> CommonSyntacticValidator{code}, which calls the other OutputStatement
> constructor with {code}info.stmt = new OutputStatement((DataIdentifier)
> paramExpression.get(0).getExpr(), DataOp.WRITE, fileName, line, col, line,
> col);{code}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-586) Fix in-memory distribution for JMLC
Deron Eriksson created SYSTEMML-586: --- Summary: Fix in-memory distribution for JMLC Key: SYSTEMML-586 URL: https://issues.apache.org/jira/browse/SYSTEMML-586 Project: SystemML Issue Type: Bug Reporter: Deron Eriksson Assignee: Deron Eriksson The in-memory jar used for JMLC currently is not built. If it is built, it is missing the dependencies needed in order to run. So, the minimal set of dependencies needs to be added to the in-memory assembly for JMLC usage, and the in-memory jar can then be included with the other distributions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-593) MLContext Redesign
Deron Eriksson created SYSTEMML-593: --- Summary: MLContext Redesign Key: SYSTEMML-593 URL: https://issues.apache.org/jira/browse/SYSTEMML-593 Project: SystemML Issue Type: Improvement Components: APIs Reporter: Deron Eriksson Assignee: Deron Eriksson This JIRA proposes a redesign of the Java MLContext API with several goals: • Simplify the user experience • Encapsulate primary entities using object-oriented concepts • Make API extensible for external users • Make API extensible for SystemML developers • Locate all user-interaction classes, interfaces, etc under a single API package • Extensive Javadocs for all classes in the API • Potentially fold JMLC API into MLContext so as to have a single programmatic API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYSTEMML-593) MLContext Redesign
[ https://issues.apache.org/jira/browse/SYSTEMML-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson updated SYSTEMML-593: Attachment: Design Document - MLContext API Redesign.pdf > MLContext Redesign > -- > > Key: SYSTEMML-593 > URL: https://issues.apache.org/jira/browse/SYSTEMML-593 > Project: SystemML > Issue Type: Improvement > Components: APIs >Reporter: Deron Eriksson >Assignee: Deron Eriksson > Attachments: Design Document - MLContext API Redesign.pdf > > > This JIRA proposes a redesign of the Java MLContext API with several goals: > • Simplify the user experience > • Encapsulate primary entities using object-oriented concepts > • Make API extensible for external users > • Make API extensible for SystemML developers > • Locate all user-interaction classes, interfaces, etc under a single API > package > • Extensive Javadocs for all classes in the API > • Potentially fold JMLC API into MLContext so as to have a single > programmatic API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYSTEMML-593) MLContext Redesign
[ https://issues.apache.org/jira/browse/SYSTEMML-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson updated SYSTEMML-593: Attachment: Design Document - MLContext API Redesign.pdf > MLContext Redesign > -- > > Key: SYSTEMML-593 > URL: https://issues.apache.org/jira/browse/SYSTEMML-593 > Project: SystemML > Issue Type: Improvement > Components: APIs >Reporter: Deron Eriksson >Assignee: Deron Eriksson > Attachments: Design Document - MLContext API Redesign.pdf > > > This JIRA proposes a redesign of the Java MLContext API with several goals: > • Simplify the user experience > • Encapsulate primary entities using object-oriented concepts > • Make API extensible for external users > • Make API extensible for SystemML developers > • Locate all user-interaction classes, interfaces, etc under a single API > package > • Extensive Javadocs for all classes in the API > • Potentially fold JMLC API into MLContext so as to have a single > programmatic API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYSTEMML-593) MLContext Redesign
[ https://issues.apache.org/jira/browse/SYSTEMML-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson updated SYSTEMML-593: Attachment: (was: Design Document - MLContext API Redesign.pdf) > MLContext Redesign > -- > > Key: SYSTEMML-593 > URL: https://issues.apache.org/jira/browse/SYSTEMML-593 > Project: SystemML > Issue Type: Improvement > Components: APIs >Reporter: Deron Eriksson >Assignee: Deron Eriksson > Attachments: Design Document - MLContext API Redesign.pdf > > > This JIRA proposes a redesign of the Java MLContext API with several goals: > • Simplify the user experience > • Encapsulate primary entities using object-oriented concepts > • Make API extensible for external users > • Make API extensible for SystemML developers > • Locate all user-interaction classes, interfaces, etc under a single API > package > • Extensive Javadocs for all classes in the API > • Potentially fold JMLC API into MLContext so as to have a single > programmatic API -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-543) Refactor MLContext in Scala
[
https://issues.apache.org/jira/browse/SYSTEMML-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15180237#comment-15180237
]
Deron Eriksson commented on SYSTEMML-543:
-
[~tommy_cug] Thank you very much for your interest. I am currently
investigating refactoring the current MLContext API (SYSTEMML-544), so it would
be best to wait before working on this until after any of those potential
changes have been accepted into the project.
> Refactor MLContext in Scala
> ---
>
> Key: SYSTEMML-543
> URL: https://issues.apache.org/jira/browse/SYSTEMML-543
> Project: SystemML
> Issue Type: Improvement
>Reporter: Mike Dusenberry
>
> Our {{MLContext}} API relies on a myriad of optional parameters as
> conveniences for end-users, which has led to our Java implementation growing
> in size. Moving to Scala will allow us to use default parameters and
> continue to expand the capabilities of the API in a clean way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-551) Enhance jMLC javadocs
Deron Eriksson created SYSTEMML-551: --- Summary: Enhance jMLC javadocs Key: SYSTEMML-551 URL: https://issues.apache.org/jira/browse/SYSTEMML-551 Project: SystemML Issue Type: Task Components: Documentation Reporter: Deron Eriksson jMLC needs its Javadocs enhanced to better explain the classes and methods involved in its usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-550) Add jMLC usage documentation
Deron Eriksson created SYSTEMML-550: --- Summary: Add jMLC usage documentation Key: SYSTEMML-550 URL: https://issues.apache.org/jira/browse/SYSTEMML-550 Project: SystemML Issue Type: Task Components: Documentation Reporter: Deron Eriksson SystemML needs a description of jMLC and examples of how to use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-549) Update OptimizerUtils.OptimizationLevel javadocs
Deron Eriksson created SYSTEMML-549:
---
Summary: Update OptimizerUtils.OptimizationLevel javadocs
Key: SYSTEMML-549
URL: https://issues.apache.org/jira/browse/SYSTEMML-549
Project: SystemML
Issue Type: Task
Components: Documentation
Reporter: Deron Eriksson
The javadoc description for the OptimizerUtils.OptimizationLevel enum lists the
following 5 levels with descriptions.
{code}
O0 STATIC
O1 MEMORY_BASED
O2 MEMORY_BASED
O3 GLOBAL TIME_MEMORY_BASED
O4 DEBUG MODE
{code}
However, the actual 6 optimization levels are:
{code}
O0_LOCAL_STATIC
O1_LOCAL_MEMORY_MIN
O2_LOCAL_MEMORY_DEFAULT
O3_LOCAL_RESOURCE_TIME_MEMORY
O4_GLOBAL_TIME_MEMORY
O5_DEBUG_MODE
{code}
Some minor HTML tags would also help readability in the javadocs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYSTEMML-551) Enhance JMLC javadocs
[ https://issues.apache.org/jira/browse/SYSTEMML-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson updated SYSTEMML-551: Summary: Enhance JMLC javadocs (was: Enhance jMLC javadocs) > Enhance JMLC javadocs > - > > Key: SYSTEMML-551 > URL: https://issues.apache.org/jira/browse/SYSTEMML-551 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson > > jMLC needs its Javadocs enhanced to better explain the classes and methods > involved in its usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYSTEMML-551) Enhance JMLC javadocs
[ https://issues.apache.org/jira/browse/SYSTEMML-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson updated SYSTEMML-551: Description: JMLC needs its Javadocs enhanced to better explain the classes and methods involved in its usage. (was: jMLC needs its Javadocs enhanced to better explain the classes and methods involved in its usage.) > Enhance JMLC javadocs > - > > Key: SYSTEMML-551 > URL: https://issues.apache.org/jira/browse/SYSTEMML-551 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson > > JMLC needs its Javadocs enhanced to better explain the classes and methods > involved in its usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYSTEMML-551) Enhance JMLC javadocs
[ https://issues.apache.org/jira/browse/SYSTEMML-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson reassigned SYSTEMML-551: --- Assignee: Deron Eriksson > Enhance JMLC javadocs > - > > Key: SYSTEMML-551 > URL: https://issues.apache.org/jira/browse/SYSTEMML-551 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > JMLC needs its Javadocs enhanced to better explain the classes and methods > involved in its usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-610) Add Databricks Notebook example to MLContext documentation
Deron Eriksson created SYSTEMML-610: --- Summary: Add Databricks Notebook example to MLContext documentation Key: SYSTEMML-610 URL: https://issues.apache.org/jira/browse/SYSTEMML-610 Project: SystemML Issue Type: Task Reporter: Deron Eriksson Assignee: Deron Eriksson Add an example of configuring a Databricks Notebook to use SystemML to the Spark MLContext Programming Guide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-615) Two adjacent identifiers in DML produce concatenated error message
Deron Eriksson created SYSTEMML-615:
---
Summary: Two adjacent identifiers in DML produce concatenated
error message
Key: SYSTEMML-615
URL: https://issues.apache.org/jira/browse/SYSTEMML-615
Project: SystemML
Issue Type: Bug
Components: Parser
Reporter: Deron Eriksson
Priority: Minor
A DML script consisting of "foo foo" or "foo foo foo" produces an error message
where the first two identifiers have been concatenated:
{code}
(syntaxError) - example.dml line 1:4 no viable alternative at input 'foofoo'
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYSTEMML-614) Single variable DML script reports wrong line number
Deron Eriksson created SYSTEMML-614:
---
Summary: Single variable DML script reports wrong line number
Key: SYSTEMML-614
URL: https://issues.apache.org/jira/browse/SYSTEMML-614
Project: SystemML
Issue Type: Bug
Components: Parser
Reporter: Deron Eriksson
Priority: Minor
A DML script consisting of a single string of alphanumeric characters such as
"f" or "foo" generates the wrong line number (2 instead of 1):
{code}
(syntaxError) - example.dml line 2:0 no viable alternative at input 'f'
{code}
{code}
(syntaxError) - example.dml line 2:0 no viable alternative at input 'foo'
{code}
For comparison, a DML script consisting of "foo()" generates the correct line
number (1):
{code}
(validationError) - example.dml line 1:0 function call needs to have lvalue
(Quickfix: change it to 'tmpVar = foo(...)')
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYSTEMML-614) Single variable DML script reports wrong line number
[
https://issues.apache.org/jira/browse/SYSTEMML-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-614:
Description:
A DML script consisting of a single string of alphanumeric characters such as
"f" or "foo" generates the wrong line number (2 instead of 1) in error message:
{code}
(syntaxError) - example.dml line 2:0 no viable alternative at input 'f'
{code}
{code}
(syntaxError) - example.dml line 2:0 no viable alternative at input 'foo'
{code}
For comparison, a DML script consisting of "foo()" generates the correct line
number (1) in error message:
{code}
(validationError) - example.dml line 1:0 function call needs to have lvalue
(Quickfix: change it to 'tmpVar = foo(...)')
{code}
was:
A DML script consisting of a single string of alphanumeric characters such as
"f" or "foo" generates the wrong line number (2 instead of 1):
{code}
(syntaxError) - example.dml line 2:0 no viable alternative at input 'f'
{code}
{code}
(syntaxError) - example.dml line 2:0 no viable alternative at input 'foo'
{code}
For comparison, a DML script consisting of "foo()" generates the correct line
number (1):
{code}
(validationError) - example.dml line 1:0 function call needs to have lvalue
(Quickfix: change it to 'tmpVar = foo(...)')
{code}
> Single variable DML script reports wrong line number
>
>
> Key: SYSTEMML-614
> URL: https://issues.apache.org/jira/browse/SYSTEMML-614
> Project: SystemML
> Issue Type: Bug
> Components: Parser
>Reporter: Deron Eriksson
>Priority: Minor
>
> A DML script consisting of a single string of alphanumeric characters such as
> "f" or "foo" generates the wrong line number (2 instead of 1) in error
> message:
> {code}
> (syntaxError) - example.dml line 2:0 no viable alternative at input 'f'
> {code}
> {code}
> (syntaxError) - example.dml line 2:0 no viable alternative at input 'foo'
> {code}
> For comparison, a DML script consisting of "foo()" generates the correct line
> number (1) in error message:
> {code}
> (validationError) - example.dml line 1:0 function call needs to have lvalue
> (Quickfix: change it to 'tmpVar = foo(...)')
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYSTEMML-503) Update license for CSS and JS
[ https://issues.apache.org/jira/browse/SYSTEMML-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15216831#comment-15216831 ] Deron Eriksson commented on SYSTEMML-503: - Fixed by [PR64|https://github.com/apache/incubator-systemml/pull/64] and [PR82|https://github.com/apache/incubator-systemml/pull/82]. > Update license for CSS and JS > - > > Key: SYSTEMML-503 > URL: https://issues.apache.org/jira/browse/SYSTEMML-503 > Project: SystemML > Issue Type: Task >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > IPMC review found project LICENSE needs to include licenses for CSS and JS in > docs/. > "LICENSE is missing: > Bootstrap [1] (MIT licensed) > Modernizr [2] (MIT/BSD licensed) > Polyfill [2] (MIT/BSD licensed) > Respond [2] (MIT/GPL licensed) > Normalize [3] (MIT licensed) > AnchorJS [5] (MIT licensed) > JQuery [6] (MIT licensed) > ... > 1. ./docs/js/vendor/bootstrap.min.js > 2. ./docs/js/vendor/modernizr-2.6.1-respond-1.1.0.min.js > 3. ./docs/css/bootstrap.min.css > ... > 5. ./docs/js/vendor/anchor.min.js > 6. ./docs/js/vendor/jquery-1.12.0.min.js" > Verify that all of these libraries are actually being used and if any are not > required, remove them. > Verify the licenses and update project LICENSE accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-503) Update license for CSS and JS
[ https://issues.apache.org/jira/browse/SYSTEMML-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-503. --- > Update license for CSS and JS > - > > Key: SYSTEMML-503 > URL: https://issues.apache.org/jira/browse/SYSTEMML-503 > Project: SystemML > Issue Type: Task >Reporter: Deron Eriksson >Assignee: Deron Eriksson > > IPMC review found project LICENSE needs to include licenses for CSS and JS in > docs/. > "LICENSE is missing: > Bootstrap [1] (MIT licensed) > Modernizr [2] (MIT/BSD licensed) > Polyfill [2] (MIT/BSD licensed) > Respond [2] (MIT/GPL licensed) > Normalize [3] (MIT licensed) > AnchorJS [5] (MIT licensed) > JQuery [6] (MIT licensed) > ... > 1. ./docs/js/vendor/bootstrap.min.js > 2. ./docs/js/vendor/modernizr-2.6.1-respond-1.1.0.min.js > 3. ./docs/css/bootstrap.min.css > ... > 5. ./docs/js/vendor/anchor.min.js > 6. ./docs/js/vendor/jquery-1.12.0.min.js" > Verify that all of these libraries are actually being used and if any are not > required, remove them. > Verify the licenses and update project LICENSE accordingly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYSTEMML-548) Add Python examples to Spark MLContext Programming Guide
[ https://issues.apache.org/jira/browse/SYSTEMML-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson resolved SYSTEMML-548. - Resolution: Fixed > Add Python examples to Spark MLContext Programming Guide > > > Key: SYSTEMML-548 > URL: https://issues.apache.org/jira/browse/SYSTEMML-548 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Mike Dusenberry > > Add Python examples to the Spark MLContext Programming Guide. The first > example can be Python independent of a notebook. The second example can be > Python in a notebook. > [~mwdus...@us.ibm.com] is currently developing working Python examples > including a notebook, so this work can serve as the basis for this > documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYSTEMML-548) Add Python examples to Spark MLContext Programming Guide
[ https://issues.apache.org/jira/browse/SYSTEMML-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson closed SYSTEMML-548. --- > Add Python examples to Spark MLContext Programming Guide > > > Key: SYSTEMML-548 > URL: https://issues.apache.org/jira/browse/SYSTEMML-548 > Project: SystemML > Issue Type: Task > Components: Documentation >Reporter: Deron Eriksson >Assignee: Mike Dusenberry > > Add Python examples to the Spark MLContext Programming Guide. The first > example can be Python independent of a notebook. The second example can be > Python in a notebook. > [~mwdus...@us.ibm.com] is currently developing working Python examples > including a notebook, so this work can serve as the basis for this > documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-606) Update ANTLR version
Deron Eriksson created SYSTEMML-606: --- Summary: Update ANTLR version Key: SYSTEMML-606 URL: https://issues.apache.org/jira/browse/SYSTEMML-606 Project: SystemML Issue Type: Task Components: Build Reporter: Deron Eriksson Priority: Minor Current version of ANTLR in SystemML is v4.3. When running SystemML on current Databricks Notebook via MLContext, we see this message: "ANTLR Tool version 4.3 used for code generation does not match the current runtime version 4.5.1" We can update ANTLR version in pom.xml from 4.3 to 4.5.1 (and run test suite to verify that nothing is broken). This has the benefits of moving us to a later version of ANTLR and should remove the ANTLR version messages when running in Databricks Notebook. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYSTEMML-611) Enhance display of parsing errors for user
[
https://issues.apache.org/jira/browse/SYSTEMML-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-611:
Description:
Currently, if parsing errors occur, the actual messages are not displayed to
standard output or standard error except via log4j. As a result, if a user does
not have log4j configured, they do not see any of the actual parsing error
messages, which makes it extremely difficult to fix DML/PyDML.
As an example, executing the following code via DMLScript:
{code}
foo();
{code}
generates the following result to the console if log4j is not configured:
{code}
Exception in thread "main" org.apache.sysml.api.DMLException:
org.apache.sysml.parser.ParseException: One or more errors found during parsing
(could not construct AST for file: example.dml). Cannot proceed ahead.
at org.apache.sysml.api.DMLScript.executeScript(DMLScript.java:350)
at org.apache.sysml.api.DMLScript.main(DMLScript.java:197)
Caused by: org.apache.sysml.parser.ParseException: One or more errors found
during parsing (could not construct AST for file: example.dml). Cannot proceed
ahead.
at
org.apache.sysml.parser.dml.DMLParserWrapper.parse(DMLParserWrapper.java:98)
at org.apache.sysml.api.DMLScript.execute(DMLScript.java:588)
at org.apache.sysml.api.DMLScript.executeScript(DMLScript.java:338)
... 1 more
{code}
There are a few issues to address here.
1) A stacktrace such as the one above does not help an end user to write/fix
DML/PyDML. In fact, it detracts from the important information (the parse error
message) that the user needs.
2) The actual parsing errors are needed by the end user (not the stacktrace),
and these should be displayed to standard output/standard error (ie, the
console) if SystemML is being invoked via DMLScript.
3) The parsing error information should be available at higher levels of the
call stack (ie, in DMLScript and MLContext, for example). Allowing this
information to be available at these higher levels has benefits, for example to
display the parse error information in a notebook via MLContext.
was:
Currently, if parsing errors occur, the actual messages are not displayed to
standard output or standard error except via log4j. As a result, if a user does
not have log4j configured, they do not see any of the actual parsing error
messages, which makes it extremely difficult to fix DML/PyDML.
As an example, executing the following code via DMLScript:
{code}
foo();
{code}
generates the following result to the console if log4j is not configured:
{code}
Exception in thread "main" org.apache.sysml.api.DMLException:
org.apache.sysml.parser.ParseException: One or more errors found during parsing
(could not construct AST for file: example.dml). Cannot proceed ahead.
at org.apache.sysml.api.DMLScript.executeScript(DMLScript.java:350)
at org.apache.sysml.api.DMLScript.main(DMLScript.java:197)
Caused by: org.apache.sysml.parser.ParseException: One or more errors found
during parsing (could not construct AST for file: example.dml). Cannot proceed
ahead.
at
org.apache.sysml.parser.dml.DMLParserWrapper.parse(DMLParserWrapper.java:98)
at org.apache.sysml.api.DMLScript.execute(DMLScript.java:588)
at org.apache.sysml.api.DMLScript.executeScript(DMLScript.java:338)
... 1 more
{code}
There are a few issues to address here.
1) A stacktrace such as the one above does not help an end user to write/fix
DML/PyDML. In fact, it detracts from the import information (the parse error
message) that the user needs.
2) The actual parsing errors are needed by the end user (not the stacktrace),
and these should be displayed to standard output/standard error (ie, the
console) if SystemML is being invoked via DMLScript.
3) The parsing error information should be available at higher levels of the
call stack (ie, in DMLScript and MLContext, for example). Allowing this
information to be available at these higher levels has benefits, for example to
display the parse error information in a notebook via MLContext.
> Enhance display of parsing errors for user
> --
>
> Key: SYSTEMML-611
> URL: https://issues.apache.org/jira/browse/SYSTEMML-611
> Project: SystemML
> Issue Type: Task
> Components: Parser
>Reporter: Deron Eriksson
>Assignee: Deron Eriksson
>
> Currently, if parsing errors occur, the actual messages are not displayed to
> standard output or standard error except via log4j. As a result, if a user
> does not have log4j configured, they do not see any of the actual parsing
> error messages, which makes it extremely difficult to fix DML/PyDML.
> As an example, executing the following code via DMLScript:
> {code}
> foo();
> {code}
> generates the following result to the
[jira] [Assigned] (SYSTEMML-649) JMLC/MLContext support for scalar output variables
[ https://issues.apache.org/jira/browse/SYSTEMML-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deron Eriksson reassigned SYSTEMML-649: --- Assignee: Deron Eriksson > JMLC/MLContext support for scalar output variables > -- > > Key: SYSTEMML-649 > URL: https://issues.apache.org/jira/browse/SYSTEMML-649 > Project: SystemML > Issue Type: Task > Components: APIs >Reporter: Matthias Boehm >Assignee: Deron Eriksson > > Right now neither JMLC nor MLContext supports scalar output variables. This > task aims to extend both APIs with the required primitives. > The workaround is to cast any output scalar on script-level with as.matrix to > a 1-1 matrix and handle it in the calling application. However, especially > with MLContext this puts an unnecessary burden on the user as he needs to > deal with RDDs for a simple scalar too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYSTEMML-625) Handle circular import references
[
https://issues.apache.org/jira/browse/SYSTEMML-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson resolved SYSTEMML-625.
-
Resolution: Fixed
> Handle circular import references
> -
>
> Key: SYSTEMML-625
> URL: https://issues.apache.org/jira/browse/SYSTEMML-625
> Project: SystemML
> Issue Type: Sub-task
> Components: Parser
>Reporter: Deron Eriksson
>Assignee: Glenn Weidner
>
> Suppose we have a DML file named "example.dml" that contains a source call to
> itself:
> {code}
> source("./example.dml") as example;
> {code}
> This produces an infinite loop that gives:
> {code}
> Exception in thread "main" java.lang.StackOverflowError
> {code}
> Similar error occurs for other types of circular references such as script1
> imports script2 imports script3 imports1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYSTEMML-649) JMLC/MLContext support for scalar output variables
[ https://issues.apache.org/jira/browse/SYSTEMML-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256804#comment-15256804 ] Deron Eriksson commented on SYSTEMML-649: - Thank you [~mboehm7]. I'll take a look at that too. I will let you know if I need any guidance. > JMLC/MLContext support for scalar output variables > -- > > Key: SYSTEMML-649 > URL: https://issues.apache.org/jira/browse/SYSTEMML-649 > Project: SystemML > Issue Type: Task > Components: APIs >Reporter: Matthias Boehm >Assignee: Deron Eriksson > > Right now neither JMLC nor MLContext supports scalar output variables. This > task aims to extend both APIs with the required primitives. > The workaround is to cast any output scalar on script-level with as.matrix to > a 1-1 matrix and handle it in the calling application. However, especially > with MLContext this puts an unnecessary burden on the user as he needs to > deal with RDDs for a simple scalar too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYSTEMML-651) Fix scalar input support for JMLC
Deron Eriksson created SYSTEMML-651:
---
Summary: Fix scalar input support for JMLC
Key: SYSTEMML-651
URL: https://issues.apache.org/jira/browse/SYSTEMML-651
Project: SystemML
Issue Type: Bug
Components: APIs
Reporter: Deron Eriksson
Assignee: Deron Eriksson
Priority: Minor
Currently scalar input variables via JMLC do not work.
Sample DML (matrix input, scalar input, and a matrix output):
{code}
inMatrix = read("./tmp/inMatrix", rows=-1, cols=-1);
print('inMatrix: ' + nrow(inMatrix) + 'x' + ncol(inMatrix));
inScalar = read("./tmp/inScalar", data_type="scalar", value_type="int");
print('inScalar: ' + inScalar);
outMatrix = matrix("1 2 3 0", rows=2, cols=2);
print('outMatrix: ' + nrow(outMatrix) + 'x' + ncol(outMatrix));
write(outMatrix, "./tmp", format="text");
{code}
JMLC code:
{code}
Connection conn = new Connection();
String dml = conn.readScript("scalar-test.dml");
PreparedScript script = conn.prepareScript(dml, new String[] { "inMatrix",
"inScalar" }, new String[] { "outMatrix" }, false);
double[][] inMatrix = matrix(2, 2, new double[] { 1, 2, 3, 4 });
int inScalar = 5;
script.setMatrix("inMatrix", inMatrix);
script.setScalar("inScalar", inScalar);
ResultVariables results = script.executeScript();
double[][] result = results.getMatrix("outMatrix");
{code}
Generates the following error:
{code}
Exception in thread "main" org.apache.sysml.runtime.DMLRuntimeException:
org.apache.sysml.runtime.DMLRuntimeException: ERROR: Runtime error in program
block generated from statement block between lines 1 and 9 -- Error evaluating
instruction: CP°read°_Var4·SCALAR·INT·false°./tmp/inScalar·SCALAR·STRING·true
at
org.apache.sysml.runtime.controlprogram.Program.execute(Program.java:152)
at
org.apache.sysml.api.jmlc.PreparedScript.executeScript(PreparedScript.java:390)
at org.apache.sysml.JMLCExampleScalar.main(JMLCExampleScalar.java:26)
Caused by: org.apache.sysml.runtime.DMLRuntimeException: ERROR: Runtime error
in program block generated from statement block between lines 1 and 9 -- Error
evaluating instruction:
CP°read°_Var4·SCALAR·INT·false°./tmp/inScalar·SCALAR·STRING·true
at
org.apache.sysml.runtime.controlprogram.ProgramBlock.executeSingleInstruction(ProgramBlock.java:333)
at
org.apache.sysml.runtime.controlprogram.ProgramBlock.executeInstructions(ProgramBlock.java:222)
at
org.apache.sysml.runtime.controlprogram.ProgramBlock.execute(ProgramBlock.java:166)
at
org.apache.sysml.runtime.controlprogram.Program.execute(Program.java:145)
... 2 more
Caused by: org.apache.sysml.runtime.DMLRuntimeException:
java.io.FileNotFoundException: File tmp/inScalar does not exist
{code}
The matrix input and output work fine.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYSTEMML-649) JMLC/MLContext support for scalar output variables
[
https://issues.apache.org/jira/browse/SYSTEMML-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256721#comment-15256721
]
Deron Eriksson commented on SYSTEMML-649:
-
Do scalar inputs via JMLC currently work? If I have this DML:
{code}
inMatrix = read("./tmp/inMatrix", rows=-1, cols=-1);
print('inMatrix: ' + nrow(inMatrix) + 'x' + ncol(inMatrix));
inScalar = read("./tmp/inScalar", data_type="scalar", value_type="int");
print('inScalar: ' + inScalar);
outMatrix = matrix("1 2 3 0", rows=2, cols=2);
print('outMatrix: ' + nrow(outMatrix) + 'x' + ncol(outMatrix));
write(outMatrix, "./tmp", format="text");
{code}
and I do this:
{code}
Connection conn = new Connection();
String dml = conn.readScript("scalar-test.dml");
PreparedScript script = conn.prepareScript(dml, new String[] { "inMatrix",
"inScalar" }, new String[] { "outMatrix" }, false);
double[][] inMatrix = matrix(2, 2, new double[] { 1, 2, 3, 4 });
int inScalar = 5;
script.setMatrix("inMatrix", inMatrix);
script.setScalar("inScalar", inScalar);
ResultVariables results = script.executeScript();
double[][] result = results.getMatrix("outMatrix");
{code}
I get:
{code}
Exception in thread "main" org.apache.sysml.runtime.DMLRuntimeException:
org.apache.sysml.runtime.DMLRuntimeException: ERROR: Runtime error in program
block generated from statement block between lines 1 and 9 -- Error evaluating
instruction: CP°read°_Var4·SCALAR·INT·false°./tmp/inScalar·SCALAR·STRING·true
at
org.apache.sysml.runtime.controlprogram.Program.execute(Program.java:152)
at
org.apache.sysml.api.jmlc.PreparedScript.executeScript(PreparedScript.java:390)
at org.apache.sysml.JMLCExampleScalar.main(JMLCExampleScalar.java:26)
Caused by: org.apache.sysml.runtime.DMLRuntimeException: ERROR: Runtime error
in program block generated from statement block between lines 1 and 9 -- Error
evaluating instruction:
CP°read°_Var4·SCALAR·INT·false°./tmp/inScalar·SCALAR·STRING·true
at
org.apache.sysml.runtime.controlprogram.ProgramBlock.executeSingleInstruction(ProgramBlock.java:333)
at
org.apache.sysml.runtime.controlprogram.ProgramBlock.executeInstructions(ProgramBlock.java:222)
at
org.apache.sysml.runtime.controlprogram.ProgramBlock.execute(ProgramBlock.java:166)
at
org.apache.sysml.runtime.controlprogram.Program.execute(Program.java:145)
... 2 more
Caused by: org.apache.sysml.runtime.DMLRuntimeException:
java.io.FileNotFoundException: File tmp/inScalar does not exist
{code}
The matrix input and output work fine.
> JMLC/MLContext support for scalar output variables
> --
>
> Key: SYSTEMML-649
> URL: https://issues.apache.org/jira/browse/SYSTEMML-649
> Project: SystemML
> Issue Type: Task
> Components: APIs
>Reporter: Matthias Boehm
>Assignee: Deron Eriksson
>
> Right now neither JMLC nor MLContext supports scalar output variables. This
> task aims to extend both APIs with the required primitives.
> The workaround is to cast any output scalar on script-level with as.matrix to
> a 1-1 matrix and handle it in the calling application. However, especially
> with MLContext this puts an unnecessary burden on the user as he needs to
> deal with RDDs for a simple scalar too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SYSTEMML-260) Can't specify a linefeed character when printing to console
[
https://issues.apache.org/jira/browse/SYSTEMML-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson resolved SYSTEMML-260.
-
Resolution: Fixed
Fixed by [commit
1b48ca0a91997f1efa72210dbb1d289359f043e6|https://github.com/apache/incubator-systemml/commit/1b48ca0a91997f1efa72210dbb1d289359f043e6]
> Can't specify a linefeed character when printing to console
> ---
>
> Key: SYSTEMML-260
> URL: https://issues.apache.org/jira/browse/SYSTEMML-260
> Project: SystemML
> Issue Type: Improvement
> Components: APIs
>Reporter: Deron Eriksson
>Assignee: Niketan Pansare
>Priority: Minor
>
> When trying to figure out DML and PyDML code, it is very useful to print
> information to the console (using the print() function). Currently, it does
> not appear possible to be able to output a linefeed character.
> For example, the following DML:
> {code}x=1
> y=2
> print('x:' + x + '\ny:' + y)
> print('x:' + x + '\\ny:' + y){code}
> produces:
> {code}x:1\ny:2
> x:1\\ny:2{code}
> This becomes more of an issue as the complexity of what is being looked at
> increases.
> For example, here a function returning a string displaying the values in a
> matrix is called and the results are printed to the console.
> {code}matrixVals = function(matrix[double] mat) return (string str){
> str = '';
> for (i in 1:nrow(mat)) {
> str = str + '| '
> for (j in 1:ncol(mat)) {
> n = mat[i,j]
> str = str + as.scalar(n) + ' | '
> }
> str = str + '\n'
> }
> }
> m = matrix("1 2 3 4 5 6 7 8 9 10 11 12", rows=4, cols=3)
> vals = matrixVals(m)
> print(vals){code}
> The printed string is:
> {code}| 1.0 | 2.0 | 3.0 | \n| 4.0 | 5.0 | 6.0 | \n| 7.0 | 8.0 | 9.0 | \n|
> 10.0 | 11.0 | 12.0 | \n{code}
> Being able to output a linefeed character can assist DML/PyDML creators when
> figuring out their scripts.
> Note: it's possible to output a linefeed by actually having a linefeed in the
> string, but this produces code that is difficult to manage.
> {code}x=1
> y=2
> print('x:' + x + '
> y:' + y){code}
> produces:
> {code}x:1
> y:2{code}
> So, it would be nice to be able to recognize either \n or a double
> backslashed n as a linefeed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYSTEMML-642) Wrong-case boolean input parameter gives somewhat cryptic message
[
https://issues.apache.org/jira/browse/SYSTEMML-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deron Eriksson updated SYSTEMML-642:
Description:
If input parameter $X is "true" rather than "TRUE" and DML script is the
following:
{code}
print("test:" + ($X == TRUE));
{code}
The resulting error is:
{code}
...
org.apache.sysml.lops.LopsException: ERROR: line 1, column 16 -- Problem
generating simple inst -
CP°==°true·SCALAR·STRING·true°true·SCALAR·BOOLEAN·true°_Var2·SCALAR·BOOLEAN
...
Caused by: org.apache.sysml.runtime.DMLRuntimeException: unexpected value-type
in Relational Binary Instruction involving scalar operands.
{code}
I have generated this error a few times, since I have not initially realized
that my boolean input parameter coming from outside of a DML script needs to be
the correct case for DML. The error is correct, but perhaps something like
"Input parameter $X (value='true') is not valid in Relational Binary
Instruction (boolean value can only be TRUE or FALSE)", or something like that,
would make it easier for the user.
was:
If input parameter $X is "true" rather than "TRUE" and DML script is the
following:
{code}
print("test:" + ($X == TRUE));
{code}
The resulting error is:
{code}
...
org.apache.sysml.lops.LopsException: ERROR: line 1, column 16 -- Problem
generating simple inst -
CP°==°true·SCALAR·STRING·true°true·SCALAR·BOOLEAN·true°_Var2·SCALAR·BOOLEAN
...
Caused by: org.apache.sysml.runtime.DMLRuntimeException: unexpected value-type
in Relational Binary Instruction involving scalar operands.
{code}
I have generated this error a few times, since I have not initially realized
that my boolean input parameter coming from outside of a DML script needs to be
the correct case for DML. The error is correct, but perhaps something like
"Input parameter $X (value='true') is not valid in Relational Binary
Instruction (boolean value can only be TRUE or FALSE)", or something like that.
> Wrong-case boolean input parameter gives somewhat cryptic message
> -
>
> Key: SYSTEMML-642
> URL: https://issues.apache.org/jira/browse/SYSTEMML-642
> Project: SystemML
> Issue Type: Improvement
> Components: APIs
>Reporter: Deron Eriksson
>Priority: Minor
>
> If input parameter $X is "true" rather than "TRUE" and DML script is the
> following:
> {code}
> print("test:" + ($X == TRUE));
> {code}
> The resulting error is:
> {code}
> ...
> org.apache.sysml.lops.LopsException: ERROR: line 1, column 16 -- Problem
> generating simple inst -
> CP°==°true·SCALAR·STRING·true°true·SCALAR·BOOLEAN·true°_Var2·SCALAR·BOOLEAN
> ...
> Caused by: org.apache.sysml.runtime.DMLRuntimeException: unexpected
> value-type in Relational Binary Instruction involving scalar operands.
> {code}
> I have generated this error a few times, since I have not initially realized
> that my boolean input parameter coming from outside of a DML script needs to
> be the correct case for DML. The error is correct, but perhaps something like
> "Input parameter $X (value='true') is not valid in Relational Binary
> Instruction (boolean value can only be TRUE or FALSE)", or something like
> that, would make it easier for the user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SYSTEMML-647) Replace all castAsScalar calls with as.scalar
[ https://issues.apache.org/jira/browse/SYSTEMML-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15261262#comment-15261262 ] Deron Eriksson commented on SYSTEMML-647: - Note: as.scalar() needed for DML, scalar() needed for PYDML > Replace all castAsScalar calls with as.scalar > - > > Key: SYSTEMML-647 > URL: https://issues.apache.org/jira/browse/SYSTEMML-647 > Project: SystemML > Issue Type: Task > Components: APIs >Reporter: Deron Eriksson >Priority: Minor > > The castAsScalar calls in the project need to be replaced by calls to > as.scalar so that castAsScalar can eventually be removed. > There are 85 'castAsScalar' matches in the scripts directory. > There are 415 *.dml 'castAsScalar' matches in the src directory. > There are 69 *.pydml 'castAsScalar' matches in the src directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
