You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular I think this could be helpful for downstream select and transpose operations to set up the tensor for different types of processing and consumption. For my specific case I resorted to doing some nth and count calls and some guess and check to get a convenient shape for the next consumer in my pipeline.
The text was updated successfully, but these errors were encountered:
They aren't totally the same as the tensor shape is output on the first line. But I still think this would be a great improvement as then the counts are inline with your eye. My concern is that (994) could be interpreted as a value in the tensor balanced against your original issue.
The ellipsis printing of tensors is great, and makes repl programming with
dtype-next
a lot of fun.In the last week I had an idea for some possible improvements.
Right now, these two tensors produce the same abbreviated repl output:
My first idea is something like this, but there could be better ideas for the formatting:
In particular I think this could be helpful for downstream
select
andtranspose
operations to set up the tensor for different types of processing and consumption. For my specific case I resorted to doing somenth
andcount
calls and some guess and check to get a convenient shape for the next consumer in my pipeline.The text was updated successfully, but these errors were encountered: