-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NumPy (hyper)cube view #13
Comments
On 25/07/15 09:16, scls19fr wrote:
This is something I'd love to support. Where would you choose/handle the third dimension? The usual approach is another slider. Maybe we can re-use that empty space in the top-left corner with a spinner. |
I like the UI approach of Spyder about this slicing problem. |
If you have time constraints I'd prefer Blaze support before cube and hyper-cube and matrix because I'm pretty sure that I will use database connection with my students in September. |
On 25/07/15 11:18, scls19fr wrote:
I'll check out blaze definitely before. 3d is "cool to have", but since it's going to be some sort of slicing |
That's exactly how I consider things too. |
Hello Yuri,
I'm trying to view a NumPy 3D array with gtabview
Compare
gtabview
with
Spyder variables editor
With an hyper-cube (4 dimensions)
gtabview
Spyder variables editor
(which means that arrays with more than 3 dimensions can't be displayed)
Being able to view a (3D) cube will help to view a Pandas Panel as slice (and not only a flatten Panel as it's done actually).
An Excel file is also a kind of (3D) cube.
First dimension is sheetname
Second is row
Third is column
Kind regards
The text was updated successfully, but these errors were encountered: