[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] [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] [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] [Updated] (SYSTEMML-617) Override default namespace for imported custom functions
[ https://issues.apache.org/jira/browse/SYSTEMML-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Dusenberry updated SYSTEMML-617: - Assignee: Glenn Weidner > Override default namespace for imported custom functions > > > Key: SYSTEMML-617 > URL: https://issues.apache.org/jira/browse/SYSTEMML-617 > Project: SystemML > Issue Type: Sub-task > Components: Parser >Reporter: Glenn Weidner >Assignee: Glenn Weidner >Priority: Minor > > This sub-task targets a specific scenario described in SYSTEMML-590. > Example of error: > org.apache.sysml.api.DMLException: org.apache.sysml.parser.LanguageException: > ERROR: null -- line 0, column 0 -- function g is undefined in namespace > .defaultNS > 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.LanguageException: ERROR: null -- line 0, > column 0 -- function g is undefined in namespace .defaultNS > at > org.apache.sysml.parser.StatementBlock.isMergeableFunctionCallBlock(StatementBlock.java:201) > at > org.apache.sysml.parser.StatementBlock.mergeFunctionCalls(StatementBlock.java:328) > at > org.apache.sysml.parser.DMLTranslator.liveVariableAnalysis(DMLTranslator.java:165) > at org.apache.sysml.api.DMLScript.execute(DMLScript.java:592) > at org.apache.sysml.api.DMLScript.executeScript(DMLScript.java:338) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYSTEMML-590) Improve Namespace Handling for UDFs
[
https://issues.apache.org/jira/browse/SYSTEMML-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15230474#comment-15230474
]
Mike Dusenberry commented on SYSTEMML-590:
--
Thanks, [~gweidner]! I've linked SYSTEMML-617 to this JIRA as well as a
dependent.
> Improve Namespace Handling for UDFs
> ---
>
> Key: SYSTEMML-590
> URL: https://issues.apache.org/jira/browse/SYSTEMML-590
> Project: SystemML
> Issue Type: Sub-task
>Reporter: Mike Dusenberry
>
> Currently, if a UDF body involves calling another UDF, the default global
> namespace is assumed, unless a namespace is explicitly indicated. This
> becomes a problem when a file contains UDFs, and is then sourced from another
> script.
> Imagine a file {{funcs.dml}} as follows:
> {code}
> f = function(double x, int a) return (double ans) {
> x2 = g(x)
> ans = a * x2
> }
> g = function(double x) return (double ans) {
> ans = x * x
> }
> {code}
> Then, let's try to call {{f}}:
> {code}
> script = """
> source ("funcs.dml") as funcs
> ans = funcs::f(3, 1)
> print(ans)
> """
> ml.reset()
> ml.executeScript(script)
> {code}
> This results in an error since {{f}} is in the {{funcs}} namespace, but the
> call to {{g}} assumes {{g}} is still in the default namespace. Clearly, the
> user intends to the use the {{g}} that is located in the same file.
> Currently, we would need to adjust {{funcs.dml}} as follows to explicitly
> assume that {{f}} and {{g}} are in a {{funcs}} namespace:
> {code}
> f = function(double x, int a) return (double ans) {
> x2 = funcs::g(x)
> ans = a * x2
> }
> g = function(double x) return (double ans) {
> ans = x * x
> }
> {code}
> Instead, it would be better to simply first look for {{g}} in its parent's
> namespace. In this case, the "parent" would be the function {{f}}, and the
> namespace we have selected is {{funcs}}, although that choice would be left
> up to the end-user. Then, namespace assumptions would not be necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
