Re: Loss of dimensionality info in transient reads

In general, there are a couple of scenarios which make size propagation challenging. This includes: * Complex function call patterns (where functions are potentially called with different sizes) * External user-defined functions * Data-dependent operators (e.g., table, aggregate, removeEmtpy); * C

Re: True/False flags in HOPs parameters

These flags in the runtime plans (-explain runtime or recompile_runtime) are indicators if the given input operand is a literal or not. Without these flags we could not differentiate between literal strings and variable names. Regards, Matthias On Tue, Apr 18, 2017 at 12:20 PM, wrote: > Regardi

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

See

Loss of dimensionality info in transient reads

In which scenarios would a transient read lose the row/col dimensionality information? -- Mike Dusenberry GitHub: github.com/dusenberrymw LinkedIn: linkedin.com/in/mikedusenberry Sent from my iPhone.

True/False flags in HOPs parameters

Regarding a hops plan, what is the meaning of the `true/false` flags in this snippet of the parameters to an op? `pad.SCALAR.INT.false 16.SCALAR.INT.true` -- Mike Dusenberry GitHub: github.com/dusenberrymw LinkedIn: linkedin.com/in/mikedusenberry Sent from my iPhone.

Re: Regarding incubator systemml/breast_cancer project

Hi Aishwarya, Certainly, here is some more detailed information about`preprocess.py`: * The preprocessing Python script is located at https://github.com/apache/incubator-systemml/blob/master/projects/breast_cancer/preprocess.py. Note that this is different than the library module at https:/

Build failed in Jenkins: SystemML-DailyTest #936

See Changes: [Matthias Boehm] [SYSTEMML-1509] Extended codegen compiler integration (runtime plans) -- [...truncated 27541 lines...] 17/04/18 03:50:19 INFO scheduler.TaskSchedulerIm