A Dijous 03 Maig 2007 21:26, Matt Knox escrigué:
> Thanks for the reply, Francesc. You may be correct in that a table could
> work for this. It would require a bit of work because ideally the class
> interface would be the same as EArray and not the more complicated table
> interface, so I'd have t
Matt Knox (el 2007-05-03 a les 19:26:58 +) va dir::
> One slight problem with this approach is that columns can't be dynamically
> added/removed from tables (as far as I know), so that boolean column would
> always need to be there even if the MaskedArray had no masked values to
> account
> f
> After pondering a bit the different possibilities, I think that a Table
> would be the best candidate for doing what you want. The Table is just
> like an EArray, but allows you to have different columns with different
> types in the same data container. So, in one column you can keep the
> actu
El dl 30 de 04 del 2007 a les 17:27 +, en/na Matt Knox va escriure:
> Hi everyone,
>
> I've been toying around with the idea of creating a maskedEArray class
> which would behave the same as EArray except it would handle masked
> arrays (and hence, missing data points). I can't quite think of
Hi everyone,
I've been toying around with the idea of creating a maskedEArray class which
would behave the same as EArray except it would handle masked arrays (and
hence, missing data points). I can't quite think of an efficient way to do this
at the moment though.
Subclassing EArray is not
