-
Notifications
You must be signed in to change notification settings - Fork 284
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
Coords to print shorter, and avoid realising #4488
Comments
Note: I think that this risks losing the 'special' support for date formatting in printing coord outputs, which would be a practical problem. |
In case anyone doesn't get a ping from the Discussion, I just raised there an awkward question of column formatting ... Right now, having a discussion, a PR and an Issue all live on this one topic is looking positively awkard ! |
Printing large coords has been a practical problem for some time : Although numpy can print arrays in a truncated form, the results for large coords are pretty unreadable (especially those with bounds)
-- and it always realises data.
This is really about Aux-coords, as only they have the potential to be multi-dimensional, and lazy.
Which, practically, means that only they will typically be "really large".
Nevertheless, it may be better to modify DimCoords also, for consistency.
Obviously, this is likely to be especially nasty for unstructured data.
We want to tackle this now, because it affects the printout of meshes -- which is currently pretty unreadable
However, it does mean "breaking change" -- if you care about the text output from printing coords.
STOP PRESS:
now also intending to produce a 'single-line format', inspired by the Cube.repr format.
This can help a lot with making Mesh printout more sensible.
The text was updated successfully, but these errors were encountered: