Brian Spilner

Hi! IMO pointwise max/min operations should be public class methods of the corresponding class (NArray,NMatrix,...). Numo.max would suggests an operation on objetcs of different Numo-classes hth

Ah, I see - I thought Numo would be a module for NArray *and* NMatrix. Will there be no Numo::NMatrix in the future?

No Problem - NArray is multidimensional out of the box. I was just asking, because some time ago I ran into problems with building gsl-bindings. The gem I used supported...

back to the topic - My favourites are both ```ruby Numo.max(a,b,...) a.max(b) ``` I guess it's rather easy to let a.max(b) make use of Numo.max(a,b) in order to stay with...

AFAIK the is not such thing like `import numpy as np` - require is file-based, and include is modules based but does not support renaming. Naming collision can also come...

IMO it works like a constructor. So I would look for something like Numo.zeros_like(a) Or simply Numo.zeros(a).

Is this realy needed? you already have something very close to it ```ruby Numo::DFloat.zeros(b.shape) ``` I personally to not need all numpy methods - esp. one-liners like this. I do...

hi! you need to use the `conda-forge` channel for getting `cdo` and `python-cdo` cheers

I guess this is solved @sujathasujji

yes, I was just suggesting a syntax - never meant to be able to run it right away ;-) thx for your thoughts! I was thinking in a similar way...