Re: Parfor semantics

yes, this came up several times - initially we only supported opt=NONE where users had to specify all other parameters. Meanwhile, there is a so-called "constrained optimizer" that does the same as the rule-based optimizer but respects any given parameters. Please try something like this:

Parfor semantics

While debugging some ParFor code it became clear that the parameters for parfor can be easily overwritten by the optimizer. One example is when I write: ``` parfor (i in 1:10, par=10, mode=REMOTE_SPARK) { // some code here } ``` Depending on the data size and cluster resources, the

Jenkins build is back to normal : SystemML-DailyTest #640

See