Problems with arguments

[kojix2]

#27

When you pass 2d ruby array as Z to methods like contour contourf, it will not work as expected.

contourf(Z)     # z is 2d ruby array or 2d numo array.
contourf(X,Y,Z) # x, y, z are 1d ruby array or 1d numo array.

This issue is complicated because sometimes these methods get multiple series.

contourf([Z,Z,Z])
contourf([[X,Y,Z],[X,Y,Z],[X,Y,Z]])

It is impossible to distinguish contourf([[X,Y,Z],[X,Y,Z],[X,Y,Z]]) from contourf(Z).
Maybe I have to reconsider APIs...

[kojix2]

Since this issue is not easy, I opened a discussion so that I can write about it more freely than an Issue. Here, I try things this way and that, and undo my previous words more easily than in the Issue.

[kojix2]

　Arrays in Ruby have a variety of roles.
　It works like a list, holding objects of various classes. It is a substitute for a tuple, because Ruby doesn't have tuples. It is also used to represent a matrix. An array of arrays is also used to represent a two-dimensional matrix.
　Matrices should be represented by their own class, NArray, like NumPy in Python.

[kojix2]

This complicates matters.
Due to the dual-meaning of arrays in Ruby, we cannot exactly distinguish whether the argument is a list of two-dimensional arrays or a three-dimensional array.

[kojix2]

To really solve this problem, I need to list all the cases.
Case separation and mathematical thinking, that's a task I'm very bad at.